Clarify steps to find Networking page

Author: ecfan

articles/connectors/enable-stateful-affinity-built-in-connectors.md

@@ -36,21 +36,21 @@ To run these connector operations in stateful mode, you must enable this capabil
 
 1. In the [Azure portal](https://portal.azure.com), open the Standard logic app resource where you want to enable stateful mode for these connector operations.
 
-1. Enable virtual network integration for your logic app and add your logic app to the previously created subnet:
+1. To enable virtual network integration for your logic app, and add your logic app to the previously created subnet, follow these steps:
 
-   1. On your logic app menu resource, under **Settings**, select **Networking**.
+   1. On the logic app menu resource, under **Settings**, select **Networking**.
 
-   1. In the **Outbound Traffic** section, select **VNET integration** > **Add VNet**.
+   1. In the **Outbound traffic configuration** section, next to **Virtual network integration**, select **Not configured** > **Add virtual network integration**.
 
-   1. On the **Add VNet Integration** pane that opens, select your Azure subscription and your virtual network.
+   1. On the **Add virtual network integration** pane that opens, select your Azure subscription and your virtual network.
 
-   1. Under **Subnet**, select **Select existing**. From the **Subnet** list, select the subnet where you want to add your logic app.
+   1. From the **Subnet** list, select the subnet where you want to add your logic app.
 
-   1. When you're done, select **OK**.
+   1. When you're done, select **Connect**, and return to the **Networking** page.
 
-      On the **Networking** page, the **VNet integration** option now appears set to **On**, for example:
+      The **Virtual network integration** property is now set to the selected virtual network and subnet, for example:
 
-      :::image type="content" source="media/enable-stateful-affinity-built-in-connectors/enable-virtual-network-integration.png" alt-text="Screenshot shows Azure portal, Standard logic app resource, Networking page, VNet integration set to On.":::
+      :::image type="content" source="media/enable-stateful-affinity-built-in-connectors/enable-virtual-network-integration.png" alt-text="Screenshot shows Azure portal, Standard logic app resource, Networking page with selected virtual network and subnet.":::
 
    For general information about enabling virtual network integration with your app, see [Enable virtual network integration in Azure App Service](../app-service/configure-vnet-integration-enable.md).
 

articles/connectors/media/enable-stateful-affinity-built-in-connectors/enable-virtual-network-integration.png

@@ -87,29 +87,31 @@ You can limit access to the inputs and outputs in the run history for your logic
 
 For example, to block anyone from accessing inputs and outputs, specify an IP address range such as `0.0.0.0-0.0.0.0`. Only a person with administrator permissions can remove this restriction, which provides the possibility for "just-in-time" access to data in your logic app workflows. A valid IP range uses these formats: *x.x.x.x/x* or *x.x.x.x-x.x.x.x*
 
-To specify the allowed IP ranges, follow these steps for either the Azure portal or your Azure Resource Manager template:
+To specify the allowed IP ranges, follow these steps for your Consumption or Standard logic app in the Azure portal or your Azure Resource Manager template:
 
 #### [Portal](#tab/azure-portal)
 
 ##### Consumption workflows
 
-1. In the [Azure portal](https://portal.azure.com), open your logic app workflow in the designer.
+1. In the [Azure portal](https://portal.azure.com), open your Consumption logic app workflow in the designer.
 
 1. On your logic app's menu, under **Settings**, select **Workflow settings**.
 
-1. Under **Access control configuration** > **Allowed inbound IP addresses**, select **Specific IP ranges**.
+1. In the **Access control configuration** section, under **Allowed inbound IP addresses**, from the **Trigger access option** list, select **Specific IP ranges**.
 
-1. Under **IP ranges for contents**, specify the IP address ranges that can access content from inputs and outputs.
+1. In the **IP ranges for contents** box, specify the IP address ranges that can access content from inputs and outputs.
 
 ##### Standard workflows
 
-1. In the [Azure portal](https://portal.azure.com), open your logic app resource.
+1. In the [Azure portal](https://portal.azure.com), open your Standard logic app resource.
 
 1. On the logic app menu, under **Settings**, select **Networking**.
 
-1. In the **Inbound Traffic** section, select **Access restriction**.
+1. In the **Inbound traffic configuration** section, next to **Public network access**, select **Enabled with no access restriction**.
 
-1. Create one or more rules to either **Allow** or **Deny** requests from specific IP ranges. You can also use the HTTP header filter settings and forwarding settings.
+1. On the **Access restrictions** page, under **App access**, select **Enabled from select virtual networks and IP addresses**.
+
+1. Under **Site access and rules**, on the **Main site** tab, add one or more rules to either **Allow** or **Deny** requests from specific IP ranges. You can also use the HTTP header filter settings and forwarding settings. A valid IP range uses these formats: *x.x.x.x/x* or *x.x.x.x-x.x.x.x*
 
    For more information, see [Blocking inbound IP addresses in Azure Logic Apps (Standard)](https://www.serverlessnotes.com/docs/block-inbound-ip-addresses-in-azure-logic-apps-standard).
 
@@ -979,13 +981,15 @@ In the Azure portal, IP address restriction affects both triggers *and* actions,
 
 ##### Standard workflows
 
-1. In the [Azure portal](https://portal.azure.com), open your logic app resource.
+1. In the [Azure portal](https://portal.azure.com), open your Standard logic app resource.
 
 1. On the logic app menu, under **Settings**, select **Networking**.
 
-1. In the **Inbound Traffic** section, select **Access restriction**.
+1. In the **Inbound traffic configuration** section, next to **Public network access**, select **Enabled with no access restriction**.
+
+1. On the **Access restrictions** page, under **App access**, select **Enabled from select virtual networks and IP addresses**.
 
-1. Create one or more rules to either **Allow** or **Deny** requests from specific IP ranges. You can also use the HTTP header filter settings and forwarding settings. A valid IP range uses these formats: *x.x.x.x/x* or *x.x.x.x-x.x.x.x*
+1. Under **Site access and rules**, on the **Main site** tab, add one or more rules to either **Allow** or **Deny** requests from specific IP ranges. A valid IP range uses these formats: *x.x.x.x/x* or *x.x.x.x-x.x.x.x*
 
    For more information, see [Blocking inbound IP addresses in Azure Logic Apps (Standard)](https://www.serverlessnotes.com/docs/block-inbound-ip-addresses-in-azure-logic-apps-standard).