Skip to content

Commit 56aa34b

Browse files
author
ecfan
committed
Fix note formatting
1 parent f19cd17 commit 56aa34b

File tree

1 file changed

+9
-8
lines changed

1 file changed

+9
-8
lines changed

articles/logic-apps/logic-apps-securing-a-logic-app.md

Lines changed: 9 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1567,23 +1567,24 @@ You can use Azure Logic Apps in [Azure Government](../azure-government/documenta
15671567
* 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.
15681568

15691569
> [!IMPORTANT]
1570+
>
15701571
> Some Azure virtual networks use private endpoints ([Azure Private Link](../private-link/private-link-overview.md))
15711572
> for providing access to Azure PaaS services, such as Azure Storage, Azure Cosmos DB, or Azure SQL Database,
15721573
> partner services, or customer services that are hosted on Azure.
15731574
>
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).
15791580
1580-
For more information about isolation, review the following documentation:
1581+
For more information about isolation, see the following documentation:
15811582

15821583
* [Isolation in the Azure Public Cloud](../security/fundamentals/isolation-choices.md)
15831584
* [Security for highly sensitive IaaS apps in Azure](/azure/architecture/reference-architectures/n-tier/high-security-iaas)
15841585

15851586
## Next steps
15861587

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)
15891590
* [Monitor logic apps](monitor-workflows-collect-diagnostic-data.md)

0 commit comments

Comments
 (0)