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

Author: dksimpson

articles/azure-functions/functions-add-output-binding-storage-queue-vs-code.md

@@ -29,7 +29,7 @@ Before you start this article, you must meet the following requirements:
 
 * Complete the steps in [part 1 of the Visual Studio Code quickstart](functions-create-first-function-vs-code.md). 
 
-This article assumes that you are already signed in to your Azure subscription from Visual Studio Code. You can sign in by running `Azure: Sign In` from the command palette. 
+This article assumes that you're already signed in to your Azure subscription from Visual Studio Code. You can sign in by running `Azure: Sign In` from the command palette. 
 
 ## Download the function app settings
 
@@ -46,13 +46,13 @@ In the [previous quickstart article](functions-create-first-function-vs-code.md)
 
 ## Register binding extensions
 
-Because you are using a Queue storage output binding, you must have the Storage bindings extension installed before you run the project. 
+Because you're using a Queue storage output binding, you must have the Storage bindings extension installed before you run the project. 
 
 ::: zone pivot="programming-language-javascript,programming-language-typescript,programming-language-python,programming-language-powershell,programming-language-java"
 
 Your project has been configured to use [extension bundles](functions-bindings-register.md#extension-bundles), which automatically installs a predefined set of extension packages. 
 
-Extension bundles is enabled in the host.json file at the root of the project, which looks like the following:
+Extension bundles usage is enabled in the host.json file at the root of the project, which appears as follows:
 
 :::code language="json" source="~/functions-quickstart-java/functions-add-output-binding-storage-queue/host.json":::
 
@@ -184,7 +184,7 @@ Now, it's time to republish the updated function app to Azure.
 
 1. In Visual Studio Code, press F1 to open the command palette. In the command palette, search for and select `Azure Functions: Deploy to function app...`.
 
-1. Choose the function app that you created in the first article. Because you are redeploying your project to the same app, select **Deploy** to dismiss the warning about overwriting files.
+1. Choose the function app that you created in the first article. Because you're redeploying your project to the same app, select **Deploy** to dismiss the warning about overwriting files.
 
 1. After deployment completes, you can again use cURL or a browser to test the redeployed function. As before, append the query string `&name=<yourname>` to the URL, as in the following example:
 
@@ -196,7 +196,7 @@ Now, it's time to republish the updated function app to Azure.
 
 ## Clean up resources
 
-*Resources* in Azure refers to function apps, functions, storage accounts, and so forth. They are grouped into *resource groups*, and you can delete everything in a group by deleting the group.
+In Azure, *resources* refer to function apps, functions, storage accounts, and so forth. They're grouped into *resource groups*, and you can delete everything in a group by deleting the group.
 
 You created resources to complete these quickstarts. You may be billed for these resources, depending on your [account status](https://azure.microsoft.com/account/) and [service pricing](https://azure.microsoft.com/pricing/). If you don't need the resources anymore, here's how to delete them:
 

articles/azure-functions/functions-how-to-github-actions.md

@@ -3,7 +3,7 @@ title: Use GitHub Actions to make code updates in Azure Functions
 description: Learn how to use GitHub Actions to define a workflow to build and deploy Azure Functions projects in GitHub.
 author: craigshoemaker
 ms.topic: conceptual
-ms.date: 09/16/2019
+ms.date: 04/16/2020
 ms.author: cshoe
 ---
 
@@ -34,29 +34,31 @@ You can create a [service principal](../active-directory/develop/app-objects-and
 az ad sp create-for-rbac --name "myApp" --role contributor --scopes /subscriptions/<SUBSCRIPTION_ID>/resourceGroups/<RESOURCE_GROUP>/providers/Microsoft.Web/sites/<APP_NAME> --sdk-auth
 ```
 
-In this example, replace the placeholders in the resource with your subscription ID, resource group, and function app name. The output is the role assignment credentials that provides access to your function app. Copy this JSON object, which you can use to authenticate from GitHub.
+In this example, replace the placeholders in the resource with your subscription ID, resource group, and function app name. The output is the role assignment credentials that provide access to your function app. Copy this JSON object, which you can use to authenticate from GitHub.
 
 > [!IMPORTANT]
 > It is always a good practice to grant minimum access. This is why the scope in the previous example is limited to the specific function app and not the entire resource group.
 
 ## Download the publishing profile
 
-You can download the publishing profile of your function app, by going to the **Overview** page of your app and clicking **Get publish profile**.
+To download the publishing profile of your function app:
 
-   ![Download publish profile](media/functions-how-to-github-actions/get-publish-profile.png)
+1. Select the function app's **Overview** page, and then select **Get publish profile**.
 
-Copy the content of the file.
+   :::image type="content" source="media/functions-how-to-github-actions/get-publish-profile.png" alt-text="Download publish profile":::
+
+1. Save and copy the contents of the publish settings file.
 
 ## Configure the GitHub secret
 
 1. In [GitHub](https://github.com), browse to your repository, select **Settings** > **Secrets** > **Add a new secret**.
 
-   ![Add Secret](media/functions-how-to-github-actions/add-secret.png)
+   :::image type="content" source="media/functions-how-to-github-actions/add-secret.png" alt-text="Add Secret":::
 
 1. Add a new secret.
 
-   * If you're using the service principal that you created by using the Azure CLI, use `AZURE_CREDENTIALS` for the **Name**. Then paste the copied JSON object output for **Value**, and select **Add secret**.
-   * If you're using a publishing profile, use `SCM_CREDENTIALS` for the **Name**. Then use the publishing profile's file content for **Value**, and select **Add secret**.
+   * If you're using the service principal that you created by using the Azure CLI, use `AZURE_CREDENTIALS` for the **Name**. Then, paste the copied JSON object output for **Value**, and select **Add secret**.
+   * If you're using a publishing profile, use `SCM_CREDENTIALS` for the **Name**. Then, use the publishing profile's file content for **Value**, and select **Add secret**.
 
 GitHub can now authenticate to your function app in Azure.
 
@@ -212,7 +214,7 @@ The following example uses version 1 of the `functions-action`:
 
 ## Next steps
 
-To view a complete workflow .yaml, see one of the files in the [Azure GitHub Actions workflow samples repo](https://aka.ms/functions-actions-samples) that have `functionapp` in the name. You can use these samples a starting point for your workflow.
+To view a complete workflow .yaml file, see one of the files in the [Azure GitHub Actions workflow samples repo](https://aka.ms/functions-actions-samples) that have `functionapp` in the name. You can use these samples a starting point for your workflow.
 
 > [!div class="nextstepaction"]
 > [Learn more about GitHub Actions](https://help.github.com/en/articles/about-github-actions)

articles/azure-functions/functions-monitor-log-analytics.md

@@ -3,7 +3,7 @@ title: Monitoring Azure Functions with Azure Monitor Logs
 description: Learn how to use Azure Monitor Logs with Azure Functions to monitor function executions.
 author: craigshoemaker
 ms.topic: conceptual
-ms.date: 10/09/2019
+ms.date: 04/15/2020
 ms.author: cshoe
 # Customer intent: As a developer, I want to monitor my functions so I can know if they're running correctly.
 ---
@@ -21,17 +21,23 @@ Azure Monitor uses a version of the [Kusto query language](/azure/kusto/query/)
 
 ## Setting up
 
-From the **Monitoring** section, select **Diagnostic settings** and then click **Add diagnostic setting**.
+1. From the **Monitoring** section of your function app in the [Azure portal](https://portal.azure.com), select **Diagnostic settings**, and then select **Add diagnostic setting**.
 
-![Add a diagnostic setting](media/functions-monitor-log-analytics/diagnostic-settings-add.png)
+   :::image type="content" source="media/functions-monitor-log-analytics/diagnostic-settings-add.png" alt-text="Select diagnostic settings":::
 
-In the **Diagnostics settings** page, choose **Send to Log Analytics**, and then select your Log Analytics workspace. Under **log** choose **FunctionAppLogs**, this table contains the desired logs.
+1. In the **Diagnostics settings** page, under **Category details** and **log**, choose **FunctionAppLogs**.
 
-![Add a diagnostic setting](media/functions-monitor-log-analytics/choose-table.png)
+   The **FunctionAppLogs** table contains the desired logs.
+
+1. Under **Destination details**, choose **Send to Log Analytics**.and then select your **Log Analytics workspace**. 
+
+1. Enter a **Diagnostic settings name**, and then select **Save**.
+
+   :::image type="content" source="media/functions-monitor-log-analytics/choose-table.png" alt-text="Add a diagnostic setting":::
 
 ## User-generated logs
 
-To generate custom logs, you can use the specific logging statement depending on your language, here are sample code snippets:
+To generate custom logs, use the logging statement specific to your language. Here are sample code snippets:
 
 
 # [C#](#tab/csharp)
@@ -68,11 +74,19 @@ logging.info('My app logs here.')
 
 ## Querying the logs
 
-To query the generated logs, go to the Log Analytics workspace that you configured to send the function logs to and click **Logs**.
+To query the generated logs:
+ 
+1. From your function app, select **Diagnostic settings**. 
+
+1. From the **Diagnostic settings** list, select the Log Analytics workspace that you configured to send the function logs to. 
+
+1. From the **Log Analytics workspace** page, select **Logs**.
+
+   Azure Functions writes all logs to the **FunctionAppLogs** table under **LogManagement**. 
 
-![Query window in LA workspace](media/functions-monitor-log-analytics/querying.png)
+   :::image type="content" source="media/functions-monitor-log-analytics/querying.png" alt-text="Query window in Log Analytics workspace":::
 
-Azure Functions writes all logs to **FunctionAppLogs** table, here are some sample queries.
+Here are some sample queries:
 
 ### All logs
 
@@ -83,7 +97,7 @@ FunctionAppLogs
 
 ```
 
-### A specific function logs
+### Specific function logs
 
 ```
 
@@ -104,6 +118,6 @@ FunctionAppLogs
 
 ## Next steps
 
-- Review the [Azure Functions overview](functions-overview.md)
-- Learn more about [Azure Monitor Logs](../azure-monitor/platform/data-platform-logs.md)
+- Review the [Azure Functions overview](functions-overview.md).
+- Learn more about [Azure Monitor Logs](../azure-monitor/platform/data-platform-logs.md).
 - Learn more about the [query language](../azure-monitor/log-query/get-started-queries.md).