Azure API for FHIR Retires September 30, 2026: Prioritize Dependency Discovery

Details

This article provides technical guidance regarding the sunsetting of Microsoft's Azure API for FHIR. The transition requires more than just data migration; application workloads must be updated to point to new endpoints, permissions must be reconfigured, and jobs must be recreated or redirected. A critical focus is identifying dependencies embedded in Windows services, IIS applications, scheduled tasks, or local files that reference legacy domains (such as azurehealthcareapis.com). These hidden dependencies are often invisible to Azure Resource Graph alone. The recommended approach involves first using Azure Resource Graph to inventory both the retired and target FHIR resources. Next, teams must inspect Microsoft Entra app registrations and Key Vaults. Furthermore, searching local file systems, such as via PowerShell scripts, is necessary to locate old domains or SMART proxy callback paths in configuration files (e.g., .config, .json). Following these steps helps identify the 'true dependencies' that might otherwise cause critical workflow failures.