Azure OpenAI

Connection steps are in the Azure OpenAI connector guide. This page is only attribution.

What you set up

1. Connect Azure OpenAI with the connector guide. The pull uses Cost Management on the subscription you connect.
2. Create departments under Governance and agents under Agents & allocation for the rules or assignments you will use.
3. If you need a department from an Azure tag, this connector will not read it. Export a FOCUS Cost and Usage file that contains the tags and use FOCUS upload, or put the calls behind a gateway or OASA events.

Azure does copy tags onto usage, including tags on a resource, and a project tag that Microsoft labels Preview on Foundry usage for Azure-sold models. (Foundry costs, tagging resources) Meridian's Azure pull does not request those tags. Putting oasa_cost_center on the resource does not change what this connector stores.

What Meridian receives

A daily cost query for services named Azure OpenAI and Cognitive Services. Meridian stores those daily totals. It does not group by resource, resource group, or tag. Token metrics from Azure Monitor are not this bill. Cost Analysis in the Azure portal can group more finely than this pull does. (Group and filter in Cost Analysis)

Foundry portal estimates, including an agent's Monitor tab, are not the invoice. Use Cost Management for the dollars. This connector reads Cost Management, at daily grain, without the tag breakdown.

How it's attributed

Rows arrive unattributed. A rule on Agents & allocation can match the vendor or the model. A person can assign selected rows in the inbox. Nothing on the pull declares an agent or inherits a tag.

A rule does not replace a row you have already assigned, and it does not replace a row that arrived declared or inherited from another source.

Copilot Studio credits are a different connector. If both are connected, Meridian flags the overlap for review so the same usage is not treated as two bills. It does not match Copilot Studio dollars to a line on the Azure invoice. See Copilot Studio.

What lands unattributed, and how to fix it

The daily total lands unattributed. The Reason column has no tag sentence, because no tag was requested.

Fix it at that grain: assign the rows to an agent, or add a rule and choose Apply rules now. That updates unlocked dates. A locked month is an adjustment on a later draft, not a rewrite.

To split several agents, use a gateway key per agent, OASA events that name each agent, or a FOCUS file whose tags match departments. This pull cannot do that split.

Limits

• Resource tags, the resource id, and the resource group are not dimensions of this pull.
• New Azure tags can take about 24 hours to show on usage, and only on resources that are incurring charges. Even after that, this connector does not read them. (Tag inheritance)
• Marketplace models and partner models are billed on different meters than Azure-sold models under the Foundry resource. This pull is filtered to the Azure OpenAI and Cognitive Services service names. Spend outside those names does not arrive here.
• A Foundry cost estimate is not a substitute for this total, and this total is not a per-agent invoice.