About this tag
The migration readiness tag covers practical planning for Microsoft service retirements and dependency discovery. Current coverage focuses on Azure API for FHIR, where healthcare IT teams must identify Windows services, IIS applications, scheduled tasks, desktop utilities, scripts, and service accounts that still use legacy endpoints or SMART proxy callback paths. The guidance emphasizes that migration involves more than moving data: applications need new endpoint references, permissions must be configured again, and jobs tied to the retiring service may need to be recreated or redirected. Use this archive to follow endpoint inventory, workload transition, and preparation tasks ahead of the September 30, 2026 retirement date.
  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