Skip to content

Commit f64d888

Browse files
Merge pull request #269328 from bandersmsft/ea-pricing
MCM - Update ea-pricing for price protection
2 parents 286a732 + 5ed1c65 commit f64d888

File tree

1 file changed

+7
-2
lines changed

1 file changed

+7
-2
lines changed

articles/cost-management-billing/manage/ea-pricing-overview.md

Lines changed: 7 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -24,13 +24,18 @@ As a customer or a channel partner, you're guaranteed to receive prices at or be
2424
The price is referred to as the baseline price. Here are more details about the coverage start date:
2525

2626
- The coverage start date is based on the usage date for the purchase order. If the usage date is the first day of the month, the coverage start date is the first day of that month. If the usage date is the second day of the month or later, the coverage start date is the first day of the *following month*. If you need to backdate the coverage date, contact your partner or Software Advisor.
27+
28+
- The price guarantee start date is set in the month of the coverage start date if you purchased Azure Prepayment more than 30 days from the agreement start date.
29+
30+
For example, assume you purchased prepayment with a coverage start date of April 1, 2023. Your agreement start date is March 1, 2023. The gap between the coverage start date and the agreement start date is **more than 30 days**. So, your price guarantee start date is set to April 1, 2023.
31+
2732
- The price guarantee start date is set in the month before the coverage start date if you purchased Monetary commitment within the first 30 days of the agreement start date.
2833

2934
For example, assume you purchased prepayment with a coverage start date of April 1, 2023. Your agreement start date is March 27, 2023. The gap between the coverage start date and the agreement start date is less than 30 days. So, your price guarantee start date is set to March 1, 2023.
3035

3136
If you have questions about price protection, contact your partner or Software Advisor.
3237

33-
For services introduced after your Azure purchase, you're charged the price that's in effect at the applicable level discount when the service is first introduced. The price protection applies during your Prepayment term - one or three years depending upon your Enterprise Agreement.
38+
For services introduced after your Azure purchase, you're charged the price that's in effect at the applicable level discount when the service is first introduced. The price protection applies during your Prepayment term - one or three years depending upon your Enterprise Agreement. For more information about prepayment provisioning, [Azure EA agreements and amendments](ea-portal-agreements.md#enrollment-provisioning-status).
3439

3540
## Price changes
3641

@@ -63,7 +68,7 @@ Enterprise administrators can create subscriptions. They can also enable account
6368
## Credit process
6469

6570
- EA customers are eligible to receive service credit when they experience an SLA breach or a system issue that affects their Azure services.
66-
- Service credit isn’t refund issued as cash. Instead, service credit is issued in the form of a credit that can be applied to future Azure usage.
71+
- Service credit isn’t a refund issued as cash. Instead, service credit is issued in the form of a credit that can be applied to future Azure usage.
6772
- To request a service credit, indirect EA customers must contact their partner administrator, who is the authorized representative of the EA enrollment.
6873

6974

0 commit comments

Comments
 (0)