Skip to content
EOL Watch
Search itemsOpen menu

AzureRetirement

Azure Fluid Relay retirement

Retirement date for Azure Fluid Relay: 2 Jun 2027. After that date the service reaches end of availability; the source says the service can be used until June 1, 2027, and the named replacement is a self-hosted Fluid service solution.

Retires , 2 Jun 2027

ShareAdd to calendarReport an error

What breaks

The source names two days: the retirement date for Azure Fluid Relay, 2 Jun 2027, and June 1, 2027, the day until which the service can be used. After the retirement date, the service reaches end of availability, and applications that still use it may experience service disruption. The Fluid Framework remains available as an open-source framework. With the self-hosted solution, the customer is responsible for hosting and operating the Fluid service, and costs depend on deployment architecture, scale, and operational requirements.

Who is affected

Matching resource types

  • microsoft.fluidrelay/fluidrelayservers
  • azurerm_fluid_relay_server

Detected by the estate check from

  • Azure Resource Graph export (CSV or JSON)
  • Terraform state or plan (JSON)
  • ARM template

Check your estate for this

What to do

  1. Review your Azure subscriptions and identify applications that use Azure Fluid Relay.
  2. Plan and complete the transition of workloads that depend on Azure Fluid Relay to a self-hosted Fluid service solution before the retirement date.
  3. Use the self-hosted Fluid service solution in the Fluid Framework GitHub repository as the migration and replacement resource.

Replacement

Self-hosted Fluid service solution

Sources

Last checked against the first source in this list on .

Related

Found an error? Report it

The text on this page is drafted with AI assistance from the vendor's text, checked against the official source and approved by a person before it is published. How items are written

Last checked · Added · Changelog for this item