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.
Also called EA.
Read more: Microsoft Learn
In the Ultra Transcenders books
Each book explains Enterprise Agreement 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.
- Microsoft Partner Agreement
The agreement Cloud Solution Provider partners use to manage Azure plan subscriptions for their customers, with one billing profile for each currency. Subscriptions can be created through code under it, but the DevTest offer is not available.
- Billing account
The highest scope under a Microsoft Customer Agreement or Partner Agreement. Billing profiles sit inside it and invoice sections inside those; the roles granted here cover invoices and creating subscriptions, never Azure resources.
- AGDLP
Nesting pattern: users go into global groups, which go into domain local groups, which receive the permissions. AGUDLP adds universal groups for forests with several domains.
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.
- Invoice section
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.