AzureRetirement
Azure API for FHIR retirement
Retirement date for Azure API for FHIR: 30 Sep 2026. Microsoft directs customers to migrate to the Azure Health Data Services FHIR service before that date.
Retired , 30 Sep 2026
What breaks
Azure API for FHIR is retired on the retirement date. Customers running Azure API for FHIR need to migrate to the Azure Health Data Services FHIR service before that date to avoid service disruptions. New Azure API for FHIR deployments are blocked from 1 April 2025.
Who is affected
Matching resource types
microsoft.healthcareapis/servicesazurerm_healthcare_service
Detected by the estate check from
- Azure Resource Graph export (CSV or JSON)
- Terraform state or plan (JSON)
- ARM template
What to do
Follow the migration strategies to migrate to the Azure Health Data Services FHIR service before 30 Sep 2026.
Replacement
Azure Health Data Services FHIR service
Sources
- Official sourceazure.microsoft.comOfficial
- Additional sourcelearn.microsoft.comOfficial
- Additional sourcelearn.microsoft.comOfficial
- Additional sourceaka.msOfficial
Last checked against the first source in this list on .
Related
- , 18 Aug 2026Microsoft Sentinel: retirement in Azure operated by 21VianetSource
- , 25 Aug 2026Azure AI Personalizer retirementSource
- , 1 Sep 2026Amazon MSK: Apache Kafka 3.7 end of supportSource
- , 1 Oct 2026Azure AI Services Anomaly Detector retirementSource
- , 31 Dec 2026Azure FXT Edge Filer end of supportSource
- , 31 Jan 2027Azure Blueprints retirementSource
Found an error? Report it
The text on this page is drafted with AI assistance from the vendor's text, checked against the official source and approved by a person before it is published. How items are written
Last checked · Added · Changelog for this item