Azure Relay
Product
Azure Relay is an Azure service that exposes services in a private network to the cloud without opening inbound firewall ports; the on-premises data gateway uses it to pick up queued requests over outbound connections.
Relationships
Azure Relay is a product and part of Microsoft Azure.
Description
Azure Relay is a service in Microsoft Azure that lets a service running inside a corporate or otherwise private network be reached from the public cloud without opening an inbound firewall port or making invasive changes to the network. Instead of accepting incoming connections, the on-premises service opens an outbound connection to the relay. This approach distinguishes it from a VPN, because a relay can be limited to a single application endpoint on one machine rather than exposing a whole network.
The mechanism works in a straightforward way. The on-premises service creates a bidirectional socket for a given address through its outbound connection to the relay. Clients then send their traffic to that address, and the relay forwards it over the existing socket to the local service. Clients need no knowledge of where the service actually runs, and the local service needs no inbound ports. The documentation lists several supported scenarios: one-way messaging, request/response messaging, peer-to-peer messaging, internet-scale event distribution, and unbuffered bidirectional sockets across network boundaries.
Azure Relay includes two features that share a gateway but are implemented differently. Hybrid Connections is built on HTTP and WebSockets, works across platforms and languages including .NET and Node.js, and replaces the Hybrid Connections feature of BizTalk Services. WCF Relay is based on Windows Communication Foundation and is used for remote procedure calls. It works only with the full .NET Framework rather than .NET Core, and the documentation describes it as a legacy option. Teams choosing between the two therefore weigh platform and language requirements against the age of the technology.
In the Power BI context, Azure Relay matters because the on-premises data gateway uses it to pick up queued requests over outbound connections. This is why the gateway can serve cloud-based reports and datasets that query data sources inside a private network without any inbound firewall rules. The service itself sits in the background of that setup, which means problems with it usually surface as gateway or refresh failures rather than as errors labeled with the service name.
The M365.FM episode "Power Query Folding and Execution Order in Power BI" touches on Azure Relay in its discussion of identifying connectivity issues. According to the episode, common network problems that can affect Power BI query connections include firewall and proxy misconfigurations that block required ports, with the examples 443, 5671-5672 and 9350-9354 given. The episode also lists network latency or packet loss affecting Azure Relay connectivity, VPNs or proxies that restrict communication and may prevent the gateway from connecting properly, incorrect gateway or data source credentials that lead to authentication failures, resource limitations such as CPU and memory on the gateway machine causing disconnections, and Azure service interruptions. For diagnosis, the episode points to developer tools in the browser as a starting point.
Typical decisions around Azure Relay follow from these points. Because only outbound connectivity is needed, network teams focus on allowing the required outbound ports and on how proxies and VPNs treat that traffic, rather than on publishing internal services. For custom integration, the choice between Hybrid Connections and WCF Relay depends mainly on whether the application is built on current cross-platform stacks or on the full .NET Framework. The documentation page does not cover pricing, quotas or service limits and refers readers to the FAQ for those topics, so such details should be checked there.
Overview compiled with AI from M365.FM episodes and the facts on this page. You can improve it with the edit button below.
| Type | Product |
|---|---|
| Documentation | Azure Relay – Microsoft Learn learn.microsoft.com |
Frequently asked questions
Questions marked with AI were written with AI from the facts on this page.
What does Azure Relay do? (AI)
Azure Relay exposes services running in a private network to the cloud without opening inbound firewall ports. The on-premises service opens an outbound connection and a bidirectional socket, and the relay forwards client traffic over it.
How is Azure Relay related to the on-premises data gateway? (AI)
The on-premises data gateway uses Azure Relay to pick up queued requests over outbound connections. As a result, the gateway does not need inbound firewall ports to serve cloud requests.
What is the difference between Hybrid Connections and WCF Relay? (AI)
Hybrid Connections is built on HTTP and WebSockets and works across platforms and languages such as .NET and Node.js. WCF Relay uses Windows Communication Foundation, works only with the full .NET Framework rather than .NET Core, and is described as a legacy option.
Related topics in brief
Topics linked to Azure Relay, each briefly explained:
- Microsoft Azure – Cloud platform by Microsoft · Part of
Microsoft Azure is Microsoft's cloud platform with services for computing, storage, networking, databases, analytics and AI.
All relationships of Azure Relay, grouped by type of relationship:
Part of
Offerings of which Azure Relay is a part:
Community wiki
Short info above, community knowledge below: add practical tips, examples or corrections. New contributions are reviewed first; trusted members publish directly.
Experts and companies for this topic
Nobody has listed this topic yet. Add it to your profile.
Experts on related topics
Experts on topics related to Azure Relay, each with the topic that connects them:
- Mirko Peters ✔ · via Microsoft Azure
Sources
- Azure Relay – Microsoft Learn learn.microsoft.com
Maintained by Mirko Peters (Microsoft MVP) · Last updated: