Repository navigation
Agent 365 Package Catalog
Availability: optional in Stable build 1852, published on 14 October 2026, with the release code merged into
main. Apply the release migrations before enabling it.
The Agent 365 package catalog report lists the agent packages returned by Microsoft's Package Management API and identifies packages that Microsoft explicitly reports as never used. It is a catalog and aggregate-usage view, not an audit of individual people.
The optional import requires all of the following:
- A Microsoft Agent 365 license for the tenant.
- The Microsoft Graph application permission
CopilotPackages.Read.All, with admin consent on the runtime app registration. - The global Microsoft cloud; the API documentation currently lists this cloud only.
The installer can verify the application permission when the import is enabled. The API itself confirms the license requirement at runtime; an HTTP 403 is recorded as a failed attempt and does not replace the last successful catalog snapshot.
See Microsoft's List copilotPackages documentation and Prerequisites → Permissions.
In the installer, open the target configuration and enable Agent 365 package catalog. The setting is off by default. Save and deploy the configuration; the importer refreshes the catalog no more than once every 24 hours.
The importer follows all pages of the catalog before publishing a snapshot. A failed or incomplete run is recorded in the report, while the previous completed snapshot remains available. The report is under Administration → Copilot & reporting → Agent 365 catalogue and requires the Portal.Administration app role when portal-role enforcement is enabled.
Status display in 1852: an attempt with a start time but no completion time is Running (En curso in Spanish), not Failed. It raises no import-failure alert, and the previous completed snapshot remains available. Failed applies only to a completed attempt whose success flag is false.
For manual configuration, add Agent365PackageCatalog=True to the ImportJobSettings value. See Configuration reference → What to import.
The report includes package name, type or platform, publisher, last-use status, aggregate active-user and session counts, supported hosts, and availability where returned by the API. It provides a filter for packages explicitly reported as never used.
The usage distinctions are intentional:
- A
lastUsedDateTimefield returned asnullis shown as Never used. - A missing
lastUsedDateTimefield, or a package without that metric, is shown as Usage not reported and is not counted as never used. - Active-user and session metrics remain unknown when the API does not return them; missing values are not treated as zero.
Dates: package modification/last-use dates and import attempt/completion/success dates are read as UTC and returned by the API with a Z UTC marker; the browser can display them in its local time zone. Existing SQL datetime2 values keep their UTC ticks rather than being reinterpreted as server-local time. Null dates stay unknown (or explicitly never used as described above), and an unfinished attempt need not have a completion date. This is a read/serialization correction, not a stored-data repair or migration.
Microsoft's package catalog schema does not provide a verified owner field. The report therefore does not claim who owns a package or join package identities to audit events by name or an unverified identifier.
The importer stores package metadata and documented aggregate usage metrics, but not arbitrary package-definition JSON. This import does not collect per-user usage, prompts, or package contents.
Catalog metadata is not billed usage. Do not add active-user/session counts to agent cost figures, infer Copilot Credits from them, or treat an unverified catalog/audit identifier match as an agent owner or billing link.
- Copilot analytics overview
- Copilot Adoption user guide
- Copilot Adoption setup (admins)
- Work Trend Index
- Copilot investment
- Copilot spend
- Agent costs
- Prompt categories
- Copilot credit history (preview)
- Agent 365 package catalog
- The Copilot data in depth
- Prerequisites
- App registrations setup
- Install with the installer
- Verify the deployment
- Security & permissions model
- Private endpoints (optional)
- Certificate authentication (optional)
- Manual installation
- Activity & usage analytics (Power BI)
- SharePoint page tracking