dedMerge branch 'release-functions-ux-update' of https://github.com/MicrosoftDocs/azure-docs-pr into release-functions-ux-update-dks-11

Author: dksimpson

articles/azure-functions/functions-create-vnet.md

@@ -3,7 +3,7 @@ title: Integrate Azure Functions with an Azure virtual network
 description: A step-by-step tutorial that shows you how to connect a function to an Azure virtual network
 author: alexkarcher-msft
 ms.topic: article
-ms.date: 5/03/2019
+ms.date: 4/23/2020
 ms.author: alkarche
 ms.reviewer: glenga
 #Customer intent: As an enterprise developer, I want create a function that can connect to a virtual network so that I can manage a WordPress app running on a VM in the virtual network.
@@ -57,7 +57,7 @@ Next, create a preconfigured VM that runs WordPress inside a virtual network ([W
     | Setting      | Suggested value  | Description      |
     | ------------ | ---------------- | ---------------- |
     | **Subscription** | Your subscription | The subscription under which your resources are created. | 
-    | **[Resource group](../azure-resource-manager/management/overview.md)**  | myResourceGroup | Choose `myResourceGroup`, or the resource group you created with your function app. Using the same resource group for the function app, WordPress VM, and hosting plan makes it easier to clean up resources when you are done with this tutorial. |
+    | **[Resource group](../azure-resource-manager/management/overview.md)**  | myResourceGroup | Choose `myResourceGroup`, or the resource group you created with your function app. Using the same resource group for the function app, WordPress VM, and hosting plan makes it easier to clean up resources when you're done with this tutorial. |
     | **Virtual machine name** | VNET-Wordpress | The VM name needs to be unique in the resource group |
     | **[Region](https://azure.microsoft.com/regions/)** | (Europe) West Europe | Choose a region near you or near the functions that access the VM. |
     | **Size** | B1s | Choose **Change size** and then select the B1s standard image, which has 1 vCPU and 1 GB of memory. |
@@ -96,17 +96,15 @@ You now have a WordPress site deployed entirely within your virtual network. Thi
 
 With a WordPress site running in a VM in a virtual network, you can now connect your function app to that virtual network.
 
-1. In your new function app, select **Platform features** > **Networking**.
-
-    ![Choose networking in the function app](./media/functions-create-vnet/networking-0.png)
+1. In your new function app, select **Networking** in the left menu.
 
 1. Under **VNet Integration**, select **Click here to configure**.
 
-    ![Status for configuring a network feature](./media/functions-create-vnet/Networking-1.png)
+    :::image type="content" source="./media/functions-create-vnet/networking-0.png" alt-text="Choose networking in the function app":::
 
-1. On the virtual network integration page, select **Add VNet (preview)**.
+1. On the **VNET Integration** page, select **Add VNet**.
 
-    ![Add the VNet Integration preview](./media/functions-create-vnet/networking-2.png)
+    :::image type="content" source="./media/functions-create-vnet/networking-2.png" alt-text="Add the VNet Integration preview":::
 
 1. In **Network Feature Status**, use the settings in the table below the image:
 
@@ -120,17 +118,17 @@ With a WordPress site running in a VM in a virtual network, you can now connect
     | **Virtual network address block** | 10.10.0.0/16 | Choose the same address block used by the WordPress site. You should only have one address block defined. |
     | **Address range** | 10.10.2.0/24   | The subnet size restricts the total number of instances that your Premium plan function app can scale out to. This example uses a `/24` subnet with 254 available host addresses. This subnet is over-provisioned, but easy to calculate. |
 
-1. Select **OK** to add the subnet. Close the VNet Integration and Network Feature Status pages to return to your function app page.
+1. Select **OK** to add the subnet. Close the **VNet Integration** and **Network Feature Status** pages to return to your function app page.
 
 The function app can now access the virtual network where the WordPress site is running. Next, you use [Azure Functions Proxies](functions-proxies.md) to return a file from the WordPress site.
 
 ## Create a proxy to access VM resources
 
 With VNet Integration enabled, you can create a proxy in your function app to forward requests to the VM running in the virtual network.
 
-1. In your function app, select  **Proxies** > **+**, then use the proxy settings in the table below the image:
+1. In your function app, select  **Proxies** from the left menu, and then select **Add**. Use the proxy settings in the table below the image:
 
-    ![Define the proxy settings](./media/functions-create-vnet/create-proxy.png)
+    :::image type="content" source="./media/functions-create-vnet/create-proxy.png" alt-text="Define the proxy settings":::
 
     | Setting  | Suggested value  | Description      |
     | -------- | ---------------- | ---------------- |

articles/azure-functions/functions-integrate-storage-queue-output-binding.md

@@ -4,60 +4,52 @@ description: Use Azure Functions to create a serverless function that is invoked
 
 ms.assetid: 0b609bc0-c264-4092-8e3e-0784dcc23b5d
 ms.topic: how-to
-ms.date: 09/19/2017
+ms.date: 04/24/2020
 ms.custom: mvc
 ---
 # Add messages to an Azure Storage queue using Functions
 
-In Azure Functions, input and output bindings provide a declarative way to make data from external services available to your code. In this quickstart, you use an output binding to create a message in a queue when a function is triggered by an HTTP request. You use Azure Storage Explorer to view the queue messages that your function creates:
-
-![Queue message shown in Storage Explorer](./media/functions-integrate-storage-queue-output-binding/function-queue-storage-output-view-queue.png)
+In Azure Functions, input and output bindings provide a declarative way to make data from external services available to your code. In this quickstart, you use an output binding to create a message in a queue when a function is triggered by an HTTP request. You use Azure storage container to view the queue messages that your function creates.
 
 ## Prerequisites
 
 To complete this quickstart:
 
-* Follow the directions in [Create your first function from the Azure portal](functions-create-first-azure-function.md) and don't do the **Clean up resources** step. That quickstart creates the function app and function that you use here.
+- An Azure subscription. If you don't have one, create a [free account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F) before you begin.
 
-* Install [Microsoft Azure Storage Explorer](https://storageexplorer.com/). This is a tool you'll use to examine queue messages that your output binding creates.
+- Follow the directions in [Create your first function from the Azure portal](functions-create-first-azure-function.md) and don't do the **Clean up resources** step. That quickstart creates the function app and function that you use here.
 
 ## <a name="add-binding"></a>Add an output binding
 
-In this section, you use the portal UI to add a queue storage output binding to the function you created earlier. This binding will make it possible to write minimal code to create a message in a queue. You don't have to write code for tasks such as opening a storage connection, creating a queue, or getting a reference to a queue. The Azure Functions runtime and queue output binding take care of those tasks for you.
-
-1. In the Azure portal, open the function app page for the function app that you created in [Create your first function from the Azure portal](functions-create-first-azure-function.md). To do this, select **All services > Function Apps**, and then select your function app.
-
-1. Select the function that you created in that earlier quickstart.
+In this section, you use the portal UI to add a queue storage output binding to the function you created earlier. This binding makes it possible to write minimal code to create a message in a queue. You don't have to write code for tasks such as opening a storage connection, creating a queue, or getting a reference to a queue. The Azure Functions runtime and queue output binding take care of those tasks for you.
 
-1. Select **Integrate > New Output > Azure Queue Storage**.
+1. In the Azure portal, open the function app page for the function app that you created in [Create your first function from the Azure portal](functions-create-first-azure-function.md). To do open the page, search for and select **Function App**. Then, select your function app.
 
-1. Click **Select**.
+1. Select your function app, and then select the function that you created in that earlier quickstart.
 
-    ![Add a Queue storage output binding to a function in the Azure portal.](./media/functions-integrate-storage-queue-output-binding/function-add-queue-storage-output-binding.png)
+1. Select **Integration**, and then select **+ Add output**.
 
-1. If you get an **Extensions not installed** message, choose **Install** to install the Storage bindings extension in the function app. This may take a minute or two.
+   :::image type="content" source="./media/functions-integrate-storage-queue-output-binding/function-create-output-binding.png" alt-text="Create an output binding for your function." border="true":::
 
-    ![Install the Storage binding extension](./media/functions-integrate-storage-queue-output-binding/functions-integrate-install-binding-extension.png)
-
-1. Under **Azure Queue Storage output**, use the settings as specified in the table that follows this screenshot: 
-
-    ![Add a Queue storage output binding to a function in the Azure portal.](./media/functions-integrate-storage-queue-output-binding/function-add-queue-storage-output-binding-2.png)
+1. Select the **Azure Queue Storage** binding type, and add the settings as specified in the table that follows this screenshot: 
 
+    :::image type="content" source="./media/functions-integrate-storage-queue-output-binding/function-create-output-binding-details.png" alt-text="Add a Queue storage output binding to a function in the Azure portal." border="true":::
+    
     | Setting      |  Suggested value   | Description                              |
     | ------------ |  ------- | -------------------------------------------------- |
     | **Message parameter name** | outputQueueItem | The name of the output binding parameter. | 
+    | **Queue name**   | outqueue  | The name of the queue to connect to in your Storage account. |
     | **Storage account connection** | AzureWebJobsStorage | You can use the storage account connection already being used by your function app, or create a new one.  |
-    | **Queue name**   | outqueue    | The name of the queue to connect to in your Storage account. |
 
-1. Click **Save** to add the binding.
+1. Select **OK** to add the binding.
 
 Now that you have an output binding defined, you need to update the code to use the binding to add messages to a queue.  
 
 ## Add code that uses the output binding
 
 In this section, you add code that writes a message to the output queue. The message includes the value that is passed to the HTTP trigger in the query string. For example, if the query string includes `name=Azure`, the queue message will be *Name passed to the function: Azure*.
 
-1. Select your function to display the function code in the editor.
+1. In your function, select **Code + Test** to display the function code in the editor.
 
 1. Update the function code depending on your function language:
 
@@ -94,54 +86,40 @@ In this section, you add code that writes a message to the output queue. The mes
 
 ## Test the function
 
-1. After the code changes are saved, select **Run**. 
+1. After the code changes are saved, select **Test**.
+1. Confirm that your test matches the image below and select **Run**. 
 
-    ![Add a Queue storage output binding to a function in the Azure portal.](./media/functions-integrate-storage-queue-output-binding/functions-test-run-function.png)
+    :::image type="content" source="./media/functions-integrate-storage-queue-output-binding/functions-test-run-function.png" alt-text="Test the queue storage binding in the Azure portal." border="true":::
 
     Notice that the **Request body** contains the `name` value *Azure*. This value appears in the queue message that is created when the function is invoked.
 
     As an alternative to selecting **Run** here, you can call the function by entering a URL in a browser and specifying the `name` value in the query string. The browser method is shown in the [previous quickstart](functions-create-first-azure-function.md#test-the-function).
 
-2. Check the logs to make sure that the function succeeded. 
+1. Check the logs to make sure that the function succeeded. 
 
-A new queue named **outqueue** is created in your Storage account by the Functions runtime when the output binding is first used. You'll use Storage Explorer to verify that the queue and a message in it were created.
+A new queue named **outqueue** is created in your Storage account by the Functions runtime when the output binding is first used. You'll use storage account to verify that the queue and a message in it were created.
 
-### Connect Storage Explorer to your account
+### Find the storage account connected to AzureWebJobsStorage
 
-Skip this section if you have already installed Storage Explorer and connected it to the storage account that you're using with this quickstart.
 
-1. Run the [Microsoft Azure Storage Explorer](https://storageexplorer.com/) tool, select the connect icon on the left, choose **Use a storage account name and key**, and select **Next**.
+1. Go to your function app and select **Configuration**.
 
-    ![Run the Storage Account Explorer tool.](./media/functions-integrate-storage-queue-output-binding/functions-storage-manager-connect-1.png)
+1. Under **Application settings**, select **AzureWebJobsStorage**.
 
-1. In the Azure portal, on the function app page, select your function and then select **Integrate**.
+    :::image type="content" source="./media/functions-integrate-storage-queue-output-binding/function-find-storage-account.png" alt-text="Locate the storage account connected to AzureWebJobsStorage." border="true":::
 
-1. Select the **Azure Queue storage** output binding that you added in an earlier step.
+1. Locate and make note of the account name.
 
-1. Expand the **Documentation** section at the bottom of the page. 
-
-   The portal shows credentials that you can use in Storage Explorer to connect to the storage account.
-
-   ![Get the Storage account connection credentials.](./media/functions-integrate-storage-queue-output-binding/function-get-storage-account-credentials.png)
-
-1. Copy the **Account Name** value from the portal and paste it in the **Account name** box in Storage Explorer.
- 
-1. Click the show/hide icon next to **Account Key** to display the value, and then copy the **Account Key** value and paste it in the **Account key** box in Storage Explorer.
-  
-1. Select **Next > Connect**.
-
-   ![Paste the storage credentials and connect.](./media/functions-integrate-storage-queue-output-binding/functions-storage-manager-connect-2.png)
+    :::image type="content" source="./media/functions-integrate-storage-queue-output-binding/function-storage-account-name.png" alt-text="Locate the storage account connected to AzureWebJobsStorage." border="true":::
 
 ### Examine the output queue
 
-1. In Storage Explorer, select the storage account that you're using for this quickstart.
+1. In the resource group for your function app, select the storage account that you're using for this quickstart.
 
-1. Expand the **Queues** node, and then select the queue named **outqueue**. 
+1. Under **Queue service**, select **Queues** and select the queue named **outqueue**. 
 
    The queue contains the message that the queue output binding created when you ran the HTTP-triggered function. If you invoked the function with the default `name` value of *Azure*, the queue message is *Name passed to the function: Azure*.
 
-    ![Queue message shown in Storage Explorer](./media/functions-integrate-storage-queue-output-binding/function-queue-storage-output-view-queue.png)
-
 1. Run the function again, and you'll see a new message appear in the queue.  
 
 ## Clean up resources