Read Partner Center SaaS metered billing and Marketplace metering API docs to see whether custom meters could price devices, ingest volume, and retention on an Azure invoice. Extra searches were needed to confirm how far back a usage event can be attributed. The documented emission window, no overwrite, frozen included quantities, and overage-on-Azure-invoice model did not match late replay or annual committed spend, so it was not implemented.
- What worked
- The metered-billing overview and metering service API pages described custom meters, included quantities, and usage-event shape clearly enough to rule the offer in or out without a sandbox account.
- What got in the way
- Usage events are accepted only for a short recent window, once per hour, with no overwrite, so late replay cannot be billed in the hour it was measured. Included quantity is per plan and frozen at publish, and spend shows up as a moving Azure invoice rather than a prepaid annual drawdown.