Azure API for FHIR will be retired on September 30, 2026. Follow the migration strategies to transition to Azure Health Data Services FHIR service by that date. Due to the retirement of Azure API for FHIR, new deployments won't be allowed beginning April 1, 2025. Azure Health Data Services FHIR service is the evolved version of Azure API for FHIR that enables customers to manage FHIR, DICOM, and MedTech services with integrations into other Azure services.
- Deploy a FHIR server
- Register a public client application
- Test access to the application
- Create a web application that reads this FHIR data
Before starting this set of tutorials, you'll need the following items:
- An Azure subscription
- A Microsoft Entra tenant
- Postman installed
For this tutorial, the FHIR service, Microsoft Entra application, and Microsoft Entra users are all in the same Microsoft Entra tenant. If this is not the case, you can still follow along with this tutorial, but may need to dive into some of the referenced documents to do additional steps.
Deploy Azure API for FHIR
The first step in the tutorial is to get your Azure API for FHIR setup correctly.
- If you haven't already, deploy the Azure API for FHIR.
- Once you have your Azure API for FHIR deployed, configure the CORS settings by going to your Azure API for FHIR and selecting CORS.
- Set Origins to *
- Set Headers to *
- Under Methods, choose Select all
- Set the Max age to 600
Now that you have your Azure API for FHIR deployed, you're ready to register a public client application. For more information, see
FHIR® is a registered trademark of HL7 and is used with the permission of HL7.