azure fhir

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...

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...

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...