Merge pull request #77306 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to master to sync with https://github.com/Microsoft/azure-docs (branch master)

Author: huypub

articles/active-directory/authentication/concept-password-ban-bad.md

@@ -74,7 +74,7 @@ Each of the above passwords does not specifically match the banned password "abc
 
 Substring matching is used on the normalized password to check for the user’s first and last name as well as the tenant name (note that tenant name matching is not done when validating passwords on an Active Directory domain controller).
 
-Example: assume that we have a user John Doe that wants to reset his password to “J0hn123fb”. After normalization, this password would become “john123fb”. Substring matching finds that the password contains the user’s first name “John”. Even though “J0hn123fb” was not specifically on either banned password list, substring matching found “John" in the password. Therefore this password would be rejected.
+Example: assume that we have a user, Pol, who wants to reset their password to “P0l123fb”. After normalization, this password would become “pol123fb”. Substring matching finds that the password contains the user’s first name “Pol”. Even though “P0l123fb” was not specifically on either banned password list, substring matching found “Pol" in the password. Therefore this password would be rejected.
 
 #### Score Calculation
 

articles/aks/acs-aks-migration.md

@@ -24,7 +24,7 @@ ACS and AKS differ in some key areas that affect migration. Before any migration
     * Unmanaged disks must be converted before you can attach them to AKS nodes.
     * Custom `StorageClass` objects for Azure disks must be changed from `unmanaged` to `managed`.
     * Any `PersistentVolumes` should use `kind: Managed`.
