Merge pull request #214931 from cmcclister/cm-linkfix-20221018-8

LinkFix: azure-docs-pr (2022-10) - 8

Author: tamarakhader

includes/cognitive-services-environment-variables.md

@@ -11,7 +11,7 @@ ms.author: aahi
 Your application must be authenticated to access Cognitive Services resources. For production, use a secure way of storing and accessing your credentials. For example, after you have a key for your resource, write it to a new environment variable on the local machine running the application.
 
 > [!TIP]
-> Don't include the key directly in your code, and never post it publicly. See the Cognitive Services [security](/azure/cognitive-services/security-features) article for more authentication options like [Azure Key Vault](/azure/cognitive-services/use-key-vault). 
+> Don't include the key directly in your code, and never post it publicly. See the Cognitive Services [security](../articles/cognitive-services/security-features.md) article for more authentication options like [Azure Key Vault](../articles/cognitive-services/use-key-vault.md). 
 
 To set the environment variable for your resource key, open a console window, and follow the instructions for your operating system and development environment. To set the `COGNITIVE_SERVICE_KEY` environment variable, replace `your-key` with one of the keys for your resource.
 
@@ -58,4 +58,4 @@ For iOS and macOS development, you set the environment variables in Xcode. For e
 For more configuration options, see the [Xcode documentation](https://help.apple.com/xcode/#/dev745c5c974).
 ***
 
-To set the environment variable for your Speech resource region, follow the same steps. Set `COGNITIVE_SERVICE_REGION` to the region of your resource. For example, `westus`.
+To set the environment variable for your Speech resource region, follow the same steps. Set `COGNITIVE_SERVICE_REGION` to the region of your resource. For example, `westus`.

includes/database-migration-service-ads.md

@@ -19,8 +19,8 @@ Check the following step-by-step tutorials for more information about each speci
 
 | Migration scenario | Migration mode
 |---------|---------|
-SQL Server to Azure SQL Managed Instance| [Online](/azure/dms/tutorial-sql-server-managed-instance-online-ads) / [Offline](/azure/dms/tutorial-sql-server-managed-instance-offline-ads)
-SQL Server to SQL Server on Azure Virtual Machine|[Online](/azure/dms/tutorial-sql-server-to-virtual-machine-online-ads) / [Offline](/azure/dms/tutorial-sql-server-to-virtual-machine-offline-ads)
-SQL Server to Azure SQL Database (Preview)| [Offline](/azure/dms/tutorial-sql-server-azure-sql-database-offline-ads)
+SQL Server to Azure SQL Managed Instance| [Online](../articles/dms/tutorial-sql-server-managed-instance-online-ads.md) / [Offline](../articles/dms/tutorial-sql-server-managed-instance-offline-ads.md)
+SQL Server to SQL Server on Azure Virtual Machine|[Online](../articles/dms/tutorial-sql-server-to-virtual-machine-online-ads.md) / [Offline](../articles/dms/tutorial-sql-server-to-virtual-machine-offline-ads.md)
+SQL Server to Azure SQL Database (Preview)| [Offline](../articles/dms/tutorial-sql-server-azure-sql-database-offline-ads.md)
 
-To learn more, see [Migrate databases with Azure SQL Migration extension for Azure Data Studio](/azure/dms/migration-using-azure-data-studio).
+To learn more, see [Migrate databases with Azure SQL Migration extension for Azure Data Studio](../articles/dms/migration-using-azure-data-studio.md).

includes/disk-encryption-key-vault.md

@@ -67,7 +67,7 @@ You can also create a key vault by using the [Resource Manager template](https:/
 ## Set key vault advanced access policies
 
 > [!IMPORTANT]
-> Newly-created key vaults have soft-delete on by default. If you are using a pre-existing key vault, you **must** enable soft-delete. See [Azure Key Vault soft-delete overview](/azure/key-vault/general/soft-delete-overview).
+> Newly-created key vaults have soft-delete on by default. If you are using a pre-existing key vault, you **must** enable soft-delete. See [Azure Key Vault soft-delete overview](../articles/key-vault/general/soft-delete-overview.md).
 
 The Azure platform needs access to the encryption keys or secrets in your key vault to make them available to the VM for booting and decrypting the volumes.
 
@@ -180,4 +180,4 @@ $KeyVault = Get-AzKeyVault -VaultName "<your-unique-keyvault-name>" -ResourceGro
 $KEK = Get-AzKeyVaultKey -VaultName "<your-unique-keyvault-name>" -Name "myKEK"
 
 Set-AzVMDiskEncryptionExtension -ResourceGroupName MyResourceGroup -VMName "MyVM" -DiskEncryptionKeyVaultUrl $KeyVault.VaultUri -DiskEncryptionKeyVaultId $KeyVault.ResourceId -KeyEncryptionKeyVaultId $KeyVault.ResourceId -KeyEncryptionKeyUrl $KEK.Id -SkipVmBackup -VolumeType All
- ```
+ ```

includes/dms-ads-sqldb-prereq.md

@@ -18,4 +18,4 @@ ms.date: 09/30/2022
 * Create a target [Azure SQL Database](/azure/azure-sql/database/single-database-create-quickstart).
 * Ensure that the login used to connect the source SQL Server is a member of the `db_datareader` and the login for the target SQL server is `db_owner`.
 * Migrate database schema from source to target using [SQL Server dacpac extension](/sql/azure-data-studio/extensions/sql-server-dacpac-extension), or [SQL Database Projects extension](/sql/azure-data-studio/extensions/sql-database-project-extension) for Azure Data Studio.
-* If you're using the Azure Database Migration Service for the first time, ensure that Microsoft.DataMigration resource provider is registered in your subscription. You can follow the steps to [register the resource provider](/azure/dms/quickstart-create-data-migration-service-portal.md#register-the-resource-provider)
+* If you're using the Azure Database Migration Service for the first time, ensure that Microsoft.DataMigration resource provider is registered in your subscription. You can follow the steps to [register the resource provider](../articles/dms/quickstart-create-data-migration-service-portal.md#register-the-resource-provider)

includes/dms-ads-sqlmi-prereq.md

@@ -12,7 +12,7 @@ ms.date: 09/30/2022
     - Contributor for the target Azure SQL Managed Instance (and Storage Account to upload your database backup files from SMB network share).
     - Reader role for the Azure Resource Groups containing the target Azure SQL Managed Instance or the Azure storage account.
     - Owner or Contributor role for the Azure subscription (required if creating a new DMS service).
-    - As an alternative to using the above built-in roles, you can assign a custom role as defined in [this article.](/azure/dms/resource-custom-roles-sql-db-managed-instance-ads)
+    - As an alternative to using the above built-in roles, you can assign a custom role as defined in [this article.](../articles/dms/resource-custom-roles-sql-db-managed-instance-ads.md)
     > [!IMPORTANT]
     > Azure account is only required when configuring the migration steps and is not required for assessment or Azure recommendation steps in the migration wizard.
 * Create a target [Azure SQL Managed Instance](/azure/azure-sql/managed-instance/instance-create-quickstart).
@@ -22,7 +22,7 @@ ms.date: 09/30/2022
     - Azure storage account file share or blob container 
 
     > [!IMPORTANT]
-    > - If your database backup files are provided in an SMB network share, [Create an Azure storage account](/azure/storage/common/storage-account-create) that allows the DMS service to upload the database backup files.  Make sure to create the Azure Storage Account in the same region as the Azure Database Migration Service instance is created.
+    > - If your database backup files are provided in an SMB network share, [Create an Azure storage account](../articles/storage/common/storage-account-create.md) that allows the DMS service to upload the database backup files.  Make sure to create the Azure Storage Account in the same region as the Azure Database Migration Service instance is created.
     > - Azure Database Migration Service does not initiate any backups, and instead uses existing backups, which you may already have as part of your disaster recovery plan, for the migration.
     > - You need to take [backups using the `WITH CHECKSUM` option](/sql/relational-databases/backup-restore/enable-or-disable-backup-checksums-during-backup-or-restore-sql-server). 
     > - Each backup can be written to either a separate backup file or multiple backup files. However, appending multiple backups (i.e. full and t-log) into a single backup media is not supported. 
@@ -43,5 +43,5 @@ ms.date: 09/30/2022
     > [!TIP]
     > If your database backup files are already provided in an Azure storage account, self-hosted integration runtime is not required during the migration process.
 
-* When using self-hosted integration runtime, ensure that the machine where the runtime is installed can connect to the source SQL Server instance and the network file share where backup files are located. Outbound port 445 should be enabled to access the network file share. Also, see [recommendations](/azure/dms/migration-using-azure-data-studio.md#recommendations-for-using-self-hosted-integration-runtime-for-database-migrations) for using self-hosted integration runtime](migration-using-azure-data-studio.md#recommendations-for-using-self-hosted-integration-runtime-for-database-migrations)
-* If you're using the Azure Database Migration Service for the first time, ensure that Microsoft.DataMigration resource provider is registered in your subscription. You can follow the steps to [register the resource provider](/azure/dms/quickstart-create-data-migration-service-portal.md#register-the-resource-provider)
+* When using self-hosted integration runtime, ensure that the machine where the runtime is installed can connect to the source SQL Server instance and the network file share where backup files are located. Outbound port 445 should be enabled to access the network file share. Also, see [recommendations](../articles/dms/migration-using-azure-data-studio.md#recommendations-for-using-self-hosted-integration-runtime-for-database-migrations) for using self-hosted integration runtime](migration-using-azure-data-studio.md#recommendations-for-using-self-hosted-integration-runtime-for-database-migrations)
+* If you're using the Azure Database Migration Service for the first time, ensure that Microsoft.DataMigration resource provider is registered in your subscription. You can follow the steps to [register the resource provider](../articles/dms/quickstart-create-data-migration-service-portal.md#register-the-resource-provider)

includes/dms-ads-sqlvm-prereq.md

@@ -12,7 +12,7 @@ ms.date: 09/30/2022
     - Contributor for the target Azure SQL Managed Instance (and Storage Account to upload your database backup files from SMB network share).
     - Reader role for the Azure Resource Groups containing the target Azure SQL Managed Instance or the Azure storage account.
     - Owner or Contributor role for the Azure subscription.
-    - As an alternative to using the above built-in roles you can assign a custom role as defined in [this article.](/azure/dms/resource-custom-roles-sql-db-virtual-machine-ads.md)
+    - As an alternative to using the above built-in roles you can assign a custom role as defined in [this article.](../articles/dms/resource-custom-roles-sql-db-virtual-machine-ads.md)
     > [!IMPORTANT]
     > Azure account is only required when configuring the migration steps and is not required for assessment or Azure recommendation steps in the migration wizard.
 * Create a target [SQL Server on Azure Virtual Machine](/azure/azure-sql/virtual-machines/windows/create-sql-vm-portal).
@@ -25,7 +25,7 @@ ms.date: 09/30/2022
     - Azure storage account file share or blob container 
 
     > [!IMPORTANT]
-    > - If your database backup files are provided in an SMB network share, [Create an Azure storage account](/azure/storage/common/storage-account-create) that allows the DMS service to upload the database backup files.  Make sure to create the Azure Storage Account in the same region as the Azure Database Migration Service instance is created.
+    > - If your database backup files are provided in an SMB network share, [Create an Azure storage account](../articles/storage/common/storage-account-create.md) that allows the DMS service to upload the database backup files.  Make sure to create the Azure Storage Account in the same region as the Azure Database Migration Service instance is created.
     > - Azure Database Migration Service does not initiate any backups, and instead uses existing backups, which you may already have as part of your disaster recovery plan, for the migration.
     > - Each backup can be written to either a separate backup file or multiple backup files. However, appending multiple backups (i.e. full and t-log) into a single backup media is not supported. 
     > - Use compressed backups to reduce the likelihood of experiencing potential issues associated with migrating large backups.
@@ -34,7 +34,7 @@ ms.date: 09/30/2022
     > [!TIP]
     > If your database contains sensitive data that is protected by [Always Encrypted](/sql/relational-databases/security/encryption/configure-always-encrypted-using-sql-server-management-studio), migration process using Azure Data Studio with DMS will automatically migrate your Always Encrypted keys to your target SQL Server on Azure Virtual Machine.
 
-* If your database backups are in a network file share, provide a machine to install [self-hosted integration runtime](/azure/data-factory/create-self-hosted-integration-runtime) to access and migrate database backups. The migration wizard provides the link and authentication keys to download and install your self-hosted integration runtime. In preparation for the migration, ensure that the machine where you plan to install the self-hosted integration runtime has the following outbound firewall rules and domain names enabled:
+* If your database backups are in a network file share, provide a machine to install [self-hosted integration runtime](../articles/data-factory/create-self-hosted-integration-runtime.md) to access and migrate database backups. The migration wizard provides the link and authentication keys to download and install your self-hosted integration runtime. In preparation for the migration, ensure that the machine where you plan to install the self-hosted integration runtime has the following outbound firewall rules and domain names enabled:
 
     | Domain names                                          | Outbound ports | Description                |
     | ----------------------------------------------------- | -------------- | ---------------------------|
@@ -45,5 +45,5 @@ ms.date: 09/30/2022
     > [!TIP]
     > If your database backup files are already provided in an Azure storage account, self-hosted integration runtime is not required during the migration process.
 
-* Runtime is installed on the machine using self-hosted integration runtime. The machine will connect to the source SQL Server instance and the network file share where backup files are located. Outbound port 445 should be enabled to access the network file share. Also, see [recommendations](/azure/dms/migration-using-azure-data-studio.md#recommendations-for-using-self-hosted-integration-runtime-for-database-migrations) for using self-hosted integration runtime](migration-using-azure-data-studio.md#recommendations-for-using-self-hosted-integration-runtime-for-database-migrations)
-* If you're using the Azure Database Migration Service for the first time, ensure that Microsoft.DataMigration resource provider is registered in your subscription. You can follow the steps to [register the resource provider](/azure/dms/quickstart-create-data-migration-service-portal.md#register-the-resource-provider)
+* Runtime is installed on the machine using self-hosted integration runtime. The machine will connect to the source SQL Server instance and the network file share where backup files are located. Outbound port 445 should be enabled to access the network file share. Also, see [recommendations](../articles/dms/migration-using-azure-data-studio.md#recommendations-for-using-self-hosted-integration-runtime-for-database-migrations) for using self-hosted integration runtime](migration-using-azure-data-studio.md#recommendations-for-using-self-hosted-integration-runtime-for-database-migrations)
+* If you're using the Azure Database Migration Service for the first time, ensure that Microsoft.DataMigration resource provider is registered in your subscription. You can follow the steps to [register the resource provider](../articles/dms/quickstart-create-data-migration-service-portal.md#register-the-resource-provider)

includes/iot-hub-prepare-resource-manager.md

@@ -10,7 +10,7 @@ You must authenticate all the operations that you perform on resources using the
 
 Install the [Azure PowerShell cmdlets][lnk-powershell-install] before you continue.
 
-The following steps show how to set up authentication for your app to register with Azure Active Directory. You can run these commands in a standard PowerShell session. Registering with Azure Active Directory is necessary to authenticate any future REST calls. For more information, see [How and why applications are added to Azure AD](/azure/active-directory/develop/active-directory-how-applications-are-added).
+The following steps show how to set up authentication for your app to register with Azure Active Directory. You can run these commands in a standard PowerShell session. Registering with Azure Active Directory is necessary to authenticate any future REST calls. For more information, see [How and why applications are added to Azure AD](../articles/active-directory/develop/active-directory-how-applications-are-added.md).
 
 1. Sign in to your Azure subscription using the following command. If you're using PowerShell in Azure Cloud Shell you're already signed in, so you can skip this step.
 
@@ -37,7 +37,7 @@ The following steps show how to set up authentication for your app to register w
 1. Create a new Azure Active Directory application using the following command, replacing these placeholders with your own values:
 
    * **{Display name}:** a display name for your application such as **MySampleApp**
-   * **{Application identifier}:** A unique identifier such as your primary domain. To find the primary domain associated with your subscription, go to the [Azure portal](https://ms.portal.azure.com/#home) in the **Azure Active Directory** service on its **Overview page** and find **Primary domain**. See the different domain possibilities in the [Azure Active Directory app manifest](/azure/active-directory/develop/reference-app-manifest#identifieruris-attribute). Be sure to add `/your-id` at the end of your domain (`your-Id` can be any name), for example, `"https://microsoft.onmicrosoft.com/my-unique-ad-app"`.
+   * **{Application identifier}:** A unique identifier such as your primary domain. To find the primary domain associated with your subscription, go to the [Azure portal](https://ms.portal.azure.com/#home) in the **Azure Active Directory** service on its **Overview page** and find **Primary domain**. See the different domain possibilities in the [Azure Active Directory app manifest](../articles/active-directory/develop/reference-app-manifest.md#identifieruris-attribute). Be sure to add `/your-id` at the end of your domain (`your-Id` can be any name), for example, `"https://microsoft.onmicrosoft.com/my-unique-ad-app"`.
 
    :::image type="content" source="/includes/media/iot-hub-prepare-resource-manager/find-domain.png" alt-text="Screenshot showing location of your Primary domain in the Azure portal.":::
 
@@ -55,7 +55,7 @@ The following steps show how to set up authentication for your app to register w
     New-AzRoleAssignment -RoleDefinitionName "Owner" -ApplicationId {MyAppId}
     ```
 
-   To understand roles and permissions, see [Create or update Azure custom roles using Azure PowerShell](/azure/role-based-access-control/custom-roles-powershell).
+   To understand roles and permissions, see [Create or update Azure custom roles using Azure PowerShell](../articles/role-based-access-control/custom-roles-powershell.md).
 
 With your new Azure AD application, you can now authenticate from your custom C# application.