Connectors outbound IP addresses

Suppose you have an environment with strict network requirements or firewalls that limit traffic to specific IP addresses. If you use managed connectors or custom connectors in Azure Logic Apps or Microsoft Power Platform, your environment or firewall must allow access for the outbound IP addresses used by these connectors in your datacenter region. Otherwise, requests sent by these connectors won't work.

When you configure firewall access rules, make sure to pay attention to the port numbers. Most connectors work on top of HTTPS protocol and use HTTPS port 443 as the default. However, some connectors might use other port numbers and protocols, such as HTTP, FTP, or SMTP. Review the following recommendations to configure firewall inbound rules as described:

  • For the destination (local) port, allow the appropriate port for the network protocol.
  • For the source (remote) port, allow ANY/ALL.

The preferred way to obtain the most current up-to-date lists of outbound IP addresses and service tags is to programmatically utilize the Service Tag Discovery API. Alternatively, downloadable lists are available for Azure Public, Azure US Government, Microsoft Azure operated by 21Vianet, and Azure Germany clouds.


Azure Logic Apps and Microsoft Power Platform each have their own datacenter regions.


If firewall or other network restrictions are in place for your environment, network security groups must allow the appropriate region service tags or the appropriate IP ranges must be added to your allow lists.

Azure Logic Apps

Before you start configuring firewall access rules for Azure Logic Apps, review the following considerations:

  • Azure Logic Apps also has inbound and outbound IP addresses that require access. For more information, review Azure Logic Apps - Firewall IP configuration considerations.

  • For Azure China 21Vianet, fixed or reserved IP addresses are unavailable for managed connectors and custom connectors in China North and China East regions. However, they are available in China North 2 and China East 2 regions.

  • If you have Standard workflows that run in the single-tenant Azure Logic Apps environment, you need the fully qualified domain names (FQDNs) for your connections. For more information, review the corresponding sections in the following articles:

  • If you create and use security rules, you can reduce complexity by using service tags instead. That way, you don't have to explicitly specify the IP address prefixes for each region. Service tags work across the regions where Azure Logic Apps is available.

  • For more information about service tags, see Virtual network service tags.

    The AzureConnectors tag represents the IP address prefixes used by managed connectors to make outbound calls to their respective services. The same service tag also represents IP address prefixes used by some managed connectors to make inbound webhook callbacks to Azure Logic Apps. Each region also has their own AzureConnectors.[region] service tag. You can use the same service tag to include all the IP address prefixes used by managed connectors.

    For example, the following managed connectors make inbound webhook callbacks to Azure Logic Apps: Adobe Creative Cloud, Adobe Sign, Adobe Sign Demo, Adobe Sign Preview, Adobe Sign Stage, Azure Sentinel, Business Central, Calendly, Common Data Service, DocuSign, DocuSign Demo, Dynamics 365 for Fin & Ops, LiveChat, Office 365 Outlook,, Parserr, SAP*, Shifts for Microsoft Teams, Teamwork Projects, and Typeform.

Region Service tags
Australia East AzureConnectors.AustraliaEast
Australia Southeast AzureConnectors.AustraliaSoutheast
Brazil South AzureConnectors.BrazilSouth
Brazil Southeast AzureConnectors.BrazilSoutheast
Canada Central AzureConnectors.CanadaCentral
Canada East AzureConnectors.CanadaEast
Central India AzureConnectors.CentralIndia
Central US AzureConnectors.CentralUS
Central US EUAP AzureConnectors.CentralUSEUAP
China East 2 AzureConnectors.ChinaEast2
China East 3 AzureConnectors.ChinaEast3
China North 2 AzureConnectors.ChinaNorth2
China North 3 AzureConnectors.ChinaNorth3
East Asia AzureConnectors.EastAsia
East US AzureConnectors.EastUS
East US 2 AzureConnectors.EastUS2
East US 2 EUAP AzureConnectors.EastUS2EUAP
France Central AzureConnectors.FranceCentral
France South AzureConnectors.FranceSouth
Germany North AzureConnectors.GermanyNorth
Germany West Central AzureConnectors.GermanyWestCentral
Israel Central AzureConnectors.IsraelCentral
Italy North AzureConnectors.ItalyNorth
Japan East AzureConnectors.JapanEast
Japan West AzureConnectors.JapanWest
Jio India West AzureConnectors.JioIndiaWest
Korea Central AzureConnectors.KoreaCentral
Korea South AzureConnectors.KoreaSouth
North Central US AzureConnectors.NorthCentralUS
North Europe AzureConnectors.NorthEurope
Norway East AzureConnectors.NorwayEast
Norway West AzureConnectors.NorwayWest
Poland Central AzureConnectors.PolandCentral
Qatar Central AzureConnectors.QatarCentral
South Africa North AzureConnectors.SouthAfricaNorth
South Africa West AzureConnectors.SouthAfricaWest
South Central US AzureConnectors.SouthCentralUS
South India AzureConnectors.SouthIndia
Southeast Asia AzureConnectors.SoutheastAsia
Sweden Central AzureConnectors.SwedenCentral
Switzerland North AzureConnectors.SwitzerlandNorth
Switzerland West AzureConnectors.SwitzerlandWest
UAE Central AzureConnectors.UAECentral
UAE North AzureConnectors.UAENorth
UK South AzureConnectors.UKSouth
UK West AzureConnectors.UKWest
West Central US AzureConnectors.WestCentralUS
West Europe AzureConnectors.WestEurope
West India AzureConnectors.WestIndia
West US AzureConnectors.WestUS
West US 2 AzureConnectors.WestUS2
West US 3 AzureConnectors.WestUS3
US DoD Central AzureConnectors.USDoDCentral
US DoD East AzureConnectors.USDoDEast
US Gov Arizona AzureConnectors.USGovArizona
US Gov Texas AzureConnectors.USGovTexas
US Gov Virginia AzureConnectors.USGovVirginia

Power Platform

Requests from Power Platform use IP addresses or service tags that depend on the region and the environment in which the app or flow is located. To facilitate Power Platform requests, add the designated IP addresses or service tags in your allow list. For more information about service tags, see Virtual network service tags.

Multi-tenant region Service tags
Asia AzureConnectors.EastAsia
Australia AzureConnectors.AustraliaCentral
Brazil AzureConnectors.BrazilEast
Canada AzureConnectors.CanadaCentral
China AzureConnectors.ChinaEast2
Europe AzureConnectors.NorthEurope
France AzureConnectors.FranceCentral
Germany AzureConnectors.GermanyCentral
India AzureConnectors.CentralIndia
Japan AzureConnectors.JapanEast
Korea AzureConnectors.KoreaCentral
Norway AzureConnectors.NorwayEast
Singapore AzureConnectors.SoutheastAsia
South Africa AzureConnectors.SouthAfricaNorth
Sweden AzureConnectors.SwedenCentral
Switzerland AzureConnectors.SwitzerlandNorth
United Arab Emirates AzureConnectors.UAECentral
United Kingdom AzureConnectors.UKNorth
United States (Preview) AzureConnectors.WestCentralUS
United States AzureConnectors.NorthCentralUS
United States Government (GCC) AzureConnectors.USGovArizona
United States Government (GCC High) AzureConnectors.USGovArizona
Department of Defense (DoD) in Azure Government AzureConnectors.USDoDCentral