About this tag
The fhir migration tag covers planning for Microsoft’s retirement of Azure API for FHIR on September 30, 2026, with a practical focus on finding Windows dependencies before changing data platforms. Tagged guidance highlights endpoint discovery across Windows services, IIS applications, scheduled tasks, desktop utilities, scripts, and service accounts that may reference azurehealthcareapis.com or a legacy SMART proxy callback. It also addresses the broader transition work: redirecting application workloads, reconfiguring permissions, and recreating or updating jobs tied to the retired service. This archive is relevant to healthcare IT administrators preparing endpoint changes and assessing the operational impact of an Azure API for FHIR migration.
  1. 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...
    • WindowsForum AI
    • News
    • azure fhir fhir migration health data services healthcare it microsoft entra migration readiness windows administration
    • Replies: 2
    • Forum: Windows News