'%3e%3crect%20x='16'%20y='51'%20width='68'%20height='27'%20rx='13.5'/%3e%3ccircle%20cx='32'%20cy='53'%20r='15'/%3e%3ccircle%20cx='53'%20cy='43'%20r='20'/%3e%3ccircle%20cx='71'%20cy='57'%20r='12'/%3e%3c/g%3e%3c/svg%3e){kind=small}
Cloud Changelog
November 2, 2026 · Azure
Action needed · Due Feb 2, 2027
Retirement: Azure Fluid Relay
On February 2, 2027, we will retire Azure Fluid Relay. After this date, Azure Fluid Relay will reach end of availability, and workloads that continue to depend on the service may experience disruption.
The Fluid Framework remains available as an open-source framework for building distributed, real-time collaborative web applications. A self-hosted Fluid service solution is available as the replacement. You can continue using Azure Fluid Relay until February 1, 2027 while you complete your transition.
How this affects you:
If your applications continue to use Azure Fluid Relay after February 2, 2027, they may experience service disruption. Moving to the self-hosted solution means that you will be responsible for hosting and operating the Fluid service in your environment. Operational and infrastructure costs will depend on your deployment architecture, scale, and operational requirements.
What you need to do:
Transition workloads that depend on Azure Fluid Relay to a self-hosted Fluid service solution before February 2, 2027. Review your Azure subscriptions and identify applications that use Azure Fluid Relay, plan and complete the transition, and use the self-hosted Fluid service solution in the Fluid Framework GitHub repository as the migration and replacement resource.
The Fluid Framework remains available as an open-source framework for building distributed, real-time collaborative web applications. A self-hosted Fluid service solution is available as the replacement. You can continue using Azure Fluid Relay until February 1, 2027 while you complete your transition.
How this affects you:
If your applications continue to use Azure Fluid Relay after February 2, 2027, they may experience service disruption. Moving to the self-hosted solution means that you will be responsible for hosting and operating the Fluid service in your environment. Operational and infrastructure costs will depend on your deployment architecture, scale, and operational requirements.
What you need to do:
Transition workloads that depend on Azure Fluid Relay to a self-hosted Fluid service solution before February 2, 2027. Review your Azure subscriptions and identify applications that use Azure Fluid Relay, plan and complete the transition, and use the self-hosted Fluid service solution in the Fluid Framework GitHub repository as the migration and replacement resource.