Merge branch 'master' of https://github.com/microsoftdocs/azure-docs-pr into akvqsfix

Author: msmbaldwin

.openpublishing.redirection.json

@@ -94,7 +94,7 @@ A web API can receive tokens from many types of clients, including web applicati
 6. The `access_token` and `refresh_token` are returned to the web server.
 7. The web API is called with the `access_token` in an authorization header.
 8. The web API validates the token.
-9. Secure data is returned to the web server.
+9. Secure data is returned to the web application.
 
 To learn more about authorization codes, refresh tokens, and the steps for getting tokens, read about the [OAuth 2.0 protocol](active-directory-b2c-reference-oauth-code.md).
 

articles/active-directory-b2c/active-directory-b2c-apps.md

@@ -102,7 +102,7 @@ After you create the application for the identity provider that you want to add,
     For example, `https://login.microsoftonline.com/contoso.onmicrosoft.com/.well-known/openid-configuration`.
 
 8. For **Client ID**, enter the application ID that you previously recorded and for **Client secret**, enter the key value that you previously recorded.
-9. Optionally, enter a value for **Domain_hint**. For example, `ContosoAD`. Domain hints(https://docs.microsoft.com/en-us/azure/active-directory/manage-apps/configure-authentication-for-federated-users-portal) are directives that are included in the authentication request from an application. They can be used to accelerate the user to their federated IdP sign-in page. Or they can be used by a multi-tenant application to accelerate the user straight to the branded Azure AD sign-in page for their tenant.
+9. Optionally, enter a value for **Domain_hint**. For example, `ContosoAD`. Domain hints(https://docs.microsoft.com/azure/active-directory/manage-apps/configure-authentication-for-federated-users-portal) are directives that are included in the authentication request from an application. They can be used to accelerate the user to their federated IdP sign-in page. Or they can be used by a multi-tenant application to accelerate the user straight to the branded Azure AD sign-in page for their tenant.
 10. Click **OK**.
 11. Select **Map this identity provider's claims** and set the following claims:
     

articles/active-directory-b2c/tutorial-add-identity-providers.md

@@ -94,7 +94,7 @@ When programmatically signing in, you need to pass the tenant ID with your authe
    ![Client ID](./media/howto-create-service-principal-portal/copy-app-id.png)
 
 ## Certificates and secrets
-Deamon applications can use two forms of credentials to authenticate with Azure AD: certificates and application secrets.  We recommend using a certificate, but you can also create a new application secret.
+Daemon applications can use two forms of credentials to authenticate with Azure AD: certificates and application secrets.  We recommend using a certificate, but you can also create a new application secret.
 
 ### Upload a certificate
 

articles/active-directory/develop/howto-create-service-principal-portal.md

@@ -91,7 +91,7 @@ The directory model is one of eventual consistencies. One typical problem with d
 
 Azure AD provides read-write consistency for applications targeting a secondary replica by routing its writes to the primary replica, and synchronously pulling the writes back to the secondary replica.
 
-Application writes using the Graph API of Azure AD are abstracted from maintaining affinity to a directory replica for read-write consistency. The Azure AD Graph service maintains a logical session, which has affinity to a secondary replica used for reads; affinity is captured in a “replica token” that the graph service caches using a distributed cache. This token is then used for subsequent operations in the same logical session. 
+Application writes using the Graph API of Azure AD are abstracted from maintaining affinity to a directory replica for read-write consistency. The Azure AD Graph service maintains a logical session, which has affinity to a secondary replica used for reads; affinity is captured in a “replica token” that the graph service caches using a distributed cache in the secondary replica datacenter. This token is then used for subsequent operations in the same logical session. To continue using the same logical session, subsequent requests must be routed to the same Azure AD datacenter. It is not possible to continue a logical session if the directory client requests are being routed to multiple Azure AD datacenters; if this happens then the client has multiple logical sessions which have independent read-write consistencies.
 
  >[!NOTE]
  >Writes are immediately replicated to the secondary replica to which the logical session's reads were issued.

articles/active-directory/fundamentals/active-directory-architecture.md

@@ -65,7 +65,7 @@ From the left menu, select **App Services**, and then select the name of the app
 
 You see the management page of the App Service app.  
 
-<a name="checkpricing"></a>
+<a name="checkpricing" aria-hidden="true"></a>
 
 ### Check the pricing tier
 
@@ -79,7 +79,7 @@ The app's current tier is highlighted by a blue border. Check to make sure that
 
 If the App Service plan is not in the **F1** tier, close the **Scale up** page and skip to [Map a CNAME record](#cname).
 
-<a name="scaleup"></a>
+<a name="scaleup" aria-hidden="true"></a>
 
 ### Scale up the App Service plan
 
@@ -93,7 +93,7 @@ When you see the following notification, the scale operation is complete.
 
 ![Scale operation confirmation](./media/app-service-web-tutorial-custom-domain/scale-notification.png)
 
-<a name="cname"></a>
+<a name="cname" aria-hidden="true"></a>
 
 ## Map your domain
 
@@ -159,7 +159,7 @@ If you missed a step or made a typo somewhere earlier, you see a verification er
 
 ![Verification error](./media/app-service-web-tutorial-custom-domain/verification-error-cname.png)
 
-<a name="a"></a>
+<a name="a" aria-hidden="true"></a>
 
 ### Map an A record
 
@@ -210,7 +210,7 @@ When the records are added, the DNS records page looks like the following exampl
 
 ![DNS records page](./media/app-service-web-tutorial-custom-domain/a-record.png)
 
-<a name="enable-a"></a>
+<a name="enable-a" aria-hidden="true"></a>
 
 #### Enable the A record mapping in the app
 
@@ -243,7 +243,7 @@ If you missed a step or made a typo somewhere earlier, you see a verification er
 
 ![Verification error](./media/app-service-web-tutorial-custom-domain/verification-error.png)
 
-<a name="wildcard"></a>
+<a name="wildcard" aria-hidden="true"></a>
 
 ### Map a wildcard domain
 
@@ -307,7 +307,7 @@ If you receive an HTTP 404 (Not Found) error when browsing to the URL of your cu
 - The custom domain configured is missing an A record and/or a CNAME record.
 - The browser client has cached the old IP address of your domain. Clear the cache and test DNS resolution again. On a Windows machine, you clear the cache with `ipconfig /flushdns`.
 
-<a name="virtualdir"></a>
+<a name="virtualdir" aria-hidden="true"></a>
 
 ## Migrate an active domain
 

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

@@ -151,6 +151,37 @@ $reports = Get-AzureRmAutomationDscNodeReport -ResourceGroupName 'MyResourceGrou
 $reports[0]
 ```
 
+## Removing nodes from service
+
+When you add a node to Azure Automation State Configuration,
+the settings in Local Configuration Manager are set to register with the service
+and pull configurations and required modules to configure the machine.
+If you choose to remove the node from the service,
+you can do so using either the Azure portal
+or the Az cmdlets.
+
+> [!NOTE]
+> Unregistering a node from the service only sets the Local Configuration Manager settings
+> so the node is no longer connecting to the service.
+> This does not effect the configuration that is currently applied to the node.
+> To remove the current configuration, use the
+> [PowerShell](https://docs.microsoft.com/en-us/powershell/module/psdesiredstateconfiguration/remove-dscconfigurationdocument?view=powershell-5.1)
+> or delete the local configuration file
+> (this is the only option for Linux nodes).
+
+### Azure portal
+
+From Azure Automation, click on **State configuration (DSC)** in the table of contents.
+Next click **Nodes** to view the list of nodes that are registered with the service.
+Click on the name of the node you wish to remove.
+In the Node view that opens, click **Unregister**.
+
+### PowerShell
+
+To unregister a node from Azure Automation State Configuration service using PowerShell,
+follow the documentation for the cmdlet
+[Unregister-AzAutomationDscNode](https://docs.microsoft.com/en-us/powershell/module/az.automation/unregister-azautomationdscnode?view=azps-2.0.0).
+
 ## Next steps
 
 - To get started, see [Getting started with Azure Automation State Configuration](automation-dsc-getting-started.md)

articles/automation/tutorial-configure-servers-desired-state.md

@@ -246,18 +246,10 @@ You can modify these parameters as needed.
 - **MaxCollectSec**. Set this parameter to prevent PerfView from running indefinitely and affecting the performance of your server.
 - **OnlyProviders**. Set this paramater to only collect logs from the SDK. You can customize this list based on your specific investigations. 
 
-   Our full list of providers is:
 
-   - Microsoft-ApplicationInsights-Core
-   - Microsoft-ApplicationInsights-Extensibility-DependencyCollector
-   - Microsoft-ApplicationInsights-Extensibility-Rtia-SharedCore
-   - Microsoft-ApplicationInsights-Extensibility-Web
-   - Microsoft-ApplicationInsights-Extensibility-WindowsServer
-   - Microsoft-ApplicationInsights-Web
-   - Microsoft-ApplicationInsights-WindowsServer-TelemetryChannel
-
-
-For more information, see [Recording performance traces with PerfView](https://github.com/dotnet/roslyn/wiki/Recording-performance-traces-with-PerfView).
+For more information,
+- [Recording performance traces with PerfView](https://github.com/dotnet/roslyn/wiki/Recording-performance-traces-with-PerfView).
+- [Application Insights Event Sources](https://github.com/microsoft/ApplicationInsights-Home/tree/master/Samples/ETW)
 
 ## Still not working...
 * [Application Insights forum](https://social.msdn.microsoft.com/Forums/vstudio/en-US/home?forum=ApplicationInsights)

articles/azure-monitor/app/asp-net-troubleshoot-no-data.md

@@ -216,8 +216,8 @@ To use the updated solutions:
 
      | Instead of: | Use: |
      | --- | --- |
-     | NetworkApplicationgateways | where OperationName=="ApplicationGatewayAccess" | AzureDiagnostics | where ResourceType="APPLICATIONGATEWAYS" and OperationName=="ApplicationGatewayAccess" |
-     | NetworkApplicationgateways | where OperationName=="ApplicationGatewayPerformance" | AzureDiagnostics | where ResourceType=="APPLICATIONGATEWAYS" and OperationName=ApplicationGatewayPerformance |
+     | NetworkApplicationgateways | where OperationName=="ApplicationGatewayAccess" | AzureDiagnostics | where ResourceType=="APPLICATIONGATEWAYS" and OperationName=="ApplicationGatewayAccess" |
+     | NetworkApplicationgateways | where OperationName=="ApplicationGatewayPerformance" | AzureDiagnostics | where ResourceType=="APPLICATIONGATEWAYS" and OperationName=="ApplicationGatewayPerformance" |
      | NetworkSecuritygroups | AzureDiagnostics | where ResourceType=="NETWORKSECURITYGROUPS" |
 
    + For any field that has a suffix of \_s, \_d, or \_g in the name, change the first character to lower case

articles/azure-monitor/insights/azure-networking-analytics.md

@@ -124,7 +124,7 @@ If you observe an abnormality, follow these steps:
 * If the application is running slow, determine whether poor application performance is because of the network or an issue on the application provider's end.
 
 ## GCC Office URLs for US Government customers
-For US Government Virginia region, only DOD URLs are built-in NPM. Customers using GCC URLs need to create custom tests and add each URL inidividually.
+For US Government Virginia region, only DOD URLs are built-in NPM. Customers using GCC URLs need to create custom tests and add each URL individually.
 
 | Field | GCC |
 |:---   |:--- |