Agent 365 agents in Meridian

Short answer. Agent 365 import is available for a tenant with a Microsoft Agent 365 license or Microsoft 365 E7/G7. An AI administrator or a Global administrator consents, and the pre-flight check on Settings confirms that license. The checklist is the Microsoft prerequisites guide. Imported agents appear on Agents & allocation. The Owner column, and the agent's page, show the Microsoft owner when that person is a member of the organization. Spend still comes from a connected provider, an upload, or OASA events.

How Agent 365 agents appear

On Settings, Microsoft Teams & Copilot, an organization admin allows registry read. The person who consents in Microsoft is an AI administrator or a Global administrator. Choose Check again. Microsoft can take a few minutes to apply new consent; if the page says consent is incomplete, try Check again shortly. When the page says Agent 365 is available, Check again is hidden and Meridian imports the registry daily. Imported agents appear on Agents & allocation. The Owner column, and the agent's page, show the Microsoft owner when that person is a member of the organization. If a registry agent matches an agent Meridian already knows, the two are joined into one row.

The tenant needs a Microsoft Agent 365 license, or Microsoft 365 E7 or G7. Other Microsoft 365 plans do not include the Graph API that reads the registry. See the Microsoft prerequisites checklist.

A registry entry is a list of agents, not usage. An agent's spend appears when one of these produces a row for it:

• a connected provider or gateway that is syncing usage,
• an invoice, seat file or FOCUS file you uploaded,
• OASA events accepted on a Usage ingest key.

What to check

1. On Settings, Microsoft Teams & Copilot, confirm the tenant is connected and registry read is allowed. An AI administrator or a Global administrator grants that consent.
2. Choose Check again while the catalog is incomplete, unavailable, or not yet checked. Microsoft can take a few minutes to apply new consent; if the page says consent is incomplete, try Check again shortly. The page should say Agent 365 is available. If it says Agent 365 isn't available, the tenant needs a Microsoft Agent 365 license or Microsoft 365 E7/G7. See the Microsoft prerequisites checklist.
3. Open Integrations and confirm the source the agent calls shows Connected · syncing. See Connect a provider.
4. Open Agents & allocation → Unattributed. The agent's spend may already be there without an agent name. Assign the rows, or add a rule that matches vendor or model. See Unattributed spend is growing.
5. If the agent is built in Copilot Studio, its spend comes from the Copilot Studio connector, not from Agent 365. See Copilot Studio attribution. If you expected to see AI use rather than spend, open Shadow AI. It lists use observed through a Discovery event key. See Shadow AI.

Stop the import

An organization owner or admin chooses Stop registry import on Settings, Microsoft Teams & Copilot. Meridian stops the daily import for that tenant and deletes the snapshot it stored. That does not remove the app from Microsoft. To remove Microsoft's consent, in Entra open Enterprise applications and remove the registry app.

See From Agent 365 to the General Ledger.

What Agent 365 does receive from Meridian

When someone asks the Meridian agent a question in Microsoft Teams or Copilot, Microsoft Agent 365 receives an inference record for that model call: the agent identity, its home tenant id, the model and token counts. The question wording is not in that record. See the Privacy Policy.