Microsoft Copilot Studio

Connection steps are in the Copilot Studio connector guide. This page is only attribution. Microsoft 365 Copilot seats are a different file. See seats.

What you set up

1. Connect Copilot Studio with the connector guide. Meridian reads credit usage from Power Platform.
2. On Integrations, under Copilot Credit valuation rates, set the rates Meridian uses to turn credits into dollars. The form starts at $0.01 per credit for pay as you go and $0.008 for packs. Pack-draw valuation is an allocation, not an invoice line. Rate changes apply to later syncs only.
3. Create a department for each agent if you want chargeback to land on a team. The Studio resource becomes the agent. Put that agent in a department under Governance if the agent Meridian creates has none.

Copilot Studio does not tag a cloud resource per request. Do not invent a tag for this connector. (Licensing)

What Meridian receives

One row per Studio resource, environment, and UTC day. The resource id is the agent. Credits are multiplied by the rate you saved. The result is the dollar amount on the row.

Power Platform's own reports can also split by user, product, and feature, down to a day, and not down to a single message. (Credits reports) Meridian's pull uses the resource and the environment. It does not import that full report.

A session with no signed-in user uses an all-zero user id in Microsoft's reports. Meridian does not map that id.

How it's attributed

After each sync, Meridian creates or links an agent from the resource id and stores that agent on the row. The row stays unattributed. Chargeback uses the row's department if it has one, and otherwise the agent's department. With neither, the dollars post to unallocated (suspense). A person can assign the row from the inbox. Set the agent's department when you want chargeback to leave suspense.

Prepaid credits are purchased for the tenant, pooled, then allocated to an environment. Pay as you go bills the environment's Azure meter. The agent split Meridian stores is the Studio resource, not a separate Azure resource per agent. (Capacity)

What lands unattributed, and how to fix it

These rows stay in the unattributed inbox even after the agent is linked, until you assign them. The Reason column does not name the resource. The agent column does.

Give the agent a department under Governance so chargeback can leave suspense. If you also want the inbox clear, assign the rows to that same agent. A person's assignment updates unlocked dates. A locked month shows the change as an adjustment later.

If both Copilot Studio and Azure OpenAI are connected, Meridian flags the overlap for review so operators do not treat the credit dollars and the Azure OpenAI bill as two copies of the same spend. It does not match those dollars to a line on the Azure invoice. Choose which source of record you will book.

Licensed Microsoft 365 Copilot use of features the rate table marks as no charge should not be booked again as Copilot credits. Seat charges belong on the seat file.

Limits

• This is not a reconciliation that ties each credit to an Azure invoice line.
• The pull is per resource, environment, and day. It is not per message, and it does not explain why a row was not billed.
• An agent's Monitor page shows billed credits only and can be lower than the admin reports, which include non-billed credits. Meridian uses the usage it pulls, valued at your rates, not the Monitor chart.
• Agents powered by the GitHub Copilot harness inside a Microsoft 365 Copilot license are not this credit pull. (Credit consumption)
• An Azure budget notifies. It does not, by itself, stop Copilot Studio consumption.
• User-level attribution from the credits report is not what this connector stores.