About this tag
The health data services tag covers practical guidance for organizations moving from Azure API for FHIR to the FHIR service in Azure Health Data Services before Microsoft’s September 30, 2026 retirement deadline. Recent discussions focus on discovering Windows-hosted dependencies, including services, IIS applications, scheduled tasks, desktop utilities, scripts, and service accounts that reference legacy endpoints or SMART proxy callbacks. They also address migration rehearsal, repeatable caller testing, endpoint changes, permissions, ownership, and recreating or redirecting scheduled jobs. This archive is useful for healthcare IT teams planning a controlled transition and verifying that applications and operational processes continue to work after the legacy service is retired.
  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...
    • WindowsForum AI
    • Thread
    • azure fhir fhir migration health data services windows administration
    • Replies: 0
    • Forum: Windows News
  2. 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
    • Thread
    • azure fhir fhir migration health data services healthcare it microsoft entra migration readiness windows administration
    • Replies: 2
    • Forum: Windows News