Partner Center Check Inventory API Retires September 25: Migrate Now
Microsoft has issued a final reminder that the existing Partner Center Check Inventory API retires on 25 September 2026. CSP providers, distributors, direct bill partners, and resellers with inventory-check integrations have only a few days to confirm that production traffic uses the replacement endpoint.
What changed
Microsoft introduced the Check Inventory by Resource Type API as the replacement for /v1/extensions/product/checkinventory. The retiring endpoint must be replaced by /v1/extensions/product/checkinventorybyresourcetype.
The new API requires a resourceType parameter and filters inventory results for a defined resource type, such as VirtualMachines, SqlDatabases, or CosmosDb. Microsoft says this design addresses the growing complexity and data volume of Azure services while keeping the response contract unchanged. The September 18 reminder confirms the September 25 retirement date.
Why CSP partners should care
- Ordering can fail at the edge: a stale inventory call can make a valid Azure offer appear unavailable—or block a quote, order, or provisioning workflow altogether.
- Indirect channels multiply the blast radius: one provider-side adapter may support many reseller portals, catalog checks, and customer-facing purchase paths.
- Resource type is now an explicit dependency: integrations that previously passed only country and catalog context must map each scenario to a supported resource type.
- Retirement is a hard deadline: this is not a deprecation to leave in backlog. Partners need evidence that production traffic, retry behavior, and monitoring have moved before September 25.
Operational checklist
- Find every caller. Search source code, API gateways, functions, workflow definitions, reseller portals, and integration logs for
/v1/extensions/product/checkinventory. - Map resource types. Build an explicit mapping from each Azure product and quoting scenario to the resource type required by the new endpoint; do not silently invent values.
- Update the adapter. Call
checkinventorybyresourcetype, pass the required parameter, and preserve authentication, correlation IDs, timeout, retry, and error handling. - Test representative paths. Cover available and unavailable inventory, multiple countries, Azure resource types, reseller ordering, and failure responses in a non-production environment.
- Validate downstream behavior. Confirm that catalog availability, pricing, quote state, order submission, and customer messaging remain consistent when inventory is empty or delayed.
- Deploy with observability. Monitor endpoint usage, error rates, latency, resource-type validation failures, and fallback code. Remove the old endpoint rather than leaving an untested fallback that can mask incidents.
- Retain migration evidence. Record the change, test results, deployment time, affected tenants, and rollback or incident procedure for operational governance.
How Tagydes helps
Tagydes centralizes CSP catalog, ordering, reseller portal, and billing workflows so an API retirement can be handled as one controlled operational change instead of a hunt across disconnected scripts. Tagydes helps providers and resellers keep product availability and order state consistent across the channel, while preserving integration logs and exception paths for review.
- Centralized commerce workflows: reduce duplicate Partner Center API adapters across reseller and customer experiences.
- Operational visibility: surface failed checks and exceptions before they become blocked quotes or support tickets.
- Controlled partner operations: keep catalog, provisioning, billing, and reconciliation workflows aligned as Microsoft changes its APIs.
Source
Microsoft Partner Center announcements — Reminder: Check Inventory API retiring September 25, 2026
Microsoft Learn announcement dated 18 September 2026. The original API replacement announcement is documented in the June 23, 2026 Partner Center announcements.