A way of splitting the charges on a Microsoft Customer Agreement billing profile's invoice, for example by team, department or project. When an Enterprise Agreement transitions to MCA, its departments turn into invoice sections.
Read more: Microsoft Learn
In the Ultra Transcenders books
Each book explains Invoice section in context, with comparison tables and the common traps.
Terms in this definition
- Microsoft Customer Agreement
Under this Microsoft agreement, the billing account is divided into billing profiles, which each get one invoice, and those are divided again into invoice sections. Enterprise MCAs allow subscriptions to be created by code, with a ceiling of 10,000.
- Billing profile
A scope within a Microsoft Customer Agreement, sitting beneath the billing account, that generates a separate monthly invoice paid by its own payment method. Each one holds at least one invoice section.
- Foundry project
A container beneath a Foundry resource that keeps one team's agents, data, files, evaluations and project connections separate. Model deployments and resource-level connections are shared from the parent, and governance is not configured at this level.
- Enterprise Agreement
Together with MCA and MPA, this is one of the Microsoft contracts under which new subscriptions can be made by code. Its billing account takes the form of an enrolment that is split into departments, then accounts.
- TURN
If a direct link can't be made, RDP Shortpath for Windows 365 relays UDP traffic via Microsoft servers on port 3478 instead.
Related terms
- Account Owner
The Enterprise Agreement billing role in charge of creating and looking after subscriptions within a single EA account, of which there is only ever one per account. When an enrolment transitions to an MCA, this person is given the Azure subscription creator role on an invoice section.
- Azure subscription creator
Under a Microsoft Customer Agreement, this role on an invoice section allows its holder to set up new subscriptions charged there, much as an account owner does under an EA. Like every billing role, it gives no rights over the resources themselves.