Merge pull request #109169 from MicrosoftDocs/master

3/26 AM Publish

Author: huypub

.openpublishing.redirection.json

@@ -50402,6 +50402,10 @@
     {
       "source_path": "articles/cognitive-services/Speech-Service/quickstart-voice-assistant-csharp-uwp.md",
       "redirect_url": "/azure/cognitive-services/speech-service/quickstarts/voice-assistants?pivots=programming-language-csharp&tabs=uwp"
+    },
+    {
+      "source_path": "articles/load-balancer/use-existing-lb-vmss-cli.md",
+      "redirect_url": "/azure/load-balancer/configure-vm-scale-set-cli"
     }
   ]
 }

articles/active-directory/app-provisioning/use-scim-to-provision-users-and-groups.md

@@ -100,7 +100,7 @@ In ASP.NET Core, these settings are located in the [appsettings.json](https://gi
 }
 ```
 
-In ASP.NET Core, another file ([properties\launchSettings.json](https://github.com/Azure-Samples/active-directory-aspnetcore-webapp-openidconnect-v2/blob/bc564d68179c36546770bf4d6264ce72009bc65a/1-WebApp-OIDC/1-1-MyOrg/Properties/launchSettings.json#L6-L7)) contains the URL (`applicationUrl`) and the SSL port (`sslPort`) for your application and various profiles.
+In ASP.NET Core, another file ([properties\launchSettings.json](https://github.com/Azure-Samples/active-directory-aspnetcore-webapp-openidconnect-v2/blob/bc564d68179c36546770bf4d6264ce72009bc65a/1-WebApp-OIDC/1-1-MyOrg/Properties/launchSettings.json#L6-L7)) contains the URL (`applicationUrl`) and the TLS/SSL port (`sslPort`) for your application and various profiles.
 
 ```Json
 {

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

@@ -66,6 +66,9 @@ If your application is a native client, the implicit flow isn’t a great fit. T
 
 If you are developing a Web application that includes a backend, and consuming an API from its backend code, the implicit flow is also not a good fit. Other grants give you far more power. For example, the OAuth2 client credentials grant provides the ability to obtain tokens that reflect the permissions assigned to the application itself, as opposed to user delegations. This means the client has the ability to maintain programmatic access to resources even when a user is not actively engaged in a session, and so on. Not only that, but such grants give higher security guarantees. For instance, access tokens never transit through the user browser, they don’t risk being saved in the browser history, and so on. The client application can also perform strong authentication when requesting a token.
 
+[OAuth2-Spec-Implicit-Misuse]: https://tools.ietf.org/html/rfc6749#section-10.16
+[OAuth2-Threat-Model-And-Security-Implications]: https://tools.ietf.org/html/rfc6819
+
 ## Protocol diagram
 
 The following diagram shows what the entire implicit sign-in flow looks like and the sections that follow describe each step in more detail.

articles/active-directory/develop/v2-oauth2-implicit-grant-flow.md

@@ -55,7 +55,6 @@ To configure the integration of monday.com into Azure AD, you need to add monday
 1. In the **Add from the gallery** section, type **monday.com** in the search box.
 1. Select **monday.com** from results panel and then add the app. Wait a few seconds while the app is added to your tenant.
 
-
 ## Configure and test Azure AD single sign-on for monday.com
 
 Configure and test Azure AD SSO with monday.com using a test user called **B.Simon**. For SSO to work, you need to establish a link relationship between an Azure AD user and the related user in monday.com.
@@ -81,50 +80,50 @@ Follow these steps to enable Azure AD SSO in the Azure portal.
 
 1. On the **Basic SAML Configuration** section, if you have **Service Provider metadata file** and wish to configure in **IDP** initiated mode, perform the following steps:
 
-	a. Click **Upload metadata file**.
+    a. Click **Upload metadata file**.
 
     ![Upload metadata file](common/upload-metadata.png)
 
-	b. Click on **folder logo** to select the metadata file and click **Upload**.
+    b. Click on **folder logo** to select the metadata file and click **Upload**.
 
-	![choose metadata file](common/browse-upload-metadata.png)
+    ![choose metadata file](common/browse-upload-metadata.png)
 
-	c. After the metadata file is successfully uploaded, the **Identifier** and **Reply URL** values get auto populated in Basic SAML Configuration section.
+    c. After the metadata file is successfully uploaded, the **Identifier** and **Reply URL** values get auto populated in Basic SAML Configuration section.
 
-	![image](common/idp-intiated.png)
+    ![image](common/idp-intiated.png)
 
-	> [!Note]
-	> If the **Identifier** and **Reply URL** values do not get populated automatically, then fill in the values manually. The **Identifier** and the **Reply URL** are the same and value is in the following pattern: `https://<your-domain>.monday.com/saml/saml_callback`
+    > [!Note]
+    > If the **Identifier** and **Reply URL** values do not get populated automatically, then fill in the values manually. The **Identifier** and the **Reply URL** are the same and value is in the following pattern: `https://<your-domain>.monday.com/saml/saml_callback`
 
 1. Click **Set additional URLs** and perform the following step if you wish to configure the application in **SP** initiated mode:
 
-	![image](common/metadata-upload-additional-signon.png)
+    ![image](common/metadata-upload-additional-signon.png)
 
-	In the **Sign-on URL** text box, type a URL using the following pattern:
+    In the **Sign-on URL** text box, type a URL using the following pattern:
     `https://<YOUR_DOMAIN>.monday.com`
 
-	> [!NOTE]
-    > These values are not real. Update these values with the actual Identifier, Reply URL and Sign-On URL. Contact [monday.com Client support team](mailto:[email protected]) to get these values. You can also refer to the patterns shown in the **Basic SAML Configuration** section in the Azure portal.
+    > [!NOTE]
+    > These values are not real. Update these values with the actual Identifier, Reply URL and Sign-On URL. Contact [monday.com Client support team](https://monday.com/contact-us/) to get these values. You can also refer to the patterns shown in the **Basic SAML Configuration** section in the Azure portal.
 
 1. monday.com application expects the SAML assertions in a specific format, which requires you to add custom attribute mappings to your SAML token attributes configuration. The following screenshot shows the list of default attributes.
 
-	![image](common/default-attributes.png)
+    ![image](common/default-attributes.png)
 
 1. In addition to above, monday.com application expects few more attributes to be passed back in SAML response which are shown below. These attributes are also pre populated but you can review them as per your requirements.
 
-    | Name | Source Attribute|
-	| ---------------| --------------- |
-	| Email | user.mail |
+    | Name | Source Attribute |
+    |--|--|
+    | Email | user.mail |
     | FirstName | user.givenname |
     | LastName | user.surname |
 
 1. On the **Set up single sign-on with SAML** page, in the **SAML Signing Certificate** section,  find **Certificate (Base64)** and select **Download** to download the certificate and save it on your computer.
 
-	![The Certificate download link](common/certificatebase64.png)
+    ![The Certificate download link](common/certificatebase64.png)
 
 1. On the **Set up monday.com** section, copy the appropriate URL(s) based on your requirement.
 
-	![Copy configuration URLs](common/copy-configuration-urls.png)
+    ![Copy configuration URLs](common/copy-configuration-urls.png)
 
 ### Create an Azure AD test user
 
@@ -133,7 +132,7 @@ In this section, you'll create a test user in the Azure portal called B.Simon.
 1. From the left pane in the Azure portal, select **Azure Active Directory**, select **Users**, and then select **All users**.
 1. Select **New user** at the top of the screen.
 1. In the **User** properties, follow these steps:
-   1. In the **Name** field, enter `B.Simon`.  
+   1. In the **Name** field, enter `B.Simon`.
    1. In the **User name** field, enter the [email protected]. For example, `[email protected]`.
    1. Select the **Show password** check box, and then write down the value that's displayed in the **Password** box.
    1. Click **Create**.
@@ -150,7 +149,7 @@ In this section, you'll enable B.Simon to use Azure single sign-on by granting a
 
 1. Select **Add user**, then select **Users and groups** in the **Add Assignment** dialog.
 
-	![The Add User link](common/add-assign-user.png)
+    ![The Add User link](common/add-assign-user.png)
 
 1. In the **Users and groups** dialog, select **B.Simon** from the Users list, then click the **Select** button at the bottom of the screen.
 1. If you're expecting any role value in the SAML assertion, in the **Select Role** dialog, select the appropriate role for the user from the list and then click the **Select** button at the bottom of the screen.
@@ -160,17 +159,17 @@ In this section, you'll enable B.Simon to use Azure single sign-on by granting a
 
 1. To automate the configuration within monday.com, you need to install **My Apps Secure Sign-in browser extension** by clicking **Install the extension**.
 
-	![My apps extension](common/install-myappssecure-extension.png)
+    ![My apps extension](common/install-myappssecure-extension.png)
 
 1. After adding extension to the browser, click on **Setup monday.com** which will direct you to the monday.com application. From there, provide the admin credentials to sign into monday.com. The browser extension will automatically configure the application for you and automate steps 3-6.
 
-	![Setup configuration](common/setup-sso.png)
+    ![Setup configuration](common/setup-sso.png)
 
 1. If you want to setup monday.com manually, open a new web browser window and sign in to monday.com as an administrator and perform the following steps:
 
 1. Go to the **Profile** on the top right corner of page and click on **Admin**.
 
-	![monday.com configuration](./media/mondaycom-tutorial/configuration01.png)
+    ![monday.com configuration](./media/mondaycom-tutorial/configuration01.png)
 
 1. Select **Security** and make sure to click on **Open** next to SAML.
 
@@ -180,8 +179,8 @@ In this section, you'll enable B.Simon to use Azure single sign-on by granting a
 
     ![monday.com configuration](./media/mondaycom-tutorial/configuration03.png)
 
-	>[!NOTE]
-	>For more details refer [this](https://support.monday.com/hc/articles/360000460605-SAML-Single-Sign-on?abcb=34642) article
+    > [!NOTE]
+    > For more details refer [this](https://support.monday.com/hc/articles/360000460605-SAML-Single-Sign-on?abcb=34642) article
 
 ### Create monday.com test user
 
@@ -195,10 +194,10 @@ When you click the monday.com tile in the Access Panel, you should be automatica
 
 ## Additional resources
 
-- [ List of Tutorials on How to Integrate SaaS Apps with Azure Active Directory ](https://docs.microsoft.com/azure/active-directory/active-directory-saas-tutorial-list)
+- [List of Tutorials on How to Integrate SaaS Apps with Azure Active Directory](https://docs.microsoft.com/azure/active-directory/active-directory-saas-tutorial-list)
 
-- [What is application access and single sign-on with Azure Active Directory? ](https://docs.microsoft.com/azure/active-directory/active-directory-appssoaccess-whatis)
+- [What is application access and single sign-on with Azure Active Directory?](https://docs.microsoft.com/azure/active-directory/active-directory-appssoaccess-whatis)
 
 - [What is conditional access in Azure Active Directory?](https://docs.microsoft.com/azure/active-directory/conditional-access/overview)
 
-- [Try monday.com with Azure AD](https://aad.portal.azure.com/)
+- [Try monday.com with Azure AD](https://aad.portal.azure.com/)

articles/active-directory/saas-apps/mondaycom-tutorial.md

@@ -27,7 +27,7 @@ A storage class is used to define how an Azure file share is created. A storage
 
 * *Standard_LRS* - standard locally redundant storage (LRS)
 * *Standard_GRS* - standard geo-redundant storage (GRS)
-* *Standard_ZRS* - standard zone redundant storage (GRS)
+* *Standard_ZRS* - standard zone redundant storage (ZRS)
 * *Standard_RAGRS* - standard read-access geo-redundant storage (RA-GRS)
 * *Premium_LRS* - premium locally redundant storage (LRS)
 * *Premium_ZRS* - premium zone redundant storage (GRS)

articles/aks/azure-files-dynamic-pv.md

@@ -59,8 +59,8 @@ The sample project contains a basic CRUD (create-read-update-delete) app using [
 Run the following commands to install the required packages, run database migrations, and start the application.
 
 ```bash
-dotnet restore
-dotnet ef database update
+dotnet tool install -g dotnet-ef --version 3.1.1
+dotnet-ef database update
 dotnet run
 ```
 

articles/app-service/app-service-web-tutorial-dotnetcore-sqldb.md

@@ -31,6 +31,11 @@
     - name: Manage Azure Automation data
       href: automation-managing-data.md
       displayName: backup
+    - name: Troubleshoot
+      items:  
+        - name: Automation account troubleshooting
+          href: troubleshoot/automation-account.md
+          displayName: troubleshoot
 - name: Process Automation
   items:
   - name: Hybrid Runbook Worker Overview

articles/automation/TOC.yml

@@ -0,0 +1,50 @@
+---
+title: Automation account troubleshooting
+description: Learn how to troubleshoot and resolve issues with an Azure account.
+services: automation
+author: mgoedtel
+ms.author: magoedte
+ms.date: 03/24/2020
+ms.topic: conceptual
+ms.service: automation
+manager: carmonm
+---
+# Automation account troubleshooting
+
+This article discusses solutions to issues that you might encounter when you use an Automation account. The following sections highlight specific error messages and possible resolutions for each. For general information about Automation accounts, see [Create an Azure account](../automation-quickstart-create-account.md).
+
+## <a name="rp-register"></a>Scenario: Unable to register Automation Resource Provider for subscriptions
+
+### Issue
+
+When you work with management solutions in your Automation account, you encounter the following error:
+
+```error
+Error details: Unable to register Automation Resource Provider for subscriptions:
+```
+
+### Cause
+
+The Automation Resource Provider isn't registered in the subscription.
+
+### Resolution
+
+To register the Automation Resource Provider, follow these steps in the Azure portal:
+
+1. From your browser, go to the [Azure portal](https://portal.azure.com).
+
+2. Navigate to **Subscriptions** and select your subscription from the Subscriptions page.   
+
+3. Under **Settings**, select **Resource Providers**.
+
+4. From the list of resource providers, verify that the **Microsoft.Automation** resource provider is registered.
+
+5. If it's not listed, register the **Microsoft.Automation** provider by following the steps at [Resolve errors for resource provider registration](/azure/azure-resource-manager/resource-manager-register-provider-errors).
+
+## Next steps
+
+If you didn't see your problem or can't resolve your issue, try one of the following channels for additional support:
+
+* Get answers from Azure experts through [Azure Forums](https://azure.microsoft.com/support/forums/).
+* Connect with [@AzureSupport](https://twitter.com/azuresupport), the official Microsoft Azure account for improving customer experience by connecting the Azure community to the right resources: answers, support, and experts.
+* File an Azure support incident. Go to the [Azure support site](https://azure.microsoft.com/support/options/) and select **Get Support**.

articles/automation/troubleshoot/automation-account.md

@@ -222,5 +222,5 @@ If you have a set of coordinate locations to reverse geocode, you can use [Post
 
 ## Next steps
 
-- Explore the [Azure Maps search service](https://docs.microsoft.com/rest/api/maps/search) API documentation.
-- Learn about [Best practices](https://docs.microsoft.com/azure/azure-maps/how-to-use-best-practices-for-search).
+- Explore the [Azure Maps Search Service REST API documentation](https://docs.microsoft.com/rest/api/maps/search).
+- Learn about [Azure Maps Search Service best practices](https://docs.microsoft.com/azure/azure-maps/how-to-use-best-practices-for-search) and how to optimize your queries.