-
Initiative
-
Resolution: Unresolved
-
Blocker
-
None
-
None
Lead Time Required56 day(s)
- Update [11/3/2022]:
This KPI was administered by the Release Operations team via the PLRBilling alias until end of October 2022. Given improvements in this space, this KPI has now been updated to a self-attested model. Your self-attestation of this requirement means that you certify that emission testing was successfully performed if required - more information below. Please do not contact the PLRBilling alias as they are no longer involved in the process.
About the KPI: Meter Emission Testing
If you are launching a new Azure Service, testing of your billing configuration is crucial. Product teams not validating their billing configuration and emission logic were responsible for over $28.9 million in over and underbilling in 2020 and 2021, and over 33% of Azure Product teams encountered at least one meter billing issue during this timeframe
In Scope:
-
- Your Service is being launched in Preview or is going straight to Generally Available
-
- Testing is a requirement regardless of if your service charges customers or not
Out of Scope: You select the 'Mark as N/A' if either of the following are true
-
- You are not utilizing Azure Billing Meters
-
- You are utilizing already existing Azure Billing Meters
If you have determined that your Service is In Scope, we have two sign-off requirements:
1. Has your team verified that the configurations of all meters for all regions for this launch will emit correctly to the right Billing Meter GUID(s) for the correct Billing Region(s)?
2. Has your emission testing (i.e. formulas used to calculate usage) been verified to be accurate?
For more information about Billing Readiness please visit here
For more information about Emission Testing please visit here
For FAQ on the Lifecycle: Meter Emission Testing requirement please visit here