Merging changes synced from https://github.com/MicrosoftDocs/azure-docs-pr (branch live)

Author: Learn Build Service GitHub App

articles/app-service/media/webjobs-sdk-get-started/select-search.png

@@ -299,8 +299,6 @@ To attach a remote debugger to a function app running in a process separate from
 
 1. Again from the **Publish** tab, select the ellipses (**...**) in the **Hosting** section, and then choose **Attach debugger**.  
 
-    :::image type="content" source="media/functions-develop-vs/attach-to-process-in-process.png" alt-text="Screenshot of attaching the debugger from Visual Studio.":::
-
     Visual Studio connects to your function app and enables remote debugging, if not already enabled. 
     
     > [!NOTE]
@@ -328,8 +326,6 @@ To attach a remote debugger to a function app running in-process with the Functi
 
 + From the **Publish** tab, select the ellipses (**...**) in the **Hosting** section, and then choose **Attach debugger**.  
 
-    :::image type="content" source="media/functions-develop-vs/attach-to-process-in-process.png" alt-text="Screenshot of attaching the debugger from Visual Studio.":::
-
 Visual Studio connects to your function app and enables remote debugging, if not already enabled. It also locates and attaches the debugger to the host process for the app. At this point, you can debug your function app as normal. 
 ::: zone-end  
 

articles/azure-functions/durable/media/durable-functions-configure-df-with-credentials/durable-functions-managed-identity-scenario-03.png

@@ -137,17 +137,11 @@ Now, you can run the function. But first, check in the portal and see what outbo
 
 1. In your function app, select **Properties** and review the **Outbound IP Addresses** field.
 
-    ![View function app outbound IP addresses](./media/functions-how-to-use-nat-gateway/function-properties-ip.png)
-
 1. Now, return to your HTTP trigger function, select **Code + Test** and then **Test/Run**.
 
     ![Test function](./media/functions-how-to-use-nat-gateway/function-code-test.png)
 
-1. Select **Run** to execute the function, then switch to the **Output**. 
-
-    ![Test function output](./media/functions-how-to-use-nat-gateway/function-test-1-output.png)
-
-1. Verify that IP address in the HTTP response body is one of the values from the outbound IP addresses you viewed earlier.
+1. Select **Run** to execute the function, then switch to the **Output** and verify that IP address in the HTTP response body is one of the values from the outbound IP addresses you viewed earlier.
 
 Now, you can create a public IP and use a NAT gateway to modify this outbound IP address.
 

articles/azure-functions/functions-develop-vs.md

@@ -157,19 +157,13 @@ Hybrid connections are configured from the networking section of the function ap
 1. Name the setting **ContosoUserPassword**, and enter the password. Select **OK**.
 1. Select **Save** to store the password in the function application.
 
-    :::image type="content" source="./media/functions-hybrid-powershell/save-administrator-password.png" alt-text="Save the password for the administrator account." border="true":::
-
 ## Create a function HTTP trigger
 
 1. In your function app, select **Functions**, and then select **+ Add**.
 
     :::image type="content" source="./media/functions-hybrid-powershell/create-http-trigger-function.png" alt-text="Create new HTTP trigger." border="true":::
 
-1. Select the **HTTP trigger** template.
-
-    :::image type="content" source="./media/functions-hybrid-powershell/select-http-trigger-template.png" alt-text="Select the HTTP trigger template." border="true":::
-
-1. Name the new function and select **Create Function**.
+1. Select the **HTTP trigger** template, name the new function, and select **Create Function**.
 
     :::image type="content" source="./media/functions-hybrid-powershell/create-new-http-function.png" alt-text="Name and create the new HTTP trigger function." border="true":::
 
@@ -210,13 +204,9 @@ Hybrid connections are configured from the networking section of the function ap
                    -SessionOption (New-PSSessionOption -SkipCACheck)
     ```
 
-1. Select **Save**.
-
-    :::image type="content" source="./media/functions-hybrid-powershell/save-http-function.png" alt-text="Change the PowerShell code and save the HTTP trigger function." border="true":::
-
- 1. Select **Test**, and then select **Run** to test the function. Review the logs to verify that the test was successful.
+1. Select **Save** to save your changes, then select **Test** > **Run** to test the function. 
 
-     :::image type="content" source="./media/functions-hybrid-powershell/test-function-hybrid.png" alt-text="Test HTTP trigger function." border="true":::
+1. Select **Logs** to review the logs and verify that the test was successful.
 
 ## Managing other systems on-premises
 

articles/azure-functions/functions-how-to-use-nat-gateway.md

@@ -44,7 +44,7 @@ You must have previously published your app to Azure. If you haven't already don
 
 1. On the **Publish** page, select the ellipses (`...`) in the **Hosting** area, and choose **Manage Azure App Service settings**. 
 
-    ![Manage App Service settings for the function app.](./media/functions-scenario-database-table-cleanup/publish-new-resource.png)
+    :::image type="content" source="./media/functions-scenario-database-table-cleanup/publish-new-resource.png" alt-text="Manage App Service settings for the function app.":::
 
 1. In **Application Settings** select **Add setting**, in **New app setting name** type `sqldb_connection`, and select **OK**.
 

articles/azure-functions/functions-hybrid-powershell.md

@@ -66,7 +66,7 @@ Older minor versions are periodically removed from Functions. For the latest new
 ::: zone pivot="programming-language-csharp"
 There's technically not a correlation between binding extension versions and the Functions runtime version. However, starting with version 4.x the Functions runtime enforces a minimum version for all trigger and binding extensions. 
 
-If you receive a warning about a package not meeting a minimum required version, you should update that NuGet package to the minimum version as you normally would. The minimum version requirements for extensions used in Functions v4.x can be found in [the linked configuration file](https://github.com/Azure/azure-functions-host/blob/v4.x/src/WebJobs.Script/extensionrequirements.json).
+If you receive a warning about a package not meeting a minimum required version, you should update that NuGet package to the minimum version as you normally would. The minimum version requirements for extensions used in Functions v4.x can be found in [the linked configuration file](https://github.com/Azure/azure-functions-host/blob/dev/src/WebJobs.Script/extensionrequirements.json).
 
 For C# script, update the extension bundle reference in the host.json as follows: