ST-2026-030 · Enforcement & amendments
Microsoft retires Azure API for FHIR and blocks portal, API and SDK access after 30 September
Microsoft will retire Azure API for FHIR on 30 September 2026, after having blocked new deployments from April 2025, and directs customers to migrate data and applications to the Azure Health Data Services FHIR service.
Previous state
Existing Azure API for FHIR accounts remained operational even though new customer deployments had been blocked since 1 April 2025.
Current state
After retirement, customers cannot create or manage accounts, access data through the portal or APIs/SDKs/client tools, receive service updates or obtain customer support.
Affected users
Who needs to care
Healthcare platform teams, application owners and data migration programmes using Azure API for FHIR, its endpoints, SDKs or SMART on FHIR proxy dependencies.
Required response
What to do
Assess data volume and architecture, deploy Azure Health Data Services FHIR service, migrate data and applications, reconfigure identity and endpoints, test cutover, and separately replace SMART on FHIR proxy before its September cutoff.
Evidence boundary
What the source does not prove
The retirement affects Azure API for FHIR, not the successor FHIR service in Azure Health Data Services. Migration tooling and capability differences require workload-specific assessment; Microsoft does not claim a zero-downtime automatic migration.
Lifecycle history
Dated event sequence
- New deployments blocked
Microsoft stopped allowing new customer deployments of Azure API for FHIR.
- SMART on FHIR proxy cutoff
Applications relying on the retiring proxy are expected to report access errors after this date.
- Service retirement
Portal, API, SDK/client access, updates and support for Azure API for FHIR end.
Evidence ledger
First-party sources
- 01Microsoft Learn — FAQ about migration from Azure API for FHIR
Official retirement and post-retirement behaviour FAQ · 2026-07-14
Open official source ↗ - 02Microsoft Learn — Migration strategies for moving from Azure API for FHIR
Official migration guidance · 2026-05-27
Open official source ↗ - 03Microsoft Lifecycle — Azure API for FHIR lifecycle
Official product lifecycle record · 2026-07-30
Open official source ↗