HealthRecordCommunity
FHIR🌏 USA🏛 MicrosoftEnriched

Azure API for FHIR Retires: Endpoint Dependency Discovery is the Immediate Priority

Azure API for FHIR Retires September 30, 2026: Cutover Gates | Windows Forum

July 20, 2026Microsoft

Summary

Microsoft will retire Azure API for FHIR on September 30, 2026. Healthcare IT teams must prioritize 'endpoint discovery'—identifying all referencing Windows services and application workloads—over mere data migration.

Details

This article details the implications and necessary steps following the retirement of Microsoft's Azure API for FHIR. The transition requires more than just moving data; entire applications, such as clinical workflows, patient portals, and interface engines, must be updated to point to new endpoints. Crucially, dangerous dependencies may reside outside the Azure Resource Graph—such as local files or scripts (e.g., old web.config, PowerShell scripts)—necessitating comprehensive inventory creation. Recommended steps include using Azure Resource Graph for resource identification, checking Microsoft Entra app registrations and Key Vaults, and searching configuration files on Windows servers to map all dependencies. This process is vital knowledge for data migration and standardization in Japanese healthcare settings.

📰
Read Original Article
indowsforum.com
→

Original content copyright by respective publishers