Blog

Microsoft’s own account of governing 500,000+ internal agents says the fix wasn’t a policy document — it was naming three distinct administrative roles across inventory, identity, and guardrails. Here’s what that means for a Dynamics 365 organization at any scale.

Most agent pilots get scoped by whoever is paying for them. Accounts payable funds an invoice-matching agent. Procurement funds a purchase-order agent. Each one gets built to fit inside the department that wrote the check. That works fine for the first few weeks. Then a real transaction crosses into a neighboring team’s territory, and the […]

Microsoft Entra Tenant Governance went GA in August 2026 to find the tenants your organization forgot it has. If an entire tenant sits outside your administration — inherited from an acquisition, spun up by a regional office — any agent running inside it sits outside your containment policy too.

Copilot Studio agents can now hand off to other agents via MCP and A2A — real, GA infrastructure, not a forecast. Each handoff can be individually defensible while the combined outcome has no owner at all. Here’s what a chain needs that single-agent governance doesn’t supply.

Microsoft says Dynamics 365 exposes over 650,000 MCP actions. Nobody has defined what counts as one, and nobody has built the tooling to say which few dozen an agent should actually be allowed to invoke. Capability stopped being the constraint; selection is now the work.

Microsoft is retiring the twice-yearly Dynamics 365 release wave model in favor of continuous publishing. ERP change management can no longer run on a project calendar — it has to become an operating capability.