Skip to content

Commit f0f3358

Browse files
xuehonggxuehongg
authored
Merge pull request #8 from ecfan/patch-2
Clarity and formatting edits
2 parents fe8c54d + 653b7a9 commit f0f3358

File tree

1 file changed

+32
-38
lines changed

1 file changed

+32
-38
lines changed

‎articles/logic-apps/logic-apps-limits-and-config.md

Lines changed: 32 additions & 38 deletions
Original file line numberDiff line numberDiff line change
@@ -526,34 +526,31 @@ Before you set up your firewall with IP addresses, review these considerations:
526526

527527
### Inbound IP addresses
528528

529-
For Azure Logic Apps to receive incoming communication through your firewall, you have to allow traffic through the inbound IP addresses described in this section for your logic app's Azure region. If you're using Azure Government, see [Azure Government - Inbound IP addresses](#azure-government-inbound).
530-
531-
> [!TIP]
532-
> To help reduce complexity when you create security rules, you can optionally use the [service tag](../virtual-network/service-tags-overview.md),
533-
> **LogicAppsManagement**, rather than specify inbound Logic Apps IP address prefixes for each region.
529+
For Azure Logic Apps to receive incoming communication through your firewall, you have to allow traffic through the inbound IP addresses described in this section for your logic app's Azure region. To help reduce complexity when you create security rules, you can optionally use the [service tag](../virtual-network/service-tags-overview.md), **LogicAppsManagement**, rather than specify the Azure Logic Apps inbound IP address prefixes for each region. If you're using Azure Government, see [Azure Government - Inbound IP addresses](#azure-government-inbound).
534530

535-
> [!Note]
536-
> Some managed connectors make inbound webhook callbacks to the Azure Logic Apps service. If you use access control on the logic
537-
> app, you need to make sure the calls from these target systems (aka IPs) are allowed to access the logic app.
538-
> The following connectors make inbound webhook callbacks to the Azure Logic Apps service:
531+
> [!NOTE]
532+
>
533+
> Some managed connectors make inbound webhook callbacks to Azure Logic Apps. If you use access control on the logic app resource,
534+
> you must make sure that the calls from these target systems (IP addresses) have permissions to access your logic app. The following
535+
> connectors make inbound webhook callbacks to Azure Logic Apps:
539536
>
540-
> Adobe Creative Cloud, Adobe Sign, Adobe Sign Demo, Adobe Sign Preview, Adobe Sign Stage, Microsoft Sentinel, Event Grid, Microsoft Form, Business Central, Calendly,
541-
> Common Data Service, DocuSign, DocuSign Demo, Dynamics 365 for Fin & Ops, LiveChat, Office 365 Outlook, Outlook.com, Parserr, SAP*,
542-
> Shifts for Microsoft Teams, Teamwork Projects, Typeform etc.
537+
> Adobe Creative Cloud, Adobe Sign, Adobe Sign Demo, Adobe Sign Preview, Adobe Sign Stage, Microsoft Sentinel, Event Grid,
538+
> Microsoft Form, Business Central, Calendly, Common Data Service, DocuSign, DocuSign Demo, Dynamics 365 for Fin & Ops,
539+
> LiveChat, Office 365* Outlook, Outlook.com, Parserr, SAP*, Shifts for Microsoft Teams, Teamwork Projects, Typeform, and so on:
543540
>
544-
> \* **Office 365**: The return caller is actually the Office 365 connector. You can specify outbound managed connector IP address prefixes for each region or optionally use the
545-
> **AzureConnectors** service tag for these managed connectors.
541+
> - **Office 365**: The return caller is actually the Office 365 connector. You can specify the managed connector outbound
542+
> IP address prefixes for each region, or optionally, you can use the **AzureConnectors** service tag for these managed connectors.
546543
>
547-
> \* **SAP**: The return caller depends on whether the deployment environment is either multi-tenant Azure or ISE. In the
548-
> multi-tenant environment, the on-premises data gateway makes the call back to the Azure Logic Apps service. In an ISE, the SAP
549-
> connector makes the call back to the Azure Logic Apps service.
544+
> - **SAP**: The return caller depends on whether the deployment environment is either multi-tenant Azure or ISE.
545+
> In the multi-tenant environment, the on-premises data gateway makes the call back to the Azure Logic Apps service.
546+
> In an ISE, the SAP connector makes the call back to Azure Logic Apps.
550547
551548
<a name="multi-tenant-inbound"></a>
552549

553550
#### Multi-tenant - Inbound IP addresses
554551

555-
| Region | IP |
556-
|--------|----|
552+
| Region | Azure Logic Apps IP |
553+
|--------|---------------------|
557554
| Australia East | 13.75.153.66, 104.210.89.222, 104.210.89.244, 52.187.231.161, 20.53.94.103, 20.53.107.215 |
558555
| Australia Southeast | 13.73.115.153, 40.115.78.70, 40.115.78.237, 52.189.216.28, 52.255.42.110, 20.70.114.64 |
559556
| Brazil South | 191.235.86.199, 191.235.95.229, 191.235.94.220, 191.234.166.198, 20.201.66.147, 20.201.25.72 |
@@ -593,46 +590,46 @@ For Azure Logic Apps to receive incoming communication through your firewall, yo
593590
| West India | 104.211.164.112, 104.211.165.81, 104.211.164.25, 104.211.157.237 |
594591
| West US | 52.160.90.237, 138.91.188.137, 13.91.252.184, 157.56.160.212, 104.40.34.112, 52.160.68.27, 13.88.168.158, 104.42.40.164, 13.87.207.79, 13.87.204.210, 168.62.9.100 |
595592
| West US 2 | 13.66.224.169, 52.183.30.10, 52.183.39.67, 13.66.128.68, 20.99.190.19, 20.72.244.108 |
596-
| West US 3| 20.150.172.240, 20.150.172.242, 20.150.172.243, 20.150.172.241, 20.106.116.172, 20.106.116.225 |
597-
|||
593+
| West US 3 | 20.150.172.240, 20.150.172.242, 20.150.172.243, 20.150.172.241, 20.106.116.172, 20.106.116.225 |
598594

599595
<a name="azure-government-inbound"></a>
600596

601597
#### Azure Government - Inbound IP addresses
602598

603-
| Azure Government region | IP |
604-
|-------------------------|----|
599+
| Azure Government region | Azure Logic Apps IP |
600+
|-------------------------|---------------------|
605601
| US Gov Arizona | 52.244.67.164, 52.244.67.64, 52.244.66.82 |
606602
| US Gov Texas | 52.238.119.104, 52.238.112.96, 52.238.119.145 |
607603
| US Gov Virginia | 52.227.159.157, 52.227.152.90, 23.97.4.36 |
608604
| US DoD Central | 52.182.49.204, 52.182.52.106 |
609-
|||
610605

611606
<a name="outbound"></a>
612607

613608
### Outbound IP addresses
614609

615610
For Azure Logic Apps to send outgoing communication through your firewall, you have to allow traffic in your logic app's Azure region for *all the outbound IP addresses* described in this section. If you're using Azure Government, see [Azure Government - Outbound IP addresses](#azure-government-outbound).
616611

617-
Also, if your workflow also uses any [managed connectors](../connectors/managed.md), such as the Office 365 Outlook connector or SQL connector, or uses any [custom connectors](/connectors/custom-connectors/), your firewall has to allow traffic in your logic app's Azure region for [*all the managed connector outbound IP addresses*](/connectors/common/outbound-ip-addresses/#azure-logic-apps). If your workflow uses custom connectors that access on-premises resources through the [on-premises data gateway resource in Azure](logic-apps-gateway-connection.md), you need to set up the gateway installation to allow access for the corresponding [*managed connector* outbound IP addresses](/connectors/common/outbound-ip-addresses#azure-logic-apps). For more information about setting up communication settings on the gateway, review these topics:
612+
> [!TIP]
613+
>
614+
> To help reduce complexity when you create security rules, you can optionally use the [service tag](../virtual-network/service-tags-overview.md),
615+
> **LogicApps**, rather than specify the Azure Logic Apps outbound IP address prefixes for each region. Optionally, you can also use the
616+
> **AzureConnectors** service tag for managed connectors that make outbound calls to their respective services, such as Azure Storage or
617+
> Azure Event Hubs, rather than specify the outbound managed connector IP address prefixes for each region. These tags work across the
618+
> regions where Azure Logic Apps is available.
619+
620+
If your workflow also uses any [managed connectors](../connectors/managed.md), such as the Office 365 Outlook connector or SQL connector, or uses any [custom connectors](/connectors/custom-connectors/), your firewall has to allow traffic in your logic app's Azure region for [*all the managed connector outbound IP addresses*](/connectors/common/outbound-ip-addresses/#azure-logic-apps). If your workflow uses custom connectors that access on-premises resources through the [on-premises data gateway resource in Azure](logic-apps-gateway-connection.md), you need to set up the gateway installation to allow access for the corresponding [*managed connector* outbound IP addresses](/connectors/common/outbound-ip-addresses#azure-logic-apps). For more information about setting up communication settings on the gateway, review these topics:
618621

619622
* [Adjust communication settings for the on-premises data gateway](/data-integration/gateway/service-gateway-communication)
620623
* [Configure proxy settings for the on-premises data gateway](/data-integration/gateway/service-gateway-proxy)
621624

622-
> [!TIP]
623-
> To help reduce complexity when you create security rules, you can optionally use the [service tag](../virtual-network/service-tags-overview.md),
624-
> **LogicApps**, rather than specify outbound Logic Apps IP address prefixes for each region. Optionally, you can also use the **AzureConnectors**
625-
> service tag for managed connectors that make outbound calls to their respective services, such as Azure Storage or Azure Event Hubs, rather than
626-
> specify outbound managed connector IP address prefixes for each region. These tags work across the regions where the Azure Logic Apps service is available.
627-
628625
<a name="multi-tenant-outbound"></a>
629626

630627
#### Multi-tenant - Outbound IP addresses
631628

632629
This section lists the outbound IP addresses that Azure Logic Apps requires in your logic app's Azure region to communicate through your firewall. Also, if your workflow uses any managed connectors or custom connectors, your firewall has to allow traffic in your logic app's Azure region for [*all the managed connectors' outbound IP addresses*](/connectors/common/outbound-ip-addresses/#azure-logic-apps). If you have custom connectors that access on-premises resources through the on-premises data gateway resource in Azure, set up your *gateway installation* to allow access for the corresponding managed connector outbound IP addresses.
633630

634-
| Region | Logic Apps IP |
635-
|--------|---------------|
631+
| Region | Azure Logic Apps IP |
632+
|--------|---------------------|
636633
| Australia East | 13.75.149.4, 104.210.91.55, 104.210.90.241, 52.187.227.245, 52.187.226.96, 52.187.231.184, 52.187.229.130, 52.187.226.139, 20.53.93.188, 20.53.72.170, 20.53.107.208, 20.53.106.182 |
637634
| Australia Southeast | 13.73.114.207, 13.77.3.139, 13.70.159.205, 52.189.222.77, 13.77.56.167, 13.77.58.136, 52.189.214.42, 52.189.220.75, 52.255.36.185, 52.158.133.57, 20.70.114.125, 20.70.114.10 |
638635
| Brazil South | 191.235.82.221, 191.235.91.7, 191.234.182.26, 191.237.255.116, 191.234.161.168, 191.234.162.178, 191.234.161.28, 191.234.162.131, 20.201.66.44, 20.201.64.135, 20.201.24.212, 191.237.207.21 |
@@ -673,22 +670,19 @@ This section lists the outbound IP addresses that Azure Logic Apps requires in y
673670
| West US | 52.160.92.112, 40.118.244.241, 40.118.241.243, 157.56.162.53, 157.56.167.147, 104.42.49.145, 40.83.164.80, 104.42.38.32, 13.86.223.0, 13.86.223.1, 13.86.223.2, 13.86.223.3, 13.86.223.4, 13.86.223.5, 104.40.34.169, 104.40.32.148, 52.160.70.221, 52.160.70.105, 13.91.81.221, 13.64.231.196, 13.87.204.182, 40.78.65.193, 13.87.207.39, 104.42.44.28, 40.83.134.97, 40.78.65.112, 168.62.9.74, 168.62.28.191 |
674671
| West US 2 | 13.66.210.167, 52.183.30.169, 52.183.29.132, 13.66.201.169, 13.77.149.159, 52.175.198.132, 13.66.246.219, 20.99.189.158, 20.99.189.70, 20.72.244.58, 20.72.243.225 |
675672
| West US 3 | 20.150.181.32, 20.150.181.33, 20.150.181.34, 20.150.181.35, 20.150.181.36, 20.150.181.37, 20.150.181.38, 20.150.173.192, 20.106.85.228, 20.150.159.163, 20.106.116.207, 20.106.116.186 |
676-
|||
677673

678674
<a name="azure-government-outbound"></a>
679675

680676
#### Azure Government - Outbound IP addresses
681677

682-
| Region | Logic Apps IP |
683-
|--------|---------------|
678+
| Region | Azure Logic Apps IP |
679+
|--------|---------------------|
684680
| US DoD Central | 52.182.48.215, 52.182.92.143 |
685681
| US Gov Arizona | 52.244.67.143, 52.244.65.66, 52.244.65.190 |
686682
| US Gov Texas | 52.238.114.217, 52.238.115.245, 52.238.117.119 |
687683
| US Gov Virginia | 13.72.54.205, 52.227.138.30, 52.227.152.44 |
688-
|||
689684

690685
## Next steps
691686

692687
* [Create an example Consumption logic app workflow in multi-tenant Azure Logic Apps](quickstart-create-example-consumption-workflow.md)
693-
694688
* [Create an example Standard logic app workflow in single-tenant Azure Logic Apps](create-single-tenant-workflows-azure-portal.md)

0 commit comments

Comments
 (0)