You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/logic-apps/logic-apps-securing-a-logic-app.md
+9-8Lines changed: 9 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1567,23 +1567,24 @@ You can use Azure Logic Apps in [Azure Government](../azure-government/documenta
1567
1567
* Consumption logic app workflows can run in an [integration service environment (ISE)](connect-virtual-network-vnet-isolated-environment-overview.md) where they can use dedicated resources and access resources protected by an Azure virtual network. However, the ISE resource retires on August 31, 2024, due to its dependency on Azure Cloud Services (classic), which retires at the same time.
1568
1568
1569
1569
> [!IMPORTANT]
1570
+
>
1570
1571
> Some Azure virtual networks use private endpoints ([Azure Private Link](../private-link/private-link-overview.md))
1571
1572
> for providing access to Azure PaaS services, such as Azure Storage, Azure Cosmos DB, or Azure SQL Database,
1572
1573
> partner services, or customer services that are hosted on Azure.
1573
1574
>
1574
-
> If you want to create Consumption logic app workflows that need access to virtual networks with private endpoints,
1575
-
> you *must create and run your Consumption workflows in an ISE*. Or, you can create Standard workflows instead,
1576
-
> which don't need an ISE. Instead, your workflows can communicate privately and securely with virtual networks
1577
-
> by using private endpoints for inbound traffic and virtual network integration for outbound traffic. For more information, see
1578
-
> [Secure traffic between virtual networks and single-tenant Azure Logic Apps using private endpoints](secure-single-tenant-workflow-virtual-network-private-endpoint.md).
1575
+
> To create Consumption logic app workflows that need access to virtual networks with private endpoints,
1576
+
> you *must create and run your Consumption workflows in an ISE*. Or, you can create Standard workflows instead,
1577
+
> which don't need an ISE. Instead, your workflows can communicate privately and securely with virtual networks
1578
+
> by using private endpoints for inbound traffic and virtual network integration for outbound traffic. For more information, see
1579
+
> [Secure traffic between virtual networks and single-tenant Azure Logic Apps using private endpoints](secure-single-tenant-workflow-virtual-network-private-endpoint.md).
1579
1580
1580
-
For more information about isolation, review the following documentation:
1581
+
For more information about isolation, see the following documentation:
1581
1582
1582
1583
*[Isolation in the Azure Public Cloud](../security/fundamentals/isolation-choices.md)
1583
1584
*[Security for highly sensitive IaaS apps in Azure](/azure/architecture/reference-architectures/n-tier/high-security-iaas)
1584
1585
1585
1586
## Next steps
1586
1587
1587
-
*[Azure security baseline for Azure Logic Apps](../logic-apps/security-baseline.md)
1588
-
*[Automate deployment for Azure Logic Apps](../logic-apps/logic-apps-azure-resource-manager-templates-overview.md)
1588
+
*[Azure security baseline for Azure Logic Apps](security-baseline.md)
1589
+
*[Automate deployment for Azure Logic Apps](logic-apps-azure-resource-manager-templates-overview.md)
0 commit comments