Merge branch 'master' of https://github.com/MicrosoftDocs/azure-docs-pr into vminsights-optout

Author: ShannonLeavitt

.markdownlint.json

@@ -9,7 +9,6 @@
     "MD007": false,
     "MD009": false,
     "MD010": false,
-    "MD011": false,
     "MD012": false,
     "MD013": false,
     "MD014": false,
@@ -38,5 +37,7 @@
     "MD040": false,
     "MD041": false,
     "MD042": false,
-    "MD045": false
+    "MD045": false,
+    "MD046": false,
+    "MD047": false
 }

.openpublishing.redirection.json

@@ -135,6 +135,11 @@
       "redirect_url": "https://docs.microsoft.com/azure/architecture/topics/high-performance-computing/",
       "redirect_document_id": false
     },
+    {
+      "source_path": "articles/virtual-machines/windows/new-azvm-demo.md",
+      "redirect_url": "/azure/virtual-machines/windows/quick-create-powershell",
+      "redirect_document_id": false
+    },	
     {
       "source_path": "articles/virtual-machines/linux/high-performance-computing.md",
       "redirect_url": "https://docs.microsoft.com/azure/architecture/topics/high-performance-computing/",

articles/active-directory/develop/scenario-web-app-sign-user-app-registration.md

@@ -45,14 +45,14 @@ If you navigate to this link, you can create bootstrap the creation of your web
 1. If your account gives you access to more than one tenant, select your account in the top-right corner, and set your portal session to the desired Azure AD tenant.
 1. In the left-hand navigation pane, select the **Azure Active Directory** service, and then select **App registrations** > **New registration**.
 1. When the **Register an application** page appears, enter your application's registration information:
-   - choose the supported account types for your application (See [Supported Account types](./v2-supported-account-types.md))
-   - In the **Name** section, enter a meaningful application name that will be displayed to users of the app, for example `AspNetCore-WebApp`.
-   - In **Reply URL**, add the reply URL for your app, for instance `https://localhost:44321/`, and select **Register**.
+   1. choose the supported account types for your application (See [Supported Account types](./v2-supported-account-types.md))
+   1. In the **Name** section, enter a meaningful application name that will be displayed to users of the app, for example `AspNetCore-WebApp`.
+   1. In **Redirect URI**, add the type of application and the URI destination that will accept returned token responses after successfully authenticating. For example, `https://localhost:44321/`.  Select **Register**.
 1. Select the **Authentication** menu, and then add the following information:
-- In **Reply URL**, add `https://localhost:44321/signin-oidc`,  and select **Register**.
-- In the **Advanced settings** section, set **sign out URL** to `https://localhost:44321/signout-oidc`.
-- Under **Implicit grant**, check **ID tokens**.
-- Select **Save**.
+   1. In **Reply URL**, add `https://localhost:44321/signin-oidc`.
+   1. In the **Advanced settings** section, set **Logout URL** to `https://localhost:44321/signout-oidc`.
+   1. Under **Implicit grant**, check **ID tokens**.
+   1. Select **Save**.
 
 ### Register an app using PowerShell
 

articles/app-service/app-service-web-get-started-java.md

@@ -62,7 +62,7 @@ Then add the following plugin definition inside the `<build>` element of the `po
     <plugin>
         <groupId>com.microsoft.azure</groupId>
         <artifactId>azure-webapp-maven-plugin</artifactId>
-        <version>1.5.4</version>
+        <version>1.6.0</version>
         <configuration>
             <!-- Specify v2 schema -->
             <schemaVersion>v2</schemaVersion>
@@ -101,9 +101,9 @@ Update the following placeholders in the plugin configuration:
 | Placeholder | Description |
 | ----------- | ----------- |
 | `SUBSCRIPTION_ID` | The unique ID of the subscription you want to deploy your app to. Default subscription's ID can be found from the Cloud Shell or CLI using the `az account show` command. For all the available subscriptions, use the `az account list` command.|
-| `RESOURCEGROUP_NAME` | Name for the new resource group in which to create your app. By putting all the resources for an app in a group, you can manage them together. For example, deleting the resource group would delete all resources associated with the app. Update this value with a unique new resource group name, for example, *TestResources*. You will use this resource group name to clean up all Azure resources in a later section. |
-| `WEBAPP_NAME` | The app name will be part the host name for the app when deployed to Azure (WEBAPP_NAME.azurewebsites.net). Update this value with a unique name for the new App Service app, which will host your Java app, for example *contoso*. |
-| `REGION` | An Azure region where the app is hosted, for example `westus2`. You can get a list of regions from the Cloud Shell or CLI using the `az account list-locations` command. |
+| `RESOURCEGROUP_NAME` | Name for the new resource group in which to create your app. By putting all the resources for an app in a group, you can manage them together. For example, deleting the resource group would delete all resources associated with the app. Update this value with a unique new resource group name, for example, *myResourceGroup*. You will use this resource group name to clean up all Azure resources in a later section. |
+| `WEBAPP_NAME` | The app name will be part of the host name for the app when deployed to Azure (WEBAPP_NAME.azurewebsites.net). Update this value with a unique name for the new App Service app, which will host your Java app, for example *contoso*. |
+| `REGION` | An Azure region where the app is hosted, for example *westus2*. You can get a list of regions from the Cloud Shell or CLI using the `az account list-locations` command. |
 
 ## Deploy the app
 

articles/app-service/app-service-web-tutorial-custom-domain.md

@@ -237,7 +237,7 @@ It might take some time for the new custom domain to be reflected in the app's *
 ![A record added](./media/app-service-web-tutorial-custom-domain/a-record-added.png)
 
 > [!NOTE]
-> A **Note Secure** label for your custom domain means that it's not yet bound to an SSL certificate, and any HTTPS request from a browser to your custom domain will receive and error or warning, depending on the browser. To add an SSL binding, see [Bind an existing custom SSL certificate to Azure App Service](app-service-web-tutorial-custom-ssl.md).
+> A **Not Secure** label for your custom domain means that it's not yet bound to an SSL certificate, and any HTTPS request from a browser to your custom domain will receive and error or warning, depending on the browser. To add an SSL binding, see [Bind an existing custom SSL certificate to Azure App Service](app-service-web-tutorial-custom-ssl.md).
 
 If you missed a step or made a typo somewhere earlier, you see a verification error at the bottom of the page.
 

articles/app-service/media/app-service-diagnostics/change-analysis-default-page-11.png

@@ -99,12 +99,12 @@ Like proactive CPU monitoring, proactive auto-healing offers an easy, proactive
 
 ![Proactive auto-healing](./media/app-service-diagnostics/proactive-auto-healing-10.png)
 
-## Change analysis
+## Change analysis (only for Windows app)
 
-In a fast-paced development environment, sometimes it may be difficult to keep track of all the changes made to your app and let alone pinpoint on a change that caused an unhealthy behavior. Change analysis can help you narrow down on the changes made to your app to facilitate trouble-shooting experience. Change analysis is embedded in diagnostic report such as **Application Crashes** so you can use it concurrently with other metrics.
+In a fast-paced development environment, sometimes it may be difficult to keep track of all the changes made to your app and let alone pinpoint on a change that caused unhealthy behavior. Change analysis can help you narrow down on the changes made to your app to facilitate trouble-shooting experience. Change analysis is found in **Application Changes** and also embedded in a diagnostic report such as **Application Crashes** so you can use it concurrently with other metrics.
 
-![Change analysis default page](./media/app-service-diagnostics/change-analysis-default-page-11.png)
+Change analysis has to be enabled before using the feature. For more information on change analysis, visit [Announcing the new change analysis experience in App Service Diagnostics](https://azure.github.io/AppService/2019/05/07/Announcing-the-new-change-analysis-experience-in-App-Service-Diagnostics-Analysis.html).
 
-![Diff view](./media/app-service-diagnostics/diff-view-12.png)
+![Change analysis default page](./media/app-service-diagnostics/change-analysis-default-page-11.png)
 
-Change analysis has to be enabled before using the feature. For more information on change analysis, visit [Announcing the new change analysis experience in App Service Diagnostics](https://azure.github.io/AppService/2019/05/07/Announcing-the-new-change-analysis-experience-in-App-Service-Diagnostics-Analysis.html).
+![Diff view](./media/app-service-diagnostics/diff-view-12.png)

articles/app-service/media/app-service-diagnostics/diff-view-12.png

@@ -5,7 +5,7 @@ services: application-gateway
 author: vhorne
 ms.service: application-gateway
 ms.topic: article
-ms.date: 6/12/2019
+ms.date: 6/18/2019
 ms.author: victorh
 ---
 
@@ -128,7 +128,7 @@ To run the script:
       -sslCertificates $Certs `
       -trustedRootCertificates $trustedCert `
       -privateIpAddress "10.0.0.1" `
-      -publicIpResourceName "MyPublicIP" `
+      -publicIpResourceId "MyPublicIP" `
       -validateMigration -enableAutoScale
    ```
 

articles/app-service/overview-diagnostics.md

@@ -48,4 +48,7 @@ To learn more about storage account types, see [Introducing the Azure Storage Se
 
 ## Next steps
 
-[!INCLUDE [Functions quickstart next steps](../../includes/functions-quickstart-next-steps.md)]
+While the Azure portal makes it easy to create and try out Functions, we recommend [local development](functions-develop-local.md). After creating a function app in the portal, you still need to add a function. 
+
+> [!div class="nextstepaction"]
+> [Add an HTTP triggered function](functions-create-first-azure-function.md#create-function)