For anyone managing Microsoft 365 Copilot at scale, this has been a long-standing gap.
Until now, there has been no simple way to get a complete, detailed inventory of all Copilot agents deployed in your environment. You could list them — but not really understand them without stitching together multiple API calls and building unnecessary complexity.
That’s about to change.
In February 2026, Microsoft is rolling out a major improvement to the Copilot Packages Admin API that finally gives administrators what they’ve been missing: full, tenant-wide visibility into every Copilot agent and app — including all of their properties. This update was originally planned for January 2026, but has been postponed to February to ensure consistency and reliability.
And yes — it’s worth the wait.
The Reality Today: Visibility Without Insight
Today’s List Copilot packages API gives you a surface-level view:
-
Names and IDs
-
Package type
-
Supported hosts
-
Basic status metadata
That’s fine for discovery — but not for governance.
If you wanted real insight into how Copilot agents are configured, where they run, or how they differ from one another, you had to query each agent individually. In enterprise environments with dozens or hundreds of agents, that approach simply doesn’t scale.
Admins have been forced to choose between:
-
Incomplete visibility, or
-
Overly complex tooling
Neither is acceptable.
What’s Coming in February 2026
Microsoft is closing this gap.
Starting in February 2026, the Copilot Packages API will allow admins to retrieve all properties for all Copilot agents and apps in their tenant, making tenant-wide discovery both complete and practical.
Using the existing admin endpoint:
Admins will be able to programmatically:
-
Enumerate every Copilot agent in the environment
-
Access detailed package properties at scale
-
Build accurate, real-time inventories without extra API gymnastics
Official documentation is available here:
https://learn.microsoft.com/en-us/microsoft-365-copilot/extensibility/api/admin-settings/package/copilotpackages-list
Timeline Update (and Why It Matters)
-
Originally planned: January 2026
-
Updated release: February 2026
The short delay signals something important: Microsoft is treating this as a foundational admin capability, not a quick patch. Reliability and consistency across tenants matter — especially for APIs that power governance, security, and automation.
Why This Is a Big Deal
This isn’t just an API enhancement. It’s a shift in how Copilot can be managed at enterprise scale.
One Source of Truth for Copilot Agents
No more piecing together partial views. Admins can finally answer:
-
What Copilot agents exist in my tenant?
-
What are their properties and capabilities?
-
How are they configured and where do they run?
All in one place.
Governance That Actually Scales
With full agent properties available tenant-wide, organizations can:
-
Enforce standards
-
Support audits and compliance
-
Confidently roll out Copilot across teams
This is the missing layer between experimentation and enterprise readiness.
Faster, Cleaner Automation
If you’re building tooling around Copilot — dashboards, reports, ITSM integrations — this update removes unnecessary complexity and API overhead. Less code. Fewer calls. Better data.
What Admins and Platform Teams Should Do Now
If Copilot is part of your roadmap:
-
Plan to simplify your Copilot inventory and governance workflows
-
Revisit any tooling that depends on per-agent detail calls
-
Track the February 2026 rollout and be ready to adopt it early
This update doesn’t add flashy features to Copilot itself — but it finally gives admins the control and visibility they need to manage Copilot like a first-class platform.
And for many organizations, that’s the real unlock.
