The billing structure in a Microsoft Azure Enterprise account can vary from company to company, depending on the size of the organization, the number of departments it creates, the number of subscriptions assigned to each department, and other factors. Azure Enterprise makes it possible to consolidate all your billing in one place, giving your company fine-grained control over it's incoming and outgoing expenses.


This section provides an overview of how you set up your Azure Enterprise account. Ensure that your Active Directory and Azure Enterprise accounts are correctly set up together. If they are, your billing and account information migrate seamlessly into VMware Cloud services.


  1. When your organization signs the Enterprise Account Agreement with Microsoft, the first thing you do is create an Enterprise Administrator.
    1. The Enterprise Administrator has permission to control everything in your Azure Enterprise account. This includes having access to your Enrollment ID.
    2. The Enterprise Administrator is the main point of contact in your organization for billing transactions and all other correspondence with Microsoft about your account.
    3. The Enterprise Administrator logs in to your Azure account at
    4. The Enterprise Administrator defines access to the other primary elements of your account: Departments, Accounts, and Subscriptions.
    5. To make managing Azure Enterprise easier, the Enterprise Administrator can create other Enterprise Administrators, with the same level of permissions and access to the account.
  2. The Enterprise Administrator creates one (or more) departments to match the needs of your organization's business structure.
    1. There can be many independent departments inside your organization, each with its own structure, organization, and flow. Marketing, Finance, Sales, and Engineering are just a few of the possible departments your Enterprise Administrator can create.
  3. The Enterprise Administrator creates one (or more) department administrators for each department.
    1. The Department Administrator has full permissions to create accounts in the department, set up cost centers, and view monthly usage and billing charges, but cannot access equivalent details about any other department.
  4. The Department Administrator creates one (or more) accounts for each department and assigns an Account Owner to each account.
    1. The Account Owner keeps track of the account, including creating and managing subscriptions, updating and managing account details, and monitoring billing in any cost centers associated with the account.
    2. The Account Owner logs in to their Azure account at
  5. The Enterprise Administrator gives the Account Owner access to the cost data for the department account.
    1. Access to the cost data for the department can only be granted by the Enterprise Administrator, who manages the cost data for the entire Azure Enterprise account.
  6. The Account Owner creates one (or more) subscriptions in the department account to allocate and manage the department's resources and expenses.
    1. Subscriptions are flexible and can be set up in multiple ways. There are no limits on the number of subscriptions that can be created to manage resources in an account. For example, every application - and all the teams creating it - can be linked to a single subscription in an engineering account. Or each development team working on an application can be linked to its own subscription instead.
    2. The Account owner controls access to the billing information in the account subscriptions using role-based access. See
    3. The Account Owner can create as many subscriptions as needed, depending upon the needs, resources, and functions assigned to the account. For example, if an account includes a multinational engineering team with developers in several countries, there could be multiple subscriptions. In a smaller local company, there may be only a few.
    4. Subscriptions can be created inside other subscriptions, to further allocate and manage resources, expenses, and personnel.
    5. Billing associated with a specific subscription can be managed and tracked. Billing and expenses can be rolled up into a parent subscription, and then into the account itself using Cost Centers set up by the Account Owner.
    6. The Account Owner creates, revises, updates, and removes subscriptions from the account as needed.
  7. Additional granularity can be achieved by assigning tags to the cost and expense resources in your subscriptions and accounts. This tagging is used to monitor, collect, and manage expenses on specific resources.
    1. For more information on using tagging with Microsoft Azure Enterprise resources, see
    2. Once granularity is set up at the lowest level of your Azure Enterprise account, the flow of billing information inside your Azure Enterprise account carries smoothly into VMware Cloud services.


For additional information on how to set up and manage billing in your Azure Enterprise account, see