Merge pull request #134805 from DCtheGeek/dmc-links-hpccache

Links: Azure - hpc-cache

Author: PRMerger18

articles/hpc-cache/customer-keys.md

@@ -53,15 +53,15 @@ Key vault access permissions:
 
 * The user that creates the Azure HPC Cache must have permissions equivalent to the [Key Vault contributor role](../role-based-access-control/built-in-roles.md#key-vault-contributor). The same permissions are needed to set up and manage Azure Key Vault.
 
-  Read [Secure access to a key vault](../key-vault/key-vault-secure-your-key-vault.md) for more information.
+  Read [Secure access to a key vault](../key-vault/general/secure-your-key-vault.md) for more information.
 
 ## 1. Set up Azure Key Vault
 
 You can set up a key vault and key before you create the cache, or do it as part of cache creation. Make sure these resources meet the requirements outlined [above](#understand-key-vault-and-key-requirements).
 
 At cache creation time you must specify a vault, key, and key version to use for the cache's encryption.
 
-Read the [Azure Key Vault documentation](../key-vault/key-vault-overview.md) for details.
+Read the [Azure Key Vault documentation](../key-vault/general/overview.md) for details.
 
 > [!NOTE]
 > The Azure Key Vault must use the same subscription and be in the same region as the Azure HPC Cache. Make sure that the region you choose [supports the customer-managed keys feature](hpc-cache-overview.md#region-availability).
@@ -87,7 +87,7 @@ The user who creates the cache must have privileges equal to the [Key Vault cont
 
 1. After selecting a vault, select the individual key from the available options, or create a new key. The key must be a 2048-bit RSA key.
 
-1. Specify the version for the selected key. Learn more about versioning in the [Azure Key Vault documentation](../key-vault/about-keys-secrets-and-certificates.md#objects-identifiers-and-versioning).
+1. Specify the version for the selected key. Learn more about versioning in the [Azure Key Vault documentation](../key-vault/general/about-keys-secrets-certificates.md#objects-identifiers-and-versioning).
 
 Continue with the rest of the specifications and create the cache as described in [Create an Azure HPC Cache](hpc-cache-create.md).
 
@@ -145,4 +145,4 @@ These articles explain more about using Azure Key Vault and customer-managed key
 
 After you have created the Azure HPC Cache and authorized Key Vault-based encryption, continue to set up your cache by giving it access to your data sources.
 
-* [Add storage targets](hpc-cache-add-storage.md)
+* [Add storage targets](hpc-cache-add-storage.md)

articles/hpc-cache/hpc-cache-add-storage.md

@@ -69,9 +69,9 @@ When finished, click **OK** to add the storage target.
 
 ### Add the access control roles to your account
 
-Azure HPC Cache uses [Azure role-based access control (Azure RBAC)](https://docs.microsoft.com/azure/role-based-access-control/index) to authorize the cache service to access your storage account for Azure Blob storage targets.
+Azure HPC Cache uses [Azure role-based access control (Azure RBAC)](../role-based-access-control/index.yml) to authorize the cache service to access your storage account for Azure Blob storage targets.
 
-The storage account owner must explicitly add the roles [Storage Account Contributor](https://docs.microsoft.com/azure/role-based-access-control/built-in-roles#storage-account-contributor) and [Storage Blob Data Contributor](https://docs.microsoft.com/azure/role-based-access-control/built-in-roles#storage-blob-data-contributor) for the user "HPC Cache Resource Provider".
+The storage account owner must explicitly add the roles [Storage Account Contributor](../role-based-access-control/built-in-roles.md#storage-account-contributor) and [Storage Blob Data Contributor](../role-based-access-control/built-in-roles.md#storage-blob-data-contributor) for the user "HPC Cache Resource Provider".
 
 You can do this ahead of time, or by clicking a link on the page where you add a Blob storage target. Keep in mind that it can take up to five minutes for the role settings to propagate through the Azure environment, so you should wait a few minutes after adding the roles before creating a storage target.
 
@@ -347,4 +347,4 @@ After creating storage targets, continue with these tasks to get your cache read
 * [Mount the Azure HPC Cache](hpc-cache-mount.md)
 * [Move data to Azure Blob storage](hpc-cache-ingest.md)
 
-If you need to update any settings, you can [edit a storage target](hpc-cache-edit-storage.md).
+If you need to update any settings, you can [edit a storage target](hpc-cache-edit-storage.md).

articles/hpc-cache/hpc-cache-create.md

@@ -76,7 +76,7 @@ After you create the cache, you must authorize it to use the key vault service.
 
 ## Add resource tags (optional)
 
-The **Tags** page lets you add [resource tags](https://go.microsoft.com/fwlink/?linkid=873112) to your Azure HPC Cache instance.
+The **Tags** page lets you add [resource tags](../azure-resource-manager/management/tag-resources.md) to your Azure HPC Cache instance.
 
 ## Finish creating the cache
 
@@ -199,7 +199,7 @@ module and connect to your Azure account using the
 [Connect-AzAccount](/powershell/module/az.accounts/connect-azaccount) cmdlet. For more information
 about installing the Az PowerShell module, see
 [Install Azure PowerShell](/powershell/azure/install-az-ps). If you choose to use Cloud Shell, see
-[Overview of Azure Cloud Shell](https://docs.microsoft.com/azure/cloud-shell/overview) for
+[Overview of Azure Cloud Shell](../cloud-shell/overview.md) for
 more information.
 
 > [!IMPORTANT]
@@ -302,4 +302,4 @@ The message includes some useful information, including these items:
 After your cache appears in the **Resources** list, you can move to the next step.
 
 * [Define storage targets](hpc-cache-add-storage.md) to give your cache access to your data sources.
-* If you use customer-managed encryption keys, you need to [authorize Azure Key Vault encryption](customer-keys.md#3-authorize-azure-key-vault-encryption-from-the-cache) from the cache's overview page to complete your cache setup. You must do this step before you can add storage. Read [Use customer-managed encryption keys](customer-keys.md) for details.
+* If you use customer-managed encryption keys, you need to [authorize Azure Key Vault encryption](customer-keys.md#3-authorize-azure-key-vault-encryption-from-the-cache) from the cache's overview page to complete your cache setup. You must do this step before you can add storage. Read [Use customer-managed encryption keys](customer-keys.md) for details.

articles/hpc-cache/hpc-cache-prerequisites.md

@@ -60,7 +60,7 @@ If you only need access to Blob storage, you can use the default Azure-provided
 
 A simple DNS server also can be used to load balance client connections among all the available cache mount points.
 
-Learn more about Azure virtual networks and DNS server configurations in [Name resolution for resources in Azure virtual networks](https://docs.microsoft.com/azure/virtual-network/virtual-networks-name-resolution-for-vms-and-role-instances).
+Learn more about Azure virtual networks and DNS server configurations in [Name resolution for resources in Azure virtual networks](../virtual-network/virtual-networks-name-resolution-for-vms-and-role-instances.md).
 
 ## Permissions
 
@@ -105,7 +105,7 @@ If using an NFS storage system (for example, an on-premises hardware NAS system)
 
 More information is included in [Troubleshoot NAS configuration and NFS storage target issues](troubleshoot-nas.md).
 
-* **Network connectivity:** The Azure HPC Cache needs high-bandwidth network access between the cache subnet and the NFS system's data center. [ExpressRoute](https://docs.microsoft.com/azure/expressroute/) or similar access is recommended. If using a VPN, you might need to configure it to clamp TCP MSS at 1350 to make sure large packets are not blocked. Read [VPN packet size restrictions](troubleshoot-nas.md#adjust-vpn-packet-size-restrictions) for additional help troubleshooting VPN settings.
+* **Network connectivity:** The Azure HPC Cache needs high-bandwidth network access between the cache subnet and the NFS system's data center. [ExpressRoute](../expressroute/index.yml) or similar access is recommended. If using a VPN, you might need to configure it to clamp TCP MSS at 1350 to make sure large packets are not blocked. Read [VPN packet size restrictions](troubleshoot-nas.md#adjust-vpn-packet-size-restrictions) for additional help troubleshooting VPN settings.
 
 * **Port access:** The cache needs access to specific TCP/UDP ports on your storage system. Different types of storage have different port requirements.
 
@@ -158,4 +158,4 @@ If you want to create or manage Azure HPC Cache from the Azure command-line inte
 
 ## Next steps
 
-* [Create an Azure HPC Cache instance](hpc-cache-create.md) from the Azure portal
+* [Create an Azure HPC Cache instance](hpc-cache-create.md) from the Azure portal