Microsoft has introduced Agent 365, a centralized management dashboard for enterprise AI agents within Microsoft 365 E7, featuring Microsoft Entra Agent ID for unique identities and Microsoft Purview for data protection.
Establishing the Agent Control Plane
Enterprise adoption of autonomous software has hit an administrative bottleneck. As artificial intelligence moves past isolated chat interfaces and into multi-step execution, organizations face an urgent operational challenge: managing non-human actors that possess both read and write access to sensitive corporate workflows. Agent 365 functions as a central control plane designed to track, audit, and isolate autonomous systems regardless of whether they were built on proprietary frameworks, open-source architectures, or third-party developer platforms.
The system debuted for Government Community Cloud (GCC) environments on October 1, 2026. Behind the interface, Microsoft Entra Agent ID assigns a unique identifier to every deployed agent. This architecture ensures that software agents do not operate under generic user service accounts. Instead, they carry isolated identity tokens that allow IT administrators to enforce least-privilege access boundaries.
Microsoft Purview is intended to protect sensitive data and ensure compliance with regulatory requirements. The underlying infrastructure connects through Work IQ and Fabric IQ, linking agent operations directly to structured data repositories in Dynamics 365 and the Power Platform.
Balancing Autonomy with Administrative Oversight
Corporate risk management demands hard operational telemetry. In official guidance released on October 2, 2026, Microsoft advised enterprises to enforce dedicated identities, minimal permissions, and immutable activity logs for every software agent deployed. Vasu Jakkal of Microsoft pointed out that Microsoft Security currently processes over 100 trillion daily security signals, protects more than 1.6 million customers, secures over 1 billion identities, and monitors more than 24 billion Copilot interactions.
Late in September 2026, CEO Satya Nadella characterized Copilot as a new operating system for work, emphasizing that autonomous actions must remain rigidly tethered to organizational compliance policies.
To operationalize this oversight, Agent 365 organizes its supervisory features into five core capabilities:
- Registry: A unified inventory service powered by Microsoft Entra that tracks usage, security posture, and the structural origin of every active agent. Administrators can isolate untrusted or rogue agents instantly.
- Access Control: Risk-based, adaptive access policies that react in real-time to compromised tokens or abnormal data retrieval patterns.
- Visualization: Centralized analytics dashboards mapping relationships between human users, corporate assets, and autonomous agents to calculate runtime efficiency and return on investment.
- Interoperability: Native integration with enterprise knowledge bases via Work IQ, allowing agents to execute tasks within Word, Excel, SharePoint, and Dynamics 365.
- Security: Cross-layer threat mitigation combining Microsoft Entra, Defender, and Purview to prevent unauthorized data access and unethically coded agent behaviors.
Consumption Economics and Deployment Timelines
The commercial rollout brings significant shifts in software billing. Microsoft structured the expansion around consumption-based models tied to Copilot extensions Home, Code, and Autopilot. While the Home interface unifies search and drafting tools across Word, Excel, and PowerPoint, the Code module leverages GitHub technology to generate applications and workflows from natural language prompts. Autopilot introduces proactive task execution.
Within the Cloud Solution Provider (CSP) program, Microsoft adjusted the initial rollout schedule for consumption-based billing on new Microsoft 365 Copilot Business subscriptions, shifting the start date from November 2 to December 1, 2026. Partner-Center sandboxes for testing open on November 2, 2026.
Pricing for Copilot Business tiers sits between 18 and 32 US dollars per user per month. The default spending limit is fixed at 4,000 Copilot Credits per user per month, equating to roughly 40 US dollars—yielding a maximum monthly limit of 400,000 credits for a 100-user organization. Partners retain the authority to modify or zero out these caps. Consumption charges apply directly to Copilot Cowork, Work IQ APIs, and the GitHub Copilot Harness.
Dataverse will also integrate bulk processing of legacy datasets via prompt columns, running as an asynchronous background job backed by Copilot or AI Builder credits. Public preview for this feature runs from mid-October to early November 2026, with general availability slated for November across commercial and government environments.
Regional Rollout Delays
Regional deployment schedules reveal significant geographic fragmentation. While Azure-backed subscriptions configure automatically during initial contracting in supported regions, the rollout explicitly bypasses several major markets in its initial phase.
Countries excluded from the initial Azure subscription rollout include:
- Germany
- France
- Italy
- Spain
- The Netherlands
- Belgium
- Poland
- Brazil
- India
- Korea
- Australia
