The article describes how Azure EA agreements and amendments might affect your access, use, and payments for Azure services.
The date that the regional operations center processes the new Azure Prepayment (previously called monetary commitment) defines the new start date. Since Azure Prepayment orders via the Azure portal are processed in the UTC time zone, you might experience some delay if your Azure Prepayment purchase order was processed in a different region. The coverage start date on the purchase order shows the start of the Azure Prepayment. The coverage start date is when the Azure Prepayment appears in the Azure portal.
The Azure Enterprise Agreement Support Plan Offer is available for some customers.
An enrollment has one of the following status values. Each value determines how you can use and access an enrollment. The enrollment status determines at which stage your enrollment is. It tells you if the enrollment needs to be activated before it can be used. Or, it informs you that the initial period expired and you're getting charged for usage overage.
Pending - The enrollment administrator needs to sign in to the Azure portal. After the administrator signs in, the enrollment switches to Active status.
Active - The enrollment is accessible and usable. You can create departments, accounts, and subscriptions in the Azure portal. The enrollment remains active until the enterprise agreement end date.
Indefinite Extended Term - Indefinite extended term status occurs after the enterprise agreement end date is reached and is expired. When an agreement enters into an extended term, it doesn't receive discounted pricing. Instead, pricing is at retail rates. Before the EA enrollment reaches the enterprise agreement end date, the Enrollment Administrator should decide to:
EA credit expires when the EA enrollment ends for all programs except the EU program.
Expired - The EA enrollment expires when it reaches the enterprise agreement end date and is opted out of the extended term. Sign a new enrollment contract as soon as possible. Although your service isn't disabled immediately, there's a risk of it getting disabled.
As of August 1, 2019, new opt-out forms aren't accepted for Azure commercial customers. Instead, all enrollments go into indefinite extended term. If you want to stop using Azure services, close your subscription in the Azure portal. Or, your partner can submit a termination request. There's no change for customers with government agreement types.
Transferred - Transferred status is applied to enrollments that have their associated accounts and services transferred to a new enrollment. Enrollments don't automatically transfer if a new enrollment number is generated during renewal. The prior enrollment number must be included in the customer's renewal request for an automatic transfer.
Manually Terminated - All the subscriptions and accounts under the enrollment are deactivated. Reactivation isn't supported for terminated enrollments. For direct EA, only a non-read-only enterprise administrator can request termination with a support request. For indirect EA, the partner can submit a request in the Volume Licensing Center. However, to terminate enrollments with Expired status, the partner must request it using Azure support.
In the Azure portal, Partner Price Markup helps to enable better cost reporting for customers. The Azure portal shows usage and prices configured by partners for their customers.
Markup allows partner administrators to add a percentage markup to their indirect enterprise agreements. Percentage markup applies to all Microsoft first party service information in the Azure portal such as: meter rates, Azure Prepayment, and orders. After the partner publishes the markup, the customer sees Azure costs in the Azure portal. For example, usage summary, price lists, and downloaded usage reports. Percentage markup is not applied to Azure Marketplace.
Starting in September 2019, partners can apply markup anytime during a term. They don't need to wait until the term next anniversary to apply markup.
Microsoft doesn't access or utilize the provided markup and associated prices for any purpose unless explicitly authorized by the channel partner.
The Licensing Solution Partners (LSP) provides a single percentage number in the Azure portal. All Microsoft first party service information on the portal gets uplifted with the percentage provided by the LSP. Example:
Use the feature if you set the same markup percentage on all commercial transactions in the EA. For example, if you mark-up the Azure Prepayment information, the meter rates, the order information, and so on.
Don't use the markup feature if:
If you're using different rates for different meters, we recommend developing a custom solution based on the API key. The customer can provide the API key to pull consumption data and provide reports.
This feature is meant to provide an estimation of the Azure cost to the end customer. The LSP is responsible for all financial transactions with the customer under the EA.
Make sure to review the commercial information - monetary balance information, price list, etc. before publishing the marked-up prices to end customer.
For Azure Savings plan purchases, in some situations, indirect EA end customers could see minor variances in their utilization percentage when they view their cost reports in Cost Management. Actual purchase and usage charges are always computed in partner prices and not in customer prices (for example, with markup). Subsequent markdown and uplift could result in floating point numbers exceeding eight decimal point precision. Azure rounds calculations to eight decimal precision, which can cause minor variances in the utilization numbers for end customers.
Let's look at an example. Assume that a customer enters an Azure Savings Plan commitment amount of 3.33/hour. If the markup is 13%, after the markdown to arrive at the partner price and the subsequent markup in the cost and usage reports, there's minor variance in numbers:
You can add price markup in the Azure portal with the following steps:
Here's an example showing price markup in the Azure portal:
To check if an enrollment has a markup published, select Manage in the left navigation menu, then select the Enrollment tab. Select the enrollment box to check, and view the markup status under Enrollment Detail. It displays the current status of the markup feature for that EA as Disabled, Preview, or Published.
To check markup status of an enrollment in the Azure portal, follow the below steps:
Once partner markup is published, the indirect customer has access to the balance and charge CSV monthly files and usage detail files. The usage detail files include the resource rate and extended cost.
Partners can use the markup feature in the Azure portal after a Change of Channel Partner is processed. There's no need to wait for the next anniversary term.
EA administrators receive various types of notifications from different services. Notifications allow enterprise administrators to enroll their team members to receive usage notifications and user management notifications without giving them billing account access in the Azure portal. For more information, see Manage notification contacts.
Customers with indirect enrollment receive usage notifications containing quantity but not cost if markup is not defined for the enrollment by partner.
The system enforces the following default quotas per subscription:
Microsoft provides services to you up to at least the level of the associated usage included in the monthly Prepayment that you purchased (the Service Prepayment). However, all other increases in usage levels of service resources are subject to the availability of these service resources. For example, adding to the number of compute instances running, or increasing the amount of storage in use.
Quotas described previously aren't Service Prepayment. You can determine the number of simultaneous small compute instances, or their equivalent, that Microsoft provides as part of a Service Prepayment. Divide the number of committed small compute instance hours purchased for a month by the number of hours in the shortest month of the year. For example, February – 672 hours.
You can request a quota increase at any time by submitting an online request. To process your request, provide the following information:
Plan SKUs offer the ability to purchase a suite of integrated services together at a discounted rate. The Plan SKUs are designed to complement each other through further integrated offerings and suite for greater cost savings.
One example would be the Operations Management Suite (OMS) subscription. OMS offers a simple way to access a full set of cloud-based management capabilities. It includes analytics, configuration, automation, security, backup, and disaster recovery. OMS subscriptions include rights to System Center components to provide a complete solution for hybrid cloud environments.
You can view your price sheet in the Azure portal. For more information, see Download pricing for an enterprise agreement.