Azure Fluid Relay FAQ

The following are frequently asked questions about Azure Fluid Relay

Azure Fluid Relay is Generally Available now. For a complete list of available regions, see Azure Fluid Relay regions and availability. For our pricing list, see Azure Fluid Relay pricing.

For a complete list of available regions, see Azure Fluid Relay regions and availability.

Yes. You can move the Fluid Relay resource from one resource group to another.

Yes. You can move the Fluid Relay resource from one subscription to another.

No. Moving the Fluid Relay resource from one region to another isn’t supported.

We adhere to the security and privacy policies and practices that other Azure services follow. In addition, we have achieved industry and regional certifications.

Fluid Relay, like the Fluid Framework technology, uses both http and web sockets for communication between the clients and the service.

Yes. The Fluid Framework uses socket.io library for communication with the service. In environments where web sockets are blocked, the client will fall back to use long-polling with http.

Azure Fluid Relay stores customer data. By default, customer data is replicated to the paired region. However, the customer can choose to keep it within the same region by selecting the Basic SKU during provisioning. This option is available in select regions where the paired region is outside the boundary of the primary country/region data is stored. For more information, go to Data storage in Azure Fluid Relay.

Offline mode is when end users of your application are disconnected from the network. The Fluid Framework client accumulates operations locally and sends them to the service when reconnected. Currently, Azure Fluid Relay doesn't support extended periods of offline mode beyond 1 minute. We highly recommend that you listen to Disconnect signals and update your user experience to avoid accumulation of many ops that can get lost.