Merge pull request #50318 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/devices/hybrid-azuread-join-plan.md

@@ -122,7 +122,7 @@ If your environment has managed domains, hybrid Azure AD join supports:
 
 - Pass Through Authentication (PTA) with Seamless Single Sign On (SSO) 
 
-- Password Has Sync (PHS) with Seamless Single Sign On (SSO) 
+- Password Hash Sync (PHS) with Seamless Single Sign On (SSO) 
 
 Beginning with version 1.1.819.0, Azure AD Connect provides you with a wizard to configure hybrid Azure AD join. The wizard enables you to significantly simplify the configuration process. For more information, see:
 

articles/aks/acs-aks-migration.md

@@ -14,13 +14,13 @@ ms.custom: mvc
 
 # Migrating from Azure Container Service (ACS) to Azure Kubernetes Service (AKS)
 
-This goal of this document is to help you plan and execute a successful migration between Azure Container Service with Kubernetes (ACS) and Azure Kubernetes Service (AKS). This guide details the differences between ACS and AKS, provides an overview of the migration process, and should help you make key decisions.
+The goal of this document is to help you plan and execute a successful migration between Azure Container Service with Kubernetes (ACS) and Azure Kubernetes Service (AKS). This guide details the differences between ACS and AKS, provides an overview of the migration process, and should help you make key decisions.
 
 ## Differences between ACS and AKS
 
 ACS and AKS differ in some key areas that impact migration. You should review and plan to address the following differences before any migration.
 
-* AKS nodes use Managed Disks
+* AKS nodes use [Managed Disks](../virtual-machines/windows/managed-disks-overview.md)
     * Unmanaged disks will need to be converted before they can be attached to AKS nodes
     * Custom `StorageClass` objects for Azure disks will need to be changed from `unmanaged` to `managed`
     * Any `PersistentVolumes` will need to use `kind: Managed`

articles/log-analytics/log-analytics-create-pipeline-datacollector-api.md

@@ -38,7 +38,7 @@ We are using a classic ETL-type logic to design our pipeline. The architecture w
 
 This article will not cover how to create data or [upload it to an Azure Blob Storage account](../storage/blobs/storage-upload-process-images.md). Rather, we pick the flow up as soon as a new file is uploaded to the blob. From here:
 
-1. A process will detect that new data has been uploaded.  Our example uses uses an [Azure Logic App](../logic-apps/logic-apps-overview.md), which has available a trigger to detect new data being uploaded to a blob.
+1. A process will detect that new data has been uploaded.  Our example uses an [Azure Logic App](../logic-apps/logic-apps-overview.md), which has available a trigger to detect new data being uploaded to a blob.
 
 2. A processor reads this new data and converts it to JSON, the format required by Log Analytics.  In this example, we use an [Azure Function](../azure-functions/functions-overview.md) as a lightweight, cost-efficient way of executing our processing code. The function is kicked off by the same Logic App that we used to detect a the new data.
 
@@ -169,4 +169,4 @@ This article presented a working prototype, the logic behind which can be applie
 
 
 ## Next steps
-Learn more about the  [Data Collector API](log-analytics-data-collector-api.md) to write data to Log Analytics from any REST API client.
+Learn more about the  [Data Collector API](log-analytics-data-collector-api.md) to write data to Log Analytics from any REST API client.

articles/sql-database/sql-database-automatic-tuning.md

@@ -59,7 +59,7 @@ For an overview of how automatic tuning works and for typical usage scenarios, s
 
 Automatic tuning options available in Azure SQL Database are:
  1. **CREATE INDEX** - identifies indexes that may improve performance of your workload, creates indexes, and automatically verifies that performance of queries has improved.
- 2. **DROP INDEX** - identifies redundant and duplicate indexes daily, and indexes that were not used for a long time (>90 days). Note that this option is not compatible with applications using partition switching and index hints.
+ 2. **DROP INDEX** - identifies redundant and duplicate indexes daily, except for unique indexes, and indexes that were not used for a long time (>90 days). Note that this option is not compatible with applications using partition switching and index hints.
  3. **FORCE LAST GOOD PLAN** - identifies SQL queries using execution plan that is slower than the previous good plan, and queries using the last known good plan instead of the regressed plan.
 
 Automatic tuning identifies **CREATE INDEX**, **DROP INDEX**, and **FORCE LAST GOOD PLAN** recommendations that can optimize your database performance and shows them in [Azure portal](sql-database-advisor-portal.md), and exposes them through [T-SQL](https://docs.microsoft.com/sql/t-sql/statements/alter-database-transact-sql-set-options?view=azuresqldb-current) and [REST API](https://docs.microsoft.com/rest/api/sql/serverautomatictuning).

articles/sql-database/sql-database-connect-query-dotnet-visual-studio.md

@@ -50,7 +50,7 @@ To complete this quickstart, make sure you have the following:
 3. Select **Console App** and enter *sqltest* for the project name.
 4. Click **OK** to create and open the new project in Visual Studio
 4. In Solution Explorer, right-click **sqltest** and click **Manage NuGet Packages**. 
-5. On the **Browse**, search for ```System.Data.SqlClient``` and, when found, select it.
+5. On the **Browse** tab, search for ```System.Data.SqlClient``` and, when found, select it.
 6. In the **System.Data.SqlClient** page, click **Install**.
 7. When the install completes, review the changes and then click **OK** to close the **Preview** window. 
 8. If a **License Acceptance** window appears, click **I Accept**.

articles/virtual-machines/linux/using-cloud-init.md

@@ -28,8 +28,10 @@ Cloud-init also works across distributions. For example, you don't use **apt-get
 
  We are actively working with our endorsed Linux distro partners in order to have cloud-init enabled images available in the Azure marketplace. These images will make your cloud-init deployments and configurations work seamlessly with VMs and VM Scale Sets (VMSS). The following table outlines the current cloud-init enabled images availability on the Azure platform:
 
-| Publisher | Offer | SKU | Version | cloud-init ready
-|:--- |:--- |:--- |:--- |:--- |:--- |
+| Publisher | Offer | SKU | Version | cloud-init ready |
+|:--- |:--- |:--- |:--- |:--- |
+|Canonical |UbuntuServer |18.04-LTS |latest |yes | 
+|Canonical |UbuntuServer |17.10 |latest |yes | 
 |Canonical |UbuntuServer |16.04-LTS |latest |yes | 
 |Canonical |UbuntuServer |14.04.5-LTS |latest |yes |
 |CoreOS |CoreOS |Stable |latest |yes |