Microsoft Product Registry

Documented as the control plane for IT and security leaders to observe, secure, and govern agents.

Release Status

Not documented as preview or GA on the cited documentation page. Licensing is documented: available as a standalone subscription for eligible Microsoft 365 subscriptions and included with Microsoft 365 E7.

Admin Center or Portal Path

Microsoft 365 admin center, Agents > Overview.

Governance Gap

Change recorded: the Microsoft 365 agent registry documents Critical risk types including Shadow agent and No owner assigned. Governance gap: the registry can surface risk and ownership signals; it cannot retroactively create the business authorization that should have preceded operation.

Release Status

Generally available. Microsoft Learn documents that Copilot Cowork is now generally available and is no longer managed by selecting All Agents then Cowork in the left navigation. Cowork is documented as an agentic system, distinct from an agent, and the agent-based access control available in the preview version is no longer used to manage user access. Admins must enable usage-based billing to allow user access. Previously research preview through the Microsoft Frontier program as of May 7, 2026.

Admin Center or Portal Path

Microsoft 365 admin center, Agents > All Agents, then select Cowork from the dropdown menu to the right. Requires usage-based billing enabled. The Anthropic model family can be turned off under Copilot settings.

Governance Gap

Change recorded: Copilot Cowork reached general availability and is documented as an agentic system, explicitly distinct from an agent. The agent-based access control available in the preview version is no longer used to manage user access; access is now gated by enabling usage-based billing, and the surface moved from All Agents > Cowork to Agents > All Agents with Cowork selected from a dropdown. Governance gap: a capability that executes long-running, multi-step work across Microsoft 365 apps, business systems, and data has been reclassified out of the agent category that Agent 365 governs, and the control that now determines who can use it is a billing setting rather than an authorization decision. Nothing in the reclassification creates a record of who approved the work it does.

Published under the microsoft GitHub organization, abbreviated in-repo as AGT.

Release Status

README states public preview, production-quality Microsoft-signed releases, may have breaking changes before GA. MIT license.

Admin Center or Portal Path

Not applicable, not a Learn-documented product. Documentation site at microsoft.github.io/agent-governance-toolkit.

Governance Gap

Governance gap: the toolkit can help structure review work, but a toolkit output is not a signed authorization unless the organization binds it to a named authority and record-retention process.

Page title reads Copilot Studio overview; the legal notice uses the Microsoft-prefixed form.

Release Status

The Workflows flows format is stated as in public preview; no status label appears for the product overall. Documentation notes that after the end of June 2026 the Copilot Studio for Teams app can no longer create classic chatbots.

Admin Center or Portal Path

Standalone web app at copilotstudio.microsoft.com.

Governance Gap

Governance gap: Copilot Studio can build and administer agents, but the product record is not the same as an authorization decision naming who accepted the business scope, prohibitions, and review triggers.

Power Platform admin center is the governance console for Power Apps, Power Automate, Power Pages, Microsoft Copilot Studio, and some Dynamics 365 apps.

Release Status

Not documented on the cited page.

Admin Center or Portal Path

admin.powerplatform.microsoft.com. The CoE Starter Kit transition page maps governance work to Inventory, Usage, Monitor, and Actions in Power Platform admin center.

Governance Gap

Change recorded: Microsoft says the Power Platform CoE Starter Kit is no longer actively maintained, and that core capabilities are moving into Power Platform admin center. Governance gap: inventory and actions can reveal what exists; they do not by themselves prove a pre-operation authorization record exists.

Release Status

Not labeled preview or GA on the cited page. Documentation records a brand evolution: Azure AI Studio and Azure AI Foundry are now Microsoft Foundry, Azure AI Services is now Foundry Tools, and hub-based projects live in a separate Foundry (classic) portal.

Admin Center or Portal Path

Foundry portal at ai.azure.com.

Governance Gap

Governance gap: Foundry governs the AI development surface. It does not prove that a business authority approved the operational purpose, permitted actions, explicit prohibitions, or renewal conditions for the deployed agent.

Capability names as written are Data Security Posture Management and Data Security Posture Management for AI (classic).

Release Status

Not documented on the cited page. Documentation states that managing these AI interactions might require enabling pay-as-you-go billing. Restricted SharePoint Search documentation, last updated July 6, 2026, says new enablement is blocked from July 31, 2026.

Admin Center or Portal Path

Documented as in-product locations rather than a navigation path. Listed agents each have a dedicated Apps and agents page, and Data Security Posture Management has an additional AI observability page supporting Agent 365.

Governance Gap

Governance gap: Purview can apply data-security, DLP, audit, and posture controls to supported AI interactions. It cannot prove that an agent's business intent remained authorized after the data environment or Microsoft control surface changed.

Release Status

Documentation states Agent ID is available for all Microsoft Entra customers, with no preview label. Tenant Governance status is resolved: Microsoft announced in the Microsoft Entra Blog post "Microsoft Entra Tenant Governance is now generally available" that Microsoft Entra Tenant Governance reached general availability on August 10, 2026. Microsoft Learn still showed preview language on August 15, 2026, which is recorded as documentation lag rather than an unresolved status conflict.

Admin Center or Portal Path

Microsoft Entra admin center paths vary by Agent ID task; the cited overview does not publish one consolidated governance path.

Governance Gap

Governance gap: Entra Agent ID can identify and secure agent identities. It does not answer who approved the agent's purpose or who accepted the business consequence of the action.

Documentation distinguishes this from Microsoft 365 Copilot Chat, which requires no add-on license.

Release Status

Microsoft 365 Copilot is documented as an add-on plan with licensing prerequisites. The service description was last updated August 5, 2026 and lists commercial availability for Microsoft 365 Copilot features, with cloud-specific differences.

Admin Center or Portal Path

Microsoft 365 admin center setup guidance is linked from the licensing page. The cited service description does not publish a single governance screen path.

Governance Gap

Governance gap: this surface proves a user can use Copilot features under existing Microsoft 365 permissions and licensing; it does not prove that an agent, prompt, or delegated action was authorized by a named business owner before use.

Release Status

Generally available. Now included for Microsoft 365 E5 and E7 customers under an inclusion model with automatic provisioning after tenant enablement, providing 400 Security Compute Units per 1,000 user licenses per month, with allocations resetting monthly and not rolling over. Non-E5/E7 customers provision capacity separately, with a minimum of one provisioned SCU billed hourly and optional overage limits.

Admin Center or Portal Path

Standalone portal at securitycopilot.microsoft.com. Capacity is managed by increasing or decreasing provisioned SCUs through the Azure portal or the Security Copilot portal. Workspace and customer data storage location are set on the Owner settings page in the Security Copilot portal. Embedded experiences appear inside the Microsoft Defender, Microsoft Entra, Microsoft Intune, and Microsoft Purview portals.

Governance Gap

Change recorded: Security Copilot moved from a provision-first model to an inclusion model for Microsoft 365 E5 and E7 tenants. Microsoft Learn states eligible customers do not need to manually provision SCUs, that the service is ready to use with no action needed, and that existing Microsoft Entra, Intune, Defender, and Purview roles automatically inherit Security Copilot owner or contributor access. Governance gap: access to an AI system that reads across Defender, Entra, Intune, and Purview now arrives as a property of a role someone already held, granted by a platform rollout rather than by a decision anyone made. Auto-provisioning gets the service ready; it does not produce a record of who authorized its use, against what scope, or on whose authority. The inherited permission is the authorization, and no one signed it.