Merge pull request #202981 from bandersmsft/ghissue94729

MCM - Update for GH issue 94729

Author: tamarakhader

articles/cost-management-billing/manage/ea-portal-agreements.md

@@ -3,7 +3,7 @@ title: Azure EA agreements and amendments
 description: This article explains how Azure EA agreements and amendments affect your Azure EA portal use.
 author: bandersmsft
 ms.author: banders
-ms.date: 04/28/2022
+ms.date: 06/27/2022
 ms.topic: conceptual
 ms.service: cost-management-billing
 ms.subservice: enterprise
@@ -26,18 +26,18 @@ The start date of a new Azure Prepayment (previously called monetary commitment)
 
 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, if the initial period has expired and you're charged for usage overage.
 
-**Pending** - The enrollment administrator needs to sign in to the Azure EA portal. Once signed in, the enrollment switches to **Active** status.
+**Pending** - The enrollment administrator needs to sign in to the Azure EA portal. After the administrator signs in, the enrollment switches to **Active** status.
 
 **Active** - The enrollment is accessible and usable. You can create accounts and subscriptions in the Azure EA portal. Direct customers can create departments, accounts and subscriptions in the [Azure portal](https://portal.azure.com). 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:
 
-- Renew the enrollment by adding additional Azure Prepayment
+- Renew the enrollment by adding more Azure Prepayment
 - Transfer the existing enrollment to a new enrollment
 - Migrate to the Microsoft Online Subscription Program (MOSP)
 - Confirm disablement of all services associated with the enrollment
 
-EA credit expires when the EA enrollment ends.
+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 won't be disabled immediately, there's a risk of it getting disabled.
 
@@ -70,19 +70,19 @@ The LSP provides a single percentage number in the EA portal.  All commercial i
 
 ### When to use a markup
 
-Use the feature if you set the same markup percentage on ALL commercial transactions in the EA. i.e. – if you mark-up the Azure Prepayment information, the meter rates, the order information, etc.
+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:
 - You use different rates between Azure Prepayment and meter rates.
 - You use different rates for different meters.
 
-If you're using different rates for different meters, we recommend developing a custom solution based on the API Key, which can be provided by the customer, to pull consumption data and provide reports.
+If you're using different rates for different meters, we recommend developing a custom solution based on the API key. The API key can be provided by the customer to pull consumption data and provide reports.
 
 ### Other important information
 
 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.
 
-Please make sure to review the commercial information - monetary balance information, price list, etc. before publishing the marked-up prices to end customer.
+Make sure to review the commercial information - monetary balance information, price list, etc. before publishing the marked-up prices to end customer.
 
 ### How to add a price markup
 
@@ -100,13 +100,13 @@ Review the markup price in the _Usage Summary_ for the Prepayment term in the cu
 1. Review the prices in the price sheet.
 1. Changes can be made before publishing by selecting **Edit** on _View Usage Summary > Customer View_ tab.
 
-Both the service prices and the Prepayment balances will be marked up by the same percentages. If you have different percentages for monetary balance and meter rates, or different percentages for different services, then please don't use this feature.
+Both the service prices and the Prepayment balances will be marked up by the same percentages. If you have different percentages for monetary balance and meter rates, or different percentages for different services, then don't use this feature.
 
 **Step Three: Publish**
 
 After pricing is reviewed and validated, select **Publish**.
 
-Pricing with markup will be available to enterprise administrators immediately after selecting publish. Edits can't be made to markup. You must disable markup and begin from Step One.
+Pricing with markup will be available to enterprise administrators immediately after selecting publish. Edits can't be made to markup. You must disable markup and begin from the first step.
 
 ### Which enrollments have a markup enabled?
 
@@ -126,44 +126,44 @@ Partners can use the markup feature (on Azure EA) after a Change of Channel Part
 
 | **Resource** | **Default Quota** | **Comments** |
 | --- | --- | --- |
-| Microsoft Azure Compute Instances | 20 concurrent small compute instances or their equivalent of the other compute instance sizes. | The following table provides how to calculate the equivalent number of small instances:<ul><li> Extra Small - 1 equivalent small instance </li><li> Small - 1 equivalent small instance </li><li> Medium - 2 equivalent small instances </li><li> Large - 4 equivalent small instances </li><li> Extra Large - 8 equivalent small instances </li> </ul>|
-| Microsoft Azure Compute Instances v2 VM's | EA: 350 Cores | GA IaaS v2 VMs:<ul><li> A0\_A7 family - 350 cores </li><li> B\_A0\_A4 family - 350 cores </li><li> A8\_A9 family - 350 cores </li><li> DF family - 350 cores</li><li> GF - 350 cores </li></ul>|
-| Microsoft Azure Hosted Services | 6 hosted services | This limit of hosted services cannot be increased beyond six for an individual subscription. If you require additional hosted services, please add additional subscriptions. |
-| Microsoft Azure Storage | 5 storage accounts, each of a maximum size of 100 TB each. | You can increase the number of storage accounts to up to 20 per subscription. If you require additional storage accounts, please add additional subscriptions. |
-| SQL Azure | 149 databases of either type (i.e., Web Edition or Business Edition). |   |
+| Microsoft Azure Compute Instances | 20 concurrent small compute instances or their equivalent of the other compute instance sizes. | The following table provides how to calculate the equivalent number of small instances:<ul><li> Extra Small - one equivalent small instance </li><li> Small - one equivalent small instance </li><li> Medium - two  equivalent small instances </li><li> Large - four  equivalent small instances </li><li> Extra Large - eight equivalent small instances </li> </ul>|
+| Microsoft Azure Compute Instances v2 VMs | EA: 350 Cores | GA IaaS v2 VMs:<ul><li> A0\_A7 family - 350 cores </li><li> B\_A0\_A4 family - 350 cores </li><li> A8\_A9 family - 350 cores </li><li> DF family - 350 cores</li><li> GF - 350 cores </li></ul>|
+| Microsoft Azure Hosted Services | six hosted services | This limit of hosted services can't be increased beyond six for an individual subscription. If you require more hosted services, add more subscriptions. |
+| Microsoft Azure Storage | Five storage accounts, each of a maximum size of 100 TB each. | You can increase the number of storage accounts to up to 20 per subscription. If you require more storage accounts, add more subscriptions. |
+| SQL Azure | 149 databases of either type (for example, Web Edition or Business Edition). |   |
 | Access Control | 50 Namespaces per account. 100 million Access Control transactions per month |   |
 | Service Bus | 50 Namespaces per account. 40 Service Bus connections | Customers purchasing Service Bus connections through connection packs will have quotas equal to the midpoint between the connection pack they purchased and the next highest connection pack amount. Customers choosing a 500 Pack will have a quota of 750. |
 
 ## Resource Prepayment
 
-Microsoft will provide services to you up to at least the level of the associated usage included in the monthly Prepayment that you purchased (the Service Prepayment), but all other increases in usage levels of service resources (e.g. adding to the number of compute instances running, or increasing the amount of storage in use) are subject to the availability of these service resources.
+Microsoft will provide 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.
 
-Any quota described above is not a Service Prepayment. For purposes of determining the number of simultaneous small compute instances (or their equivalent) that Microsoft will provide as part of a Service Prepayment, this is determined by dividing the number of committed small compute instance hours purchased for a month by the number of hours in the shortest month of the year (i.e., February – 672 hours).
+Quotas described above 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.
 
 ## Requesting a quota increase
 
 You can request a quota increase at any time by submitting an [online request](https://portal.azure.com/). To process your request, provide the following information:
 
-- The Microsoft account or work or school account associated with the account owner of your subscription. This is the email address utilized to sign in to the Microsoft Azure portal to manage your subscription(s). Please also identify that this account is associated with an EA enrollment.
+- The Microsoft account or work or school account associated with the account owner of your subscription. It's the email address used to sign in to the Microsoft Azure portal to manage your subscription(s). Verify that the account is associated with an EA enrollment.
 - The resource(s) and amount for which you desire a quota increase.
 - The Azure Developer Portal Subscription ID associated with your service.
-  - For information on how to obtain your subscription ID, please [contact support](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/overview).
+  - For information on how to obtain your subscription ID, [contact support](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/overview).
 
 ## Plan SKUs
 
 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, including 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.
+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.
 
-Enterprise Administrators can assign Account Owners to provision previously purchased Plan SKUs in the Enterprise Portal by following these steps:
+Enterprise Administrators can assign Account Owners to prepare previously purchased Plan SKUs in the Enterprise portal by following these steps:
 
 ### View the price sheet to check included quantity
 
 1. Sign in as an Enterprise Administrator.
 1. Select **Reports** on the left navigation.
 1. Select the **Price Sheet** tab.
-1. Select the 'Download' icon in the top-right corner.
-1. Find the corresponding Plan SKU part numbers with filter on column "Included Quantity" and select values greater than "0".
+1. Select the **Download** symbol in the top-right corner of the page.
+1. Find the corresponding Plan SKU part numbers with filter on column **Included Quantity** and select values greater than 0 (zero).
 
 Direct customer can view price sheet in Azure portal. See [view price sheet in Azure portal](ea-pricing.md#download-pricing-for-an-enterprise-agreement).
 
@@ -175,13 +175,13 @@ Direct customer can view price sheet in Azure portal. See [view price sheet in A
 1. Select **+Add Subscription**.
 1. Select **Purchase**.
 
-The first time you add a subscription to an account, you'll need to provide your contact information. When adding later subscriptions, your contact information will be populated for you.
+The first time you add a subscription to an account, you'll need to provide your contact information. When you add more subscriptions later, your contact information will be populated for you.
 
-The first time you add a subscription to your account, you'll be asked to accept the MOSA agreement and a Rate Plan. These sections are NOT Applicable to Enterprise Agreement Customers, but are currently necessary to provision your subscription. Your Microsoft Azure Enterprise Agreement Enrollment Amendment supersedes the above items and your contractual relationship won't change. Please check the box indicating you accept the terms.
+The first time you add a subscription to your account, you'll be asked to accept the MOSA agreement and a Rate Plan. These sections aren't Applicable to Enterprise Agreement Customers, but are currently necessary to create your subscription. Your Microsoft Azure Enterprise Agreement Enrollment Amendment supersedes the above items and your contractual relationship won't change. Select the box indicating you accept the terms.
 
 **Step Two: Update subscription name**
 
-All new subscriptions will be added with the default "Microsoft Azure Enterprise" subscription name. It's important to update the subscription name to differentiate it from the other subscriptions within your Enterprise Enrollment and ensure that it's recognizable on reports at the enterprise level.
+All new subscriptions will be added with the default *Microsoft Azure Enterprise* subscription name. It's important to update the subscription name to differentiate it from the other subscriptions within your Enterprise Enrollment and ensure that it's recognizable on reports at the enterprise level.
 
 Select **Subscriptions**, select the subscription you created, and then select **Edit Subscription Details.**
 
@@ -196,21 +196,21 @@ Direct customer can create and edit subscription in Azure portal. See [manage su
 
 **Account owner showing in pending status**
 
-When new Account Owners (AO) are added to the enrollment for the first time, they'll always show as "pending" under status. Upon receiving the activation welcome email, the AO can sign in to activate their account. This activation will update their account status from "pending" to "active".
+When new Account Owners (AO) are added to the enrollment for the first time, they'll always show as `pending` under status. When you receive the activation welcome email, the AO can sign in to activate their account. This activation will update their account status from `pending` to `active`.
 
 **Usages being charged after Plan SKUs are purchased**
 
 This scenario occurs when the customer has deployed services under the wrong enrollment number or selected the wrong services.
 
-To validate if you're deploying under the right enrollment, you can check your included units information via the price sheet. Please sign in as an Enterprise Administrator and select **Reports** on the left navigation and select **Price Sheet** tab. Select the Download symbol in the top-right corner and find the corresponding Plan SKU part numbers with filter on column "Included Quantity" and select values greater than "0".
+To validate if you're deploying under the right enrollment, you can check your included units information via the price sheet. Sign in as an Enterprise Administrator and select **Reports** on the left navigation and select **Price Sheet** tab. Select the Download symbol in the top-right corner and find the corresponding Plan SKU part numbers with filter on column "Included Quantity" and select values greater than "0".
 
-Ensure that your OMS plan is showing on the price sheet under included units. If there are no included units for OMS plan on your enrollment, your OMS plan may be under another enrollment. Please contact Azure Enterprise Portal Support at [https://aka.ms/AzureEntSupport](https://aka.ms/AzureEntSupport).
+Ensure that your OMS plan is showing on the price sheet under included units. If there are no included units for OMS plan on your enrollment, your OMS plan may be under another enrollment. Contact Azure Enterprise Portal Support at [https://aka.ms/AzureEntSupport](https://aka.ms/AzureEntSupport).
 
-If the included units for the services on the price sheet don't match with what you have deployed, e.g. Operational Insights Premium Data Analyzed vs. Operational Insights Standard Data Analyzed, it means that you may have deployed services that are not covered by the plan, please contact Azure Enterprise Portal Support at [https://aka.ms/AzureEntSupport](https://aka.ms/AzureEntSupport) so we can assist you further.
+If the included units for the services on the price sheet don't match with what you have deployed, then you may have deployed services that aren't covered by the plan. For example, Operational Insights Premium Data Analyzed vs. Operational Insights Standard Data Analyzed. In this example, contact Azure Enterprise Portal Support at [https://aka.ms/AzureEntSupport](https://aka.ms/AzureEntSupport) so we can assist you further.
 
 **Provisioned Plan SKU services on wrong enrollment**
 
-If you have multiple enrollments and have deployed services under the wrong enrollment number, which doesn't have an OMS plan, please contact Azure Enterprise Portal Support at [https://aka.ms/AzureEntSupport](https://aka.ms/AzureEntSupport).
+If you have multiple enrollments and have deployed services under the wrong enrollment number, which doesn't have an OMS plan, contact Azure Enterprise Portal Support at [https://aka.ms/AzureEntSupport](https://aka.ms/AzureEntSupport).
 
 ## Next steps