-* AKS supports supports [multiple node pools](https://docs.microsoft.com/en-us/azure/aks/use-multiple-node-pools) (currently in preview).
+* AKS supports [multiple node pools](https://docs.microsoft.com/azure/aks/use-multiple-node-pools) (currently in preview).
 * Nodes based on Windows Server are currently in [preview in AKS](https://azure.microsoft.com/blog/kubernetes-on-azure/).
 * AKS supports a limited set of [regions](https://docs.microsoft.com/azure/aks/quotas-skus-regions).
 * AKS is a managed service with a hosted Kubernetes control plane. You might need to modify your applications if you've previously modified the configuration of your ACS masters.

articles/azure-monitor/platform/agents-overview.md

@@ -25,7 +25,7 @@ Microsoft Azure provides multiple ways to collect different types of data from v
 This article describes the differences between them and their capabilities in order for you to determine which one will support your IT service management or general monitoring requirements.  
 
 ## Azure Diagnostic extension
-The [Azure Diagnostics extension](../../azure-monitor/platform/diagnostics-extension-overview.md) (commonly referred to as the Windows Azure Diagnostic (WAD) or Linux Azure Diagnostic (LAD) extension), which has been provided for Azure Cloud Services since it became generally available in 2010, is an agent that delivers simple collection of diagnostic data from an Azure compute resource like a VM, and persist it to Azure storage. Once in storage, you chose to view with one of several available tools, such as [Server Explorer in Visual Studio](/visualstudio/azure/vs-azure-tools-storage-resources-server-explorer-browse-manage) and [Azure Storage Explorer](../../vs-azure-tools-storage-manage-with-storage-explorer.md).
+The [Azure Diagnostics extension](../../azure-monitor/platform/diagnostics-extension-overview.md) (commonly referred to as the Windows Azure Diagnostic (WAD) or Linux Azure Diagnostic (LAD) extension), which has been provided for Azure Cloud Services since it became generally available in 2010, is an agent that delivers simple collection of diagnostic data from an Azure compute resource like a VM, and persist it to Azure storage. Once in storage, you choose to view with one of several available tools, such as [Server Explorer in Visual Studio](/visualstudio/azure/vs-azure-tools-storage-resources-server-explorer-browse-manage) and [Azure Storage Explorer](../../vs-azure-tools-storage-manage-with-storage-explorer.md).
 
 You can choose to collect:
 
@@ -54,7 +54,7 @@ For advanced monitoring where you need to do more than collect metrics and a sub
 The Log Analytics agent should be used when you want to:
 
 * Collect data from a variety of sources both within Azure, other cloud providers, and on-premises resources. 
-* Using one of the Azure Monitor monitoring solutions such as [Azure Monitor for VMs](../insights/vminsights-overview.md), [Azure Monitor for containers](../insights/container-insights-overview.md), etc.  
+* Use one of the Azure Monitor monitoring solutions such as [Azure Monitor for VMs](../insights/vminsights-overview.md), [Azure Monitor for containers](../insights/container-insights-overview.md), etc.  
 * Use one of the other Azure management services such as [Azure Security Center](../../security-center/security-center-intro.md), [Azure Automation](../../automation/automation-intro.md), etc.
 
 Previously, several Azure services were bundled as the *Operations Management Suite*, and as a result the Log Analytics agent is shared across services including Azure Security Center and Azure Automation.  This includes the full set of features they offer, delivering comprehensive management of your Azure VMs through their lifecycle.  Some examples of this are:

articles/hdinsight/hdinsight-restrict-outbound-traffic.md

@@ -21,7 +21,7 @@ There are several dependencies that require inbound traffic. The inbound managem
 
 The HDInsight outbound traffic dependencies are almost entirely defined with FQDNs, which don't have static IP addresses behind them. The lack of static addresses means that Network Security Groups (NSGs) can't be used to lock down the outbound traffic from a cluster. The addresses change often enough that one can't set up rules based on the current name resolution and use that to set up NSG rules.
 
-The solution to securing outbound addresses is to use a firewall device that can control outbound traffic based on domain names. Azure Firewall can restrict outbound HTTP and HTTPS traffic based on the FQDN of the destination.
+The solution to securing outbound addresses is to use a firewall device that can control outbound traffic based on domain names. Azure Firewall can restrict outbound HTTP and HTTPS traffic based on the FQDN of the destination or [FQDN tags](https://docs.microsoft.com/azure/firewall/fqdn-tags).
 
 ## Configuring Azure Firewall with HDInsight
 
@@ -74,7 +74,7 @@ On the **Add application rule collection** screen, complete the following steps:
         1. Enter `https:443` under **Protocol:Port** and `sqm.telemetry.microsoft.com` under **Target FQDNS**.
     1. If your cluster is backed by WASB and you are not using the service endpoints above, then add a rule for WASB:
         1. In the **Target FQDNs** section, provide a **Name**, and set **Source addresses** to `*`.
-        1. Enter `wasb` under **Protocol:Port** and `*` under **Target FQDNS**.
+        1. Enter `http` or [https] depending on if you are using wasb:// or wasbs:// under **Protocol:Port** and the storage account url under **Target FQDNS**.
 1. Click **Add**.
 
 ![Title: Enter application rule collection details](./media/hdinsight-restrict-outbound-traffic/hdinsight-restrict-outbound-traffic-add-app-rule-collection-details.png)

articles/sql-database/saas-multitenantdb-get-started-deploy.md

@@ -52,7 +52,7 @@ To complete this tutorial, make sure the following prerequisites are completed:
 ### Plan the names
 
 In the steps of this section, you provide a *user* value that is used to ensure resource names are globally unique, and a name for the *resource group* which contains all the resources created by a deployment of the app. For a person named *Ann Finley*, we suggest:
-- *User:* **af1**  *(Her initials, plus a digit. Use a different value (e.g. af2) if you deploy the app a second time.)*
+- *User:* **af1**  *(Their initials, plus a digit. Use a different value (e.g. af2) if you deploy the app a second time.)*
 - *Resource group:* **wingtip-mt-af1** *(wingtip-mt indicates this is the sharded multi-tenant app. Appending the user name af1 correlates the resource group name with the names of the resources it contains.)*
 
 Choose your names now, and write them down. 

articles/sql-database/sql-database-tutorial-predictive-model-deploy.md

@@ -29,7 +29,7 @@ In this article, you'll learn how to:
 > * Create a stored procedure that makes predictions using the model
 > * Execute the model with new data
 
-In [part one](sql-database-tutorial-predictive-model-prepare-data.md), you learned how how to import a sample database into an Azure SQL database, and then prepare the data to be used for training a predictive model in R.
+In [part one](sql-database-tutorial-predictive-model-prepare-data.md), you learned how to import a sample database into an Azure SQL database, and then prepare the data to be used for training a predictive model in R.
 
 In [part two](sql-database-tutorial-predictive-model-build-compare.md), you learned how to create and train multiple models, and then choose the most accurate one.
 

articles/sql-database/sql-database-tutorial-predictive-model-prepare-data.md

@@ -40,7 +40,7 @@ In [part three](sql-database-tutorial-predictive-model-deploy.md), you'll learn
 
 * Azure SQL Database Server with Machine Learning Services enabled - During the public preview, Microsoft will onboard you and enable machine learning for your existing or new databases. Follow the steps in [Sign up for the preview](sql-database-machine-learning-services-overview.md#signup).
 
-* RevoScaleR package - See [RevoScaleR](https://docs.microsoft.com/en-us/sql/advanced-analytics/r/ref-r-revoscaler?view=sql-server-2017#versions-and-platforms) for options to install this package locally.
+* RevoScaleR package - See [RevoScaleR](https://docs.microsoft.com/sql/advanced-analytics/r/ref-r-revoscaler?view=sql-server-2017#versions-and-platforms) for options to install this package locally.
 
 * R IDE - This tutorial uses [RStudio Desktop](https://www.rstudio.com/products/rstudio/download/).
 
@@ -56,7 +56,7 @@ The sample dataset used in this tutorial has been saved to a **.bacpac** databas
 
 1. Download the file [TutorialDB.bacpac](https://sqlchoice.blob.core.windows.net/sqlchoice/static/TutorialDB.bacpac).
 
-1. Follow the directions in [Import a BACPAC file to create an Azure SQL database](https://docs.microsoft.com/en-us/azure/sql-database/sql-database-import), using these details:
+1. Follow the directions in [Import a BACPAC file to create an Azure SQL database](https://docs.microsoft.com/azure/sql-database/sql-database-import), using these details:
 
    * Import from the **TutorialDB.bacpac** file you downloaded
    * During the public preview, choose the **Gen5/vCore** configuration for the new database