Merge pull request #92788 from MicrosoftDocs/master

10/22 AM Publish

Author: huypub

articles/active-directory-domain-services/tutorial-create-instance.md

@@ -115,7 +115,7 @@ On the **Summary** page of the wizard, review the configuration settings for the
 
     ![Domain Services status once successfully provisioned](./media/tutorial-create-instance/successfully-provisioned.png)
 
-During the provisioning process, Azure AD DS creates two Enterprise Applications named *Domain Controller Services* and *AzureActiveDirectoryDomainControllerServices* in your directory. These Enterprise Applications are needed to service your managed domain. It's imperative that these applications are not deleted at any time.
+We provision Azure AD Domain Services on the Azure Active Directory tenant and the Azure AD Domain Services resource for the service is created within the associated Azure subscription. During the provisioning process, Azure AD DS creates two Enterprise Applications named *Domain Controller Services* and *AzureActiveDirectoryDomainControllerServices* in your Azure Active directory instance where you have enabled the Azure AD domain services. These Enterprise Applications are needed to service your managed domain.  It's imperative that these applications are not deleted at any time.
 
 ## Update DNS settings for the Azure virtual network
 

articles/active-directory/manage-apps/application-provisioning-config-how-to.md

@@ -22,15 +22,15 @@ ms.collection: M365-identity-device-management
 
 # How to configure user provisioning to an Azure AD Gallery application
 
-*User account provisioning* is the act of creating, updating, and/or disabling user account records in an application’s local user profile store. Most cloud and SaaS applications store the users role and permissions in their own local user profile store, and presence of such a user record in their local store is *required* for single sign-on and access to work.
+*User account provisioning* is the act of creating, updating, and/or disabling user account records in an application’s local user profile store. Most cloud and SaaS applications store the users role and permissions in the user's own local user profile store, and presence of such a user record in the user's local store is *required* for single sign-on and access to work.
 
 In the Azure portal, the **Provisioning** tab in the left navigation pane for an Enterprise App displays what provisioning modes are supported for that app. This can be one of two values:
 
 ## Configuring an application for Manual Provisioning
 
-*Manual* provisioning means that user accounts must be created manually using the methods provided by that app. This could mean logging into an administrative portal for that app and adding users using a web-based user interface. Or it could be uploading a spreadsheet with user account detail, using a mechanism provided by that application. Consult the documentation provided by the app, or contact the app developer to determine wat mechanisms are available.
+*Manual* provisioning means that user accounts must be created manually using methods provided by the app. This could mean logging into an administrative portal for that app and adding users using a web-based user interface. Or it could be uploading a spreadsheet with user account detail, using a mechanism provided by that application. Consult the documentation provided by the app, or contact the app developer to determine what mechanisms are available.
 
-If Manual is the only mode shown for a given application, it means that no automatic Azure AD provisioning connector has been created for the app yet. Or it means the app does not support the pre-requisite user management API upon which to build an automated provisioning connector.
+If *Manual* is the only mode shown for a given application, it means that there is no automatic Azure AD provisioning connector for the app yet. Or it means the app does not support the pre-requisites for Microsoft's user management API, which is used to build an automated provisioning connector.
 
 If you would like to request support for automatic provisioning for a given app, you can fill out a request using the [Azure Active Directory Application Requests](https://aka.ms/aadapprequest).
 
@@ -40,16 +40,14 @@ If you would like to request support for automatic provisioning for a given app,
 
 For more information on how to provision specific users and groups to an application, see [Managing user account provisioning for enterprise apps](https://docs.microsoft.com/azure/active-directory/active-directory-enterprise-apps-manage-provisioning).
 
-The actual steps required to enable and configure automatic provisioning vary depending on the application.
+The actual steps required to enable and configure automatic provisioning varies depending on the application.
 
->[!NOTE]
->You should start by finding the setup tutorial specific to setting up provisioning for your application, and following those steps to configure both the app and Azure AD to create the provisioning connection. 
->
->
+> [!NOTE]
+> You should start by finding the setup tutorial specific to setting up provisioning for your application, and following those steps to configure both the app and Azure AD to create the provisioning connection. 
 
 App tutorials can be found at [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).
 
-An important thing to consider when setting up provisioning be to review and configure the attribute mappings and workflows that define which user (or group) properties flow from Azure AD to the application. This includes setting the “matching property” that be used to uniquely identify and match users/groups between the two systems. For more information on this important process.
+An important thing to consider when setting up provisioning is to review and configure the attribute mappings and workflows that define which user (or group) properties flow from Azure AD to the application. This includes setting the “matching property” that is used to uniquely identify and match users/groups between the two systems. See the link in *Next Steps* for more information on attribute mappings.
 
 ## Next steps
 [Customizing User Provisioning Attribute Mappings for SaaS Applications in Azure Active Directory](https://docs.microsoft.com/azure/active-directory/active-directory-saas-customizing-attribute-mappings)

articles/app-service/app-service-web-get-started-dotnet-framework.md

@@ -4,15 +4,14 @@ description: Learn how to run web apps in Azure App Service by deploying the def
 services: app-service\web
 documentationcenter: ''
 author: cephalin
-manager: cfowler
-editor: ''
+manager: gwallace
 
 ms.assetid: 04a1becf-7756-4d4e-92d8-d9471c263d23
 ms.service: app-service-web
 ms.workload: web
 ms.tgt_pltfrm: na
 ms.topic: quickstart
-ms.date: 08/30/2019
+ms.date: 10/21/2019
 ms.author: cephalin
 ms.custom: mvc, devcenter
 ms.custom: seodec18
@@ -41,27 +40,27 @@ Create an ASP.NET web app by following these steps:
 
 1. Open Visual Studio and then select **Create a new project**.
 
-1. In **Create a new project**, find and choose **ASP.NET Web Application (.NET Framework)** for C#, then select **Next**.
+2. In **Create a new project**, find and choose **ASP.NET Web Application (.NET Framework)**, then select **Next**.
 
-1. In **Configure your new project**, name the application _myFirstAzureWebApp_, and then select **Create**.
+3. In **Configure your new project**, name the application _myFirstAzureWebApp_, and then select **Create**.
 
    ![Configure your web app project](./media/app-service-web-get-started-dotnet-framework/configure-web-app-project-framework.png)
 
-1. You can deploy any type of ASP.NET web app to Azure. For this quickstart, choose the **MVC** template. 
+4. You can deploy any type of ASP.NET web app to Azure. For this quickstart, choose the **MVC** template.
 
-1. Make sure authentication is set to **No Authentication**. Select **Create**.
+5. Make sure authentication is set to **No Authentication**. Select **Create**.
 
    ![Create ASP.NET Web Application](./media/app-service-web-get-started-dotnet-framework/select-mvc-template-vs2019.png)
 
-1. From the Visual Studio menu, select **Debug** > **Start Without Debugging** to run the web app locally.
+6. From the Visual Studio menu, select **Debug** > **Start Without Debugging** to run the web app locally.
 
    ![Run app locally](./media/app-service-web-get-started-dotnet-framework/local-web-app.png)
 
 ## Publish your web app <a name="launch-the-publish-wizard"></a>
 
 1. In **Solution Explorer**, right-click the **myFirstAzureWebApp** project and select **Publish**.
 
-1. Choose **App Service** and then select **Publish**.
+1. Choose **App Service** and then change **Create profile** to **Publish**.
 
    ![Publish from project overview page](./media/app-service-web-get-started-dotnet-framework/publish-app-framework-vs2019.png)
 
@@ -96,9 +95,9 @@ Create an ASP.NET web app by following these steps:
 
 1. In **Name**, enter a unique app name that includes only the valid characters are `a-z`, `A-Z`, `0-9`, and `-`. You can accept the automatically generated unique name. The URL of the web app is `http://<app_name>.azurewebsites.net`, where `<app_name>` is your app name.
 
-   ![Configure app name](./media/app-service-web-get-started-dotnet-framework/web-app-name-framework-vs2019.png)
+2. Select **Create** to start creating the Azure resources.
 
-1. Select **Create** to start creating the Azure resources.
+   ![Configure app name](./media/app-service-web-get-started-dotnet-framework/web-app-name-framework-vs2019.png)
 
 Once the wizard completes, it publishes the ASP.NET web app to Azure, and then launches the app in the default browser.
 
@@ -121,11 +120,7 @@ The app name specified in the **App Service Create new** page is used as the URL
    </div>
    ```
 
-1. To redeploy to Azure, right-click the **myFirstAzureWebApp** project in **Solution Explorer** and select **Publish**.
-
-1. In the **Publish** summary page, select **Publish**.
-
-   ![Visual Studio summary page for publishing](./media/app-service-web-get-started-dotnet-framework/publish-summary-page-framework-vs2019.png)
+1. To redeploy to Azure, right-click the **myFirstAzureWebApp** project in **Solution Explorer** and select **Publish**. Then, select **Publish**.
 
 When publishing completes, Visual Studio launches a browser to the URL of the web app.
 
@@ -135,7 +130,7 @@ When publishing completes, Visual Studio launches a browser to the URL of the we
 
 1. Go to the <a href="https://portal.azure.com" target="_blank">Azure portal</a> to manage the web app.
 
-1. From the left menu, select **App Services**, and then select the name of your Azure app.
+2. From the left menu, select **App Services**, and then select the name of your Azure app.
 
    ![Portal navigation to Azure app](./media/app-service-web-get-started-dotnet-framework/access-portal-framework-vs2019.png)
 
@@ -145,14 +140,6 @@ When publishing completes, Visual Studio launches a browser to the URL of the we
 
    The left menu provides different pages for configuring your app.
 
-## Video
-
-Watch the video to see this quickstart in action and then follow the steps yourself to publish your first .NET app on Azure.
-
-> [!VIDEO https://channel9.msdn.com/Shows/Azure-for-NET-Developers/Create-a-NET-app-in-Azure-Quickstart/player]
-
-[!INCLUDE [Clean-up section](../../includes/clean-up-section-portal.md)]
-
 ## Next steps
 
 > [!div class="nextstepaction"]

articles/app-service/app-service-web-tutorial-windows-containers-custom-fonts.md

@@ -11,7 +11,7 @@ ms.service: app-service-web
 ms.workload: web
 ms.tgt_pltfrm: na
 ms.topic: quickstart
-ms.date: 04/03/2019
+ms.date: 10/22/2019
 ms.author: cephalin
 ms.custom: mvc
 ms.custom: seodec18
@@ -87,6 +87,10 @@ RUN ${source:-obj/Docker/publish/InstallFont.ps1}
 
 You can find _InstallFont.ps1_ in the **CustomFontSample** project. It's a simple script that installs the font. You can find a more complex version of the script in the [Script Center](https://gallery.technet.microsoft.com/scriptcenter/fb742f92-e594-4d0c-8b79-27564c575133).
 
+> [!NOTE]
+> To test the Windows container locally, make sure that Docker is started on your local machine.
+>
+
 ## Publish to Azure Container Registry
 
 [Azure Container Registry](https://docs.microsoft.com/azure/container-registry/) can store your images for container deployments. You can configure App Service to use images hosted in Azure Container Registry.
@@ -132,27 +136,34 @@ Sign in to the Azure portal at https://portal.azure.com.
 
 From the left menu, select **Create a resource** > **Web** > **Web App for Containers**.
 
-### Configure the new web app
+### Configure app basics
 
-In the create interface, configure the settings according to the following table:
+In the **Basics** tab, configure the settings according to the following table, then click **Next: Docker**.
 
 | Setting  | Suggested value | For more information |
 | ----------------- | ------------ | ----|
-|**App Name**| Type a unique name. | The URL of the web app is `http://<app_name>.azurewebsites.net`, where `<app_name>` is your app name. |
-|**Resource Group**| Select **Use existing** and type **myResourceGroup**. |  |
-|**OS**| Windows (Preview) | |
-
-### Configure App Service plan
+|**Subscription**| Make sure the correct subscription is selected. |  |
+|**Resource Group**| Select **Create new**, type **myResourceGroup**, and click **OK**. |  |
+|**Name**| Type a unique name. | The URL of the web app is `http://<app-name>.azurewebsites.net`, where `<app-name>` is your app name. |
+|**Publish**| Docker container | |
+|**Operating System**| Windows | |
+|**Region**| West Europe | |
+|**Windows Plan**| Select **Create new**, type **myAppServicePlan**, and click **OK**. | |
 
-Click **App Service plan/Location** > **Create new**. Give the new plan a name, select **West Europe** as the location, and click **OK**.
+Your **Basics** tab should look like this:
 
-![](media/app-service-web-tutorial-windows-containers-custom-fonts/configure-app-service-plan.png)
+![](media/app-service-web-tutorial-windows-containers-custom-fonts/configure-app-basics.png)
 
-### Configure container
+### Configure Windows container
 
-Click **Configure container** > **Azure Container Registry**. Select the registry, image, and tag you created earlier in [Publish to Azure Container Registry](#publish-to-azure-container-registry), and click **OK**.
+In the **Docker** tab, configure your custom Windows container as shown in the following table, and select **Review + create**.
 
-![](media/app-service-web-tutorial-windows-containers-custom-fonts/configure-app-container.png)
+| Setting  | Suggested value |
+| ----------------- | ------------ |
+|**Image Source**| Azure Container Register |
+|**Registry**| Select [the registry you created earlier](#publish-to-azure-container-registry). |
+|**Image**| customfontsample |
+|**Tag**| latest |
 
 ### Complete app creation
 
@@ -180,9 +191,9 @@ Wait a few minutes and try again, until you get the homepage with the beautiful
 
 ## See container start-up logs
 
-It may take some time for the Windows container to load. To see the progress, navigate to the following URL by replacing *\<app_name>* with the name of your app.
+It may take some time for the Windows container to load. To see the progress, navigate to the following URL by replacing *\<app-name>* with the name of your app.
 ```
-https://<app_name>.scm.azurewebsites.net/api/logstream
+https://<app-name>.scm.azurewebsites.net/api/logstream
 ```
 
 The streamed logs looks like this: