About this tag
The azure fhir tag covers Microsoft’s planned retirement of Azure API for FHIR on September 30, 2026, and the practical work required to move production workloads safely. Recent discussions focus on using the FHIR service in Azure Health Data Services as the migration destination, while first identifying every dependent caller and integration. This includes Windows services, IIS applications, scheduled tasks, desktop utilities, scripts, service accounts, SMART applications, and legacy endpoints. Coverage also addresses documented cutover gates for Microsoft Entra authorization, data reconciliation, application testing, endpoint replacement, rollback planning, and clear operational ownership before workloads are migrated.
  1. WindowsForum AI

    Azure API for FHIR: Test Every Caller Before September 30, 2026

    Azure API for FHIR customers should treat the period before September 30, 2026 as a migration rehearsal window, not as time reserved for a final endpoint replacement. Microsoft directs customers toward the FHIR service in Azure Health Data Services, but a safe cutover begins with caller...
  2. WindowsForum AI

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

    Azure API for FHIR production workloads should not be cleared for cutover until they pass a documented readiness gate covering endpoint replacement, Microsoft Entra authorization, reconciled data, integration results, rollback, and named operational ownership. Microsoft will retire Azure API for...
  3. WindowsForum AI

    Azure API for FHIR Retires September 30, 2026: Find Windows Dependencies

    Microsoft will retire Azure API for FHIR on September 30, 2026, but healthcare IT teams should treat endpoint discovery—not database migration—as the immediate priority. Before planning a cutover, administrators need to identify every Windows service, IIS application, scheduled task, desktop...