You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A fancy feature for customers would be to get live insights into the current meters of their subscription. Build a web app which essentially taps into the snapshot storage JSON files, and extract the respective customer's current meters.
Background
An Azure Marketplace offer might contain "included quantities". Imagine an offer where the customer purchases a machine learning solution, which costs 100$ per month, and that monthly fee contains 10 machine learning jobs. Each time a new billing month starts, unconsumed quantities from the previous month 'evaporate', because the solution resets the current counter of remaining machine learning jobs for the new month back to 10.
A customer, who sees that the new billing month starts tomorrow, might want to 'eat up' / consume the remaining quantities before they expire ("Use it, or loose it").
Given that the ISV only submits overage consumption to Microsoft, the Azure systems do not know anything about the current metering values with respect to remaining included quantities.
By offering a query API, customers could ask "Do I still have some free credits for this month remaining?" and take consumption decisions accordingly.
The text was updated successfully, but these errors were encountered:
A fancy feature for customers would be to get live insights into the current meters of their subscription. Build a web app which essentially taps into the snapshot storage JSON files, and extract the respective customer's current meters.
Background
An Azure Marketplace offer might contain "included quantities". Imagine an offer where the customer purchases a machine learning solution, which costs 100$ per month, and that monthly fee contains 10 machine learning jobs. Each time a new billing month starts, unconsumed quantities from the previous month 'evaporate', because the solution resets the current counter of remaining machine learning jobs for the new month back to 10.
A customer, who sees that the new billing month starts tomorrow, might want to 'eat up' / consume the remaining quantities before they expire ("Use it, or loose it").
Given that the ISV only submits overage consumption to Microsoft, the Azure systems do not know anything about the current metering values with respect to remaining included quantities.
By offering a query API, customers could ask "Do I still have some free credits for this month remaining?" and take consumption decisions accordingly.
The text was updated successfully, but these errors were encountered: