pr validation error fixes

Author: bandersmsft

articles/active-directory/managed-identities-azure-resources/overview.md

@@ -2,14 +2,14 @@
 title: Managed identities for Azure resources
 description: An overview of the managed identities for Azure resources.
 services: active-directory
-documentationcenter: 
+documentationcenter:
 author: MarkusVi
 manager: daveba
-editor: 
+editor:
 ms.assetid: 0232041d-b8f5-4bd2-8d11-27999ad69370
 ms.service: active-directory
 ms.subservice: msi
-ms.devlang: 
+ms.devlang:
 ms.topic: overview
 ms.custom: mvc
 ms.date: 09/26/2019
@@ -23,7 +23,7 @@ ms.collection: M365-identity-device-management
 
 [!INCLUDE [preview-notice](../../../includes/active-directory-msi-preview-notice.md)]
 
-A common challenge when building cloud applications is how to manage the credentials in your code for authenticating to cloud services. Keeping the credentials secure is an important task. Ideally, the credentials never appear on developer workstations and aren't checked into source control. Azure Key Vault provides a way to securely store credentials, secrets, and other keys, but your code has to authenticate to Key Vault to retrieve them. 
+A common challenge when building cloud applications is how to manage the credentials in your code for authenticating to cloud services. Keeping the credentials secure is an important task. Ideally, the credentials never appear on developer workstations and aren't checked into source control. Azure Key Vault provides a way to securely store credentials, secrets, and other keys, but your code has to authenticate to Key Vault to retrieve them.
 
 The managed identities for Azure resources feature in Azure Active Directory (Azure AD) solves this problem. The feature provides Azure services with an automatically managed identity in Azure AD. You can use the identity to authenticate to any service that supports Azure AD authentication, including Key Vault, without any credentials in your code.
 
@@ -47,9 +47,9 @@ There are two types of managed identities:
 - A **system-assigned managed identity** is enabled directly on an Azure service instance. When the identity is enabled, Azure creates an identity for the instance in the Azure AD tenant that's trusted by the subscription of the instance. After the identity is created, the credentials are provisioned onto the instance. The lifecycle of a system-assigned identity is directly tied to the Azure service instance that it's enabled on. If the instance is deleted, Azure automatically cleans up the credentials and the identity in Azure AD.
 - A **user-assigned managed identity** is created as a standalone Azure resource. Through a create process, Azure creates an identity in the Azure AD tenant that's trusted by the subscription in use. After the identity is created, the identity can be assigned to one or more Azure service instances. The lifecycle of a user-assigned identity is managed separately from the lifecycle of the Azure service instances to which it's assigned.
 
-Internally, managed identities are service principals of a special type, which are locked to only be used with Azure resources. When the managed identity is deleted, the corresponding service principal is automatically removed. 
+Internally, managed identities are service principals of a special type, which are locked to only be used with Azure resources. When the managed identity is deleted, the corresponding service principal is automatically removed.
 
-Your code can use a managed identity to request access tokens for services that support Azure AD authentication. Azure takes care of rolling the credentials that are used by the service instance. 
+Your code can use a managed identity to request access tokens for services that support Azure AD authentication. Azure takes care of rolling the credentials that are used by the service instance.
 
 The following diagram shows how managed service identities work with Azure virtual machines (VMs):
 
@@ -60,7 +60,7 @@ The following diagram shows how managed service identities work with Azure virtu
 | Creation |  Created as part of an Azure resource (for example, an Azure virtual machine or Azure App Service) | Created as a stand-alone Azure resource |
 | Lifecycle | Shared lifecycle with the Azure resource that the managed identity is created with. <br/> When the parent resource is deleted, the managed identity is deleted as well. | Independent life-cycle. <br/> Must be explicitly deleted. |
 | Sharing across Azure resources | Cannot be shared. <br/> It can only be associated with a single Azure resource. | Can be shared <br/> The same user-assigned managed identity can be associated with more than one Azure resource. |
-| Common use cases | Workloads that are contained within a single Azure resource <br/> Workloads for which you need independent identities. <br/> For example, an application that runs on a single virtual machine | Workloads that run on multiple resources and which can share a single identity. <br/> Workloads that need pre-authorization to a secure resource as part of a provisioning flow. <br/> Workloads where resources are recycled frequently, but permissions should stay consistent. <br/> For example, a workload where multiple virtual machines need to access the same resource | 
+| Common use cases | Workloads that are contained within a single Azure resource <br/> Workloads for which you need independent identities. <br/> For example, an application that runs on a single virtual machine | Workloads that run on multiple resources and which can share a single identity. <br/> Workloads that need pre-authorization to a secure resource as part of a provisioning flow. <br/> Workloads where resources are recycled frequently, but permissions should stay consistent. <br/> For example, a workload where multiple virtual machines need to access the same resource |
 
 ### How a system-assigned managed identity works with an Azure VM
 
@@ -113,7 +113,7 @@ Learn how to use a managed identity with a Windows VM:
 * [Access Azure Data Lake Store](tutorial-windows-vm-access-datalake.md)
 * [Access Azure Resource Manager](tutorial-windows-vm-access-arm.md)
 * [Access Azure SQL](tutorial-windows-vm-access-sql.md)
-* [Access Azure Storage by using an access key](tutorial-windows-vm-access-storage.md)
+* [Access Azure Storage by using an access key](tutorial-vm-windows-access-storage.md)
 * [Access Azure Storage by using shared access signatures](tutorial-windows-vm-access-storage-sas.md)
 * [Access a non-Azure AD resource with Azure Key Vault](tutorial-windows-vm-access-nonaad.md)
 

articles/azure-monitor/platform/resource-logs-collect-storage.md

@@ -13,7 +13,7 @@ ms.subservice: logs
 [Resource logs](resource-logs-overview.md) in Azure provide rich, frequent data about the internal operation of an Azure resource. This article describes collecting resource logs to an Azure storage account to retain data for archiving.
 
 ## Prerequisites
-You need to [create an Azure storage account](../../storage/common/storage-quickstart-create-account.md) if you don't already have one. The storage account does not have to be in the same subscription as the resource sending logs as long as the user who configures the setting has appropriate RBAC access to both subscriptions.
+You need to [create an Azure storage account](../../storage/common/storage-account-create.md) if you don't already have one. The storage account does not have to be in the same subscription as the resource sending logs as long as the user who configures the setting has appropriate RBAC access to both subscriptions.
 
 
 > [!IMPORTANT]

articles/azure-resource-manager/resource-manager-tutorial-use-conditions.md

@@ -150,7 +150,7 @@ New-AzResourceGroupDeployment `
 > [!NOTE]
 > The deployment fails if **newOrExisting** is **new**, but the storage account with the storage account name specified already exists.
 
-Try making another deployment with **newOrExisting** set to "existing" and specify an existing storage account. To create a storage account beforehand, see [Create a storage account](../storage/common/storage-quickstart-create-account.md).
+Try making another deployment with **newOrExisting** set to "existing" and specify an existing storage account. To create a storage account beforehand, see [Create a storage account](../storage/common/storage-account-create.md).
 
 ## Clean up resources
 

articles/cloud-services/cloud-services-how-to-monitor.md

@@ -47,7 +47,7 @@ As each role is created, Visual Studio adds the Azure Diagnostics extension to i
 
 ## Setup diagnostics extension
 
-First, if you don't have a **classic** storage account, [create one](../storage/common/storage-quickstart-create-account.md). Make sure the storage account is created with the **Classic deployment model** specified.
+First, if you don't have a **classic** storage account, [create one](../storage/common/storage-account-create.md). Make sure the storage account is created with the **Classic deployment model** specified.
 
 Next, navigate to the **Storage account (classic)** resource. Select **Settings** > **Access keys** and copy the **Primary connection string** value. You need this value for the cloud service. 
 

articles/cognitive-services/form-recognizer/tutorial-form-recognizer-with-logic-apps.md

@@ -47,7 +47,7 @@ In this tutorial, we learn how to extract the information from such tables into
 
 You use this container to upload sample data that is required to train the model.
 
-1. Follow the instructions in [Create an Azure Storage account](../../storage/common/storage-quickstart-create-account.md) to create a storage account. Use **formrecostorage** as the storage account name.
+1. Follow the instructions in [Create an Azure Storage account](../../storage/common/storage-account-create.md) to create a storage account. Use **formrecostorage** as the storage account name.
 1. Follow the instructions in [Create an Azure blob container](../../storage/blobs/storage-quickstart-blobs-portal.md) to create a container within the Azure Storage account. Use **formrecocontainer** as the container name. Make sure you set the public access level to **Container (anonymous read access for containers and blobs)**.
 
     > [!div class="mx-imgBorder"]

articles/cost-management/storage-accounts.md

@@ -22,7 +22,7 @@ You can save Cloudyn reports in the Cloudyn portal, Azure storage, or AWS storag
 
 You must have either an Azure storage account or an Amazon storage bucket.
 
-If you don't have an Azure storage account, you need to create one. For more information about creating an Azure storage account, see [Create a storage account](../storage/common/storage-quickstart-create-account.md).
+If you don't have an Azure storage account, you need to create one. For more information about creating an Azure storage account, see [Create a storage account](../storage/common/storage-account-create.md).
 
 If you don't have an AWS simple storage service (S3) bucket, you need to create one. For more information about creating an S3 bucket, see [Create a Bucket](https://docs.aws.amazon.com/AmazonS3/latest/gsg/CreatingABucket.html).
 

articles/data-factory/quickstart-create-data-factory-python.md

@@ -29,7 +29,7 @@ If you don't have an Azure subscription, create a [free](https://azure.microsoft
 
 ## Prerequisites
 
-* **Azure Storage account**. You use the blob storage as **source** and **sink** data store. If you don't have an Azure storage account, see the [Create a storage account](../storage/common/storage-quickstart-create-account.md) article for steps to create one.
+* **Azure Storage account**. You use the blob storage as **source** and **sink** data store. If you don't have an Azure storage account, see the [Create a storage account](../storage/common/storage-account-create.md) article for steps to create one.
 * **Create an application in Azure Active Directory** following [this instruction](../active-directory/develop/howto-create-service-principal-portal.md#create-an-azure-active-directory-application). Make note of the following values that you use in later steps: **application ID**, **authentication key**, and **tenant ID**. Assign application to "**Contributor**" role by following instructions in the same article.
 
 ### Create and upload an input file

articles/data-factory/v1/data-factory-customer-profiling-usecase.md

@@ -24,7 +24,7 @@ Contoso’s goal is to identify up-sell/cross-sell opportunities based on the ga
 In this solution, Contoso wants to evaluate the effectiveness of a marketing campaign it has recently launched. We start with the raw gaming logs, process and enrich them with geolocation data, join it with advertising reference data, and lastly copy them into an Azure SQL Database to analyze the campaign’s impact.
 
 ## Deploy Solution
-All you need to access and try out this simple use case is an [Azure subscription](https://azure.microsoft.com/pricing/free-trial/), an [Azure Blob storage account](../../storage/common/storage-quickstart-create-account.md), and an [Azure SQL Database](../../sql-database/sql-database-get-started.md). You deploy the customer profiling pipeline from the **Sample pipelines** tile on the home page of your data factory.
+All you need to access and try out this simple use case is an [Azure subscription](https://azure.microsoft.com/pricing/free-trial/), an [Azure Blob storage account](../../storage/common/storage-account-create.md), and an [Azure SQL Database](../../sql-database/sql-database-get-started.md). You deploy the customer profiling pipeline from the **Sample pipelines** tile on the home page of your data factory.
 
 1. Create a data factory or open an existing data factory. See [Copy data from Blob Storage to SQL Database using Data Factory](data-factory-copy-data-from-azure-blob-storage-to-sql-database.md) for steps to create a data factory.
 2. In the **DATA FACTORY** blade for the data factory, click the **Sample pipelines** tile.

articles/event-grid/blob-event-quickstart-portal.md

@@ -32,7 +32,7 @@ When you're finished, you see that the event data has been sent to the web app.
 
    ![Select storage](./media/blob-event-quickstart-portal/create-storage.png)
 
-1. To subscribe to events, create either a general-purpose v2 storage account or a Blob storage account. For more information, see [Create a storage account](../storage/common/storage-quickstart-create-account.md).
+1. To subscribe to events, create either a general-purpose v2 storage account or a Blob storage account. For more information, see [Create a storage account](../storage/common/storage-account-create.md).
 
    ![Start steps](./media/blob-event-quickstart-portal/provide-blob-values.png)
 

articles/event-hubs/event-hubs-kafka-stream-analytics.md

@@ -35,7 +35,7 @@ To complete this quickstart, make sure you have the following prerequisites:
 * [Java Development Kit (JDK) 1.7+](https://aka.ms/azure-jdks).
 * [Download](https://maven.apache.org/download.cgi) and [install](https://maven.apache.org/install.html) a Maven binary archive.
 * [Git](https://www.git-scm.com/)
-* An **Azure Storage account**. If you don't have one, [create one](../storage/common/storage-quickstart-create-account.md) before proceeding further. The Stream Analytics job in this walkthrough stores the output data in an Azure blob storage. 
+* An **Azure Storage account**. If you don't have one, [create one](../storage/common/storage-account-create.md) before proceeding further. The Stream Analytics job in this walkthrough stores the output data in an Azure blob storage. 
 
 
 ## Create a Kafka enabled Event Hubs namespace
@@ -111,7 +111,7 @@ You can now stream events from your applications that use the Kafka protocol int
     ![Event hub - messages](./media/event-hubs-kafka-stream-analytics/confirm-event-hub-messages.png)
 
 ## Process event data using a Stream Analytics job
-In this section, you create an Azure Stream Analytics job. The Kafka client sends events to the event hub. You create a Stream Analytics job that takes event data as input and outputs it to an Azure blob storage. If you don't have  an **Azure Storage account**, [create one](../storage/common/storage-quickstart-create-account.md).
+In this section, you create an Azure Stream Analytics job. The Kafka client sends events to the event hub. You create a Stream Analytics job that takes event data as input and outputs it to an Azure blob storage. If you don't have  an **Azure Storage account**, [create one](../storage/common/storage-account-create.md).
 
 The query in the Stream Analytics job passes through the data without performing any analytics. You can create a query that transforms the input data to produce output data in a different format or with gained insights.  
 

articles/guides/operations/azure-operations-guide.md

@@ -403,7 +403,7 @@ There are several options for deploying a storage account.
 
 #### Portal
 
-Deploying a storage account by using the Azure portal requires only an active Azure subscription and access to a web browser. You can deploy a new storage account into a new or existing resource group. After you’ve created the storage account, you can create a blob container or file share by using the portal. You can create Table and Queue storage entities programmatically. For more information, see [Create a storage account](../../storage/common/storage-quickstart-create-account.md).
+Deploying a storage account by using the Azure portal requires only an active Azure subscription and access to a web browser. You can deploy a new storage account into a new or existing resource group. After you’ve created the storage account, you can create a blob container or file share by using the portal. You can create Table and Queue storage entities programmatically. For more information, see [Create a storage account](../../storage/common/storage-account-create.md).
 
 In addition to deploying a storage account from the Azure portal, you can deploy an Azure Resource Manager template from the portal. This will deploy and configure all resources as defined in the template, including any storage accounts. For more information, see [Deploy resources with Resource Manager templates and Azure portal](../../azure-resource-manager/resource-group-template-deploy-portal.md).
 

articles/hdinsight/hdinsight-hadoop-create-linux-clusters-dotnet-sdk.md

@@ -27,7 +27,7 @@ Learn how to create an [Apache Hadoop](https://hadoop.apache.org/) cluster in Az
 [!INCLUDE [delete-cluster-warning](../../includes/hdinsight-delete-cluster-warning.md)]
 
 * **An Azure subscription**. See [Get Azure free trial](https://azure.microsoft.com/documentation/videos/get-azure-free-trial-for-testing-hadoop-in-hdinsight/).
-* **An Azure storage account**. See [Create a storage account](../storage/common/storage-quickstart-create-account.md).
+* **An Azure storage account**. See [Create a storage account](../storage/common/storage-account-create.md).
 * **Visual Studio**.
 
 ## Create clusters

articles/iot-accelerators/iot-accelerators-device-simulation-protobuf.md

@@ -38,7 +38,7 @@ To follow the steps in this how-to guide, you need:
 * Postman. You can download [Postman for Mac, windows, or Linux](https://www.getpostman.com/apps).
 * An [IoT hub deployed to your Azure subscription](../iot-hub/iot-hub-create-through-portal.md). You need the IoT hub's connection string to complete the steps in this guide. You can get the connection string from the Azure portal.
 * A [Cosmos DB database deployed to your Azure subscription](../cosmos-db/create-sql-api-dotnet.md#create-account) that uses the SQL API and that's configured for [strong consistency](../cosmos-db/manage-account.md). You need the Cosmos DB database's connection string to complete the steps in this guide. You can get the connection string from the Azure portal.
-* An [Azure storage account deployed to your Azure subscription](../storage/common/storage-quickstart-create-account.md). You need the storage account's connection string to complete the steps in this guide. You can get the connection string from the Azure portal.
+* An [Azure storage account deployed to your Azure subscription](../storage/common/storage-account-create.md). You need the storage account's connection string to complete the steps in this guide. You can get the connection string from the Azure portal.
 
 ## Prepare your development environment
 

articles/iot-accelerators/iot-accelerators-remote-monitoring-bulk-configuration-update.md

@@ -41,7 +41,7 @@ To follow this tutorial, you need a deployed instance of the Remote Monitoring s
 
 If you haven't deployed the Remote Monitoring solution accelerator yet, you should complete the [Deploy a cloud-based remote monitoring solution](quickstart-remote-monitoring-deploy.md) quickstart.
 
-You need an Azure storage account to host your firmware files. You can use an existing storage account, or [create a new storage account](../storage/common/storage-quickstart-create-account.md) in your subscription.
+You need an Azure storage account to host your firmware files. You can use an existing storage account, or [create a new storage account](../storage/common/storage-account-create.md) in your subscription.
 
 The tutorial uses an [IoT DevKit](https://microsoft.github.io/azure-iot-developer-kit/) device as a sample device.