Manage metered billing anomalies in Partner Center
The custom metered billing option is currently available to Software as a service (SaaS) offers, Azure Applications with a Managed application plan and Kubernetes app offers.
If you're using the metered billing option to create offers in the commercial marketplace program that lets you charge for usage based on nonstandard units, you need to know when your customer has used more of a service than expected.
Microsoft relies on you, the partner, to report your customers’ overage usage of their SaaS, Azure Managed application or Kubernetes app offers before Microsoft invoices the customer. If the wrong usage is reported, the customer could potentially receive an incorrect invoice, undermining both Microsoft’s and the partner’s credibility.
To help ensure that your customers are billed correctly, use the Anomaly detection feature for both SaaS Apps and Azure application managed application plans. This feature monitors usage against metered billing and predicts the expected value of usage within the expected range. If the usage is outside the expected range, it's treated as unexpected (an anomaly), and you'll receive an alert notification on your Offer Overview page in the commercial marketplace program of Partner Center. You can track your customers’ usage daily for every custom meter dimension that you’ve set.
Sign in to Partner Center.
On the Home page, select the Insights tile.
In the left menu, select Usage.
Select the Metered usage anomalies tab.
For any usage anomalies detected against metered billing, as a publisher you'll be asked to investigate and confirm if the anomaly is true or not. Select Mark as anomaly to confirm the diagnosis.
If you believe that the overage usage anomaly we detected isn't genuine, you can provide that feedback by selecting Not an anomaly for the Partner Center flagged anomaly on the particular overage usage.
You can scroll down the page to see an inventory list of unacknowledged anomalies. The list provides an inventory of anomalies that you've not acknowledged. You can choose to mark any of the Partner Center-flagged anomalies as genuine or false.
Figure 4: Partner Center unacknowledged anomalies listBy default, flagged anomalies that have an estimated financial impact greater than 100 USD are shown in Partner Center. However, you can select All from the Estimated financial impact of anomaly list to see all flagged anomalies.
You would also see an anomaly action log that shows the actions you took on the overage usages. In the action log, you'll be able to see which overage usage events were marked as genuine or false.
Partner Center analytics won't support restatement of overage usage events in the export reports. Partner Center lets you enter the corrected overage usage for an anomaly and the details are passed on to the correct Microsoft team for investigation. Based on the investigation, Microsoft will issue credit refunds to the overcharged customer, as appropriate. When you select any of the flagged anomalies, you can select Mark as anomaly to mark the usage overage anomaly as genuine.
The first time an overage usage is flagged as irregular in Partner Center, you'll get a window of 30 days from that instance to mark the anomaly as genuine or false. After the 30-day period, as the publisher you wouldn't be able to act on the anomalies.
Svarīgi
Under-reported overage usage units aren't eligible for restatement and financial adjustment.
You can see all the anomalies (acknowledged or otherwise) for the selected computation period. The various computation periods are the last 30 days, last 60 days, and last 90 days.
Svarīgi
You're requested to act on the flagged anomalies within 30 days of the time from when the anomalies are first reported in Partner Center.
The filter modal in the widget lets you select individual offers and individual custom meters.
After you mark an overage usage as an anomaly or acknowledge a model that flagged an anomaly as genuine, you can’t change the selection to “Not an Anomaly”.
Svarīgi
You can resubmit overage usages in the event of overcharge situations.