Agent 365 Cost Management + Meridian: from the admin center to the general ledger
Last reviewed 2026-11-18.
Short answer. Agent 365 Cost Management shows IT what Microsoft AI services cost and where a limit can stop them. Meridian attributes that spend, and spend from other providers, to an owner and a cost center. It then posts the journal entry finance closes on.
Microsoft Agent 365 Cost Management gives IT administrators one place to see, limit and alert on usage-based Microsoft AI services. Meridian gives finance the next step: it attributes that spend, and the AI spend outside Microsoft, to the departments, cost centers and agents that caused it. Then it books it to the general ledger as journal entries a controller can close on. Use them together. Agent 365 handles control in the tenant, and Meridian handles accounting.
Updated November 18, 2026
What Microsoft announced
At Ignite 2026, Microsoft brought FinOps discipline into Agent 365. The details are in the Ignite 2026 Book of News and the September 25, 2026 FinOps for AI post:
- Agent 365 Cost Management (Microsoft 365 admin center, preview) is a central place to see and control usage-based AI services such as Copilot Cowork, Copilot Code, GitHub Copilot CLI, Copilot Studio, Copilot Managed Runtime, Autopilot and Work IQ APIs. Admins see spend drivers and set spending policies, limits and alerts. A Copilot Studio spending policy can set a monthly limit and a per-agent limit. Credit guidance treats an agent-level limit as the stopping point. A budget notification by itself does not stop consumption. For chargeback, spending policies associate charges with Azure subscriptions and resource groups, and admins can extend the analysis through Microsoft Fabric.
- Agent 365 Business Analytics (Frontier program) puts AI cost next to adoption and outcome measures for business leaders. Insights on Microsoft services need at least one Microsoft 365 Copilot license. Insights on non-Microsoft services need an Agent 365 license.
- Microsoft has said it will extend value insights to non-Microsoft agents.
This is a big step. When the company that sells most enterprise AI seats says AI spend needs FinOps, the category is mainstream.
What still has to happen after the admin center
A spending policy in the admin center is a control. It is not an accounting entry. At month-end, finance still has to answer questions the admin center was not built for:
| Finance question | Agent 365 Cost Management | Meridian |
|---|---|---|
| What did Microsoft AI services cost, by user, group and agent? | Yes, in the admin center (credits) | Copilot Studio credits per agent, priced at your rate. More Microsoft services on the roadmap |
| Who owns each agent, and which department is it in? | Not a cost dimension | Yes: owners from your Agent 365 inventory, mapped to departments and cost centers |
| What did OpenAI, Anthropic, AWS Bedrock and Google cost, for the same agents and departments? | Not today (non-Microsoft value insights announced as planned) | Yes, direct provider connections and gateway ingest |
| Which cost center and GL account does each dollar belong to? | Spending policies associate charges with Azure subscriptions and resource groups. Fabric supports custom chargeback reports | Attribution rules and rate cards, owned by finance, down to department and GL account |
| Post it to the books | No | Journal entries to QuickBooks Online and Dynamics 365 Business Central. NetSuite, Sage Intacct, SAP and Dynamics 365 Finance are in early access |
| Accruals for usage not yet invoiced, and invoice reconciliation | No | Partial today: a beta month-end accrual for metered usage not yet on an invoice, and a true-up that scales measured usage to the confirmed vendor invoice. |
| Spending limits | A Copilot Studio policy can set a monthly limit and a per-agent limit. An agent-level limit is the stopping point | Alerts and budgets. Use Microsoft's limit where it exists |
| One record of agent spend that holds up under audit | Partial: admin view of Microsoft services | Agent Ledger with an audit trail |
| Open, vendor-neutral data format | Microsoft schema | OASA, an open spec under CC BY 4.0 |
How they fit together
- Inventory. Meridian reads your Agent 365 agent inventory and owners every day (plus Google Agent Registry), so every agent has an owner and a cost center.
- Meter. Microsoft meters Copilot Credits. Meridian prices Copilot Studio credits per agent at your rate, and meters the rest of your AI spend (OpenAI, Anthropic, AWS Bedrock, Google, Azure OpenAI, AI gateways such as LiteLLM, Kong and Portkey, and OpenTelemetry) in one normalized ledger.
- Control. Set spending policies and limits in Agent 365 for Microsoft services. Use Meridian budgets and alerts in Teams or Slack for spend across all providers.
- Book. Meridian turns attributed spend into chargeback journal entries in your GL. The controller reviews them and posts them.
- Prove. Every entry traces back to the agent, the source record and the rule that allocated it.
Who does what
- IT admin: sets Agent 365 spending policies, limits and model access.
- FinOps analyst: reconciles provider invoices, tunes allocation rules, and watches anomalies in Meridian.
- Controller / CFO: gets AI spend in the general ledger by cost center, closes on time, and can show the board what agents cost.
Where this is going
Agents will soon spend across many vendors, clouds and payment rails in a single workflow. No single vendor's admin center can be the system of record for that. Finance needs a neutral ledger that every source writes into and every ERP can read. That is what Meridian and the OASA spec are built for.
FAQ
Is Agent 365 Cost Management free? Microsoft says cost management in Agent 365 is included with your Microsoft cloud subscription. Business Analytics has license requirements: a Microsoft 365 Copilot license in the tenant for Microsoft services, and an Agent 365 license for non-Microsoft services.
Does Agent 365 Cost Management post to the general ledger? No. Spending policies associate charges with Azure subscriptions and resource groups, and Fabric can hold custom chargeback reports. The Ignite announcements don't describe general ledger posting. Meridian splits that spend by owner and department and posts chargeback journal entries to QuickBooks Online and Business Central today.
Do I need Meridian if all my AI is Microsoft? If you only need to see and limit Microsoft AI usage, the admin center may be enough. You need Meridian when finance has to allocate that spend to cost centers, book it, accrue it, or combine it with OpenAI, Anthropic, AWS or Google spend.
Does Meridian replace Agent 365? No. Agent 365 governs agents in your Microsoft tenant. Meridian is finance's ledger for what all agents spend. Meridian reads from Agent 365. It does not compete with it.
How do I start? Run the free two-week Agent Spend Assessment. We connect your sources, including your Agent 365 agent inventory, and show you a month of AI spend by cost center, ready to book.
Next step
Start the free assessment · See integrations · FinOps for agentic AI · What finance still does at month-end