Merge pull request #186274 from v-haiboz/feature/Task536167-7

task#536167:[Refresh link]Replace bookmarks in repo(pr 7)

Author: PRMerger4

articles/azure-functions/disable-function.md

@@ -27,7 +27,7 @@ Even when you publish to your function app from a local project, you can still u
 
 # [Azure CLI](#tab/azurecli)
 
-In the Azure CLI, you use the [`az functionapp config appsettings set`](/cli/azure/functionapp/config/appsettings#az_functionapp_config_appsettings_set) command to create and modify the app setting. The following command disables a function named `QueueTrigger` by creating an app setting named `AzureWebJobs.QueueTrigger.Disabled` and setting it to `true`. 
+In the Azure CLI, you use the [`az functionapp config appsettings set`](/cli/azure/functionapp/config/appsettings#az-functionapp-config-appsettings-set) command to create and modify the app setting. The following command disables a function named `QueueTrigger` by creating an app setting named `AzureWebJobs.QueueTrigger.Disabled` and setting it to `true`. 
 
 ```azurecli-interactive
 az functionapp config appsettings set --name <FUNCTION_APP_NAME> \

articles/azure-functions/functions-deployment-slots.md

@@ -118,7 +118,7 @@ All slots scale to the same number of workers as the production slot.
 
 ## Add a slot
 
-You can add a slot via the [CLI](/cli/azure/functionapp/deployment/slot#az_functionapp_deployment_slot_create) or through the portal. The following steps demonstrate how to create a new slot in the portal:
+You can add a slot via the [CLI](/cli/azure/functionapp/deployment/slot#az-functionapp-deployment-slot-create) or through the portal. The following steps demonstrate how to create a new slot in the portal:
 
 1. Navigate to your function app.
 
@@ -132,7 +132,7 @@ You can add a slot via the [CLI](/cli/azure/functionapp/deployment/slot#az_funct
 
 ## Swap slots
 
-You can swap slots via the [CLI](/cli/azure/functionapp/deployment/slot#az_functionapp_deployment_slot_swap) or through the portal. The following steps demonstrate how to swap slots in the portal:
+You can swap slots via the [CLI](/cli/azure/functionapp/deployment/slot#az-functionapp-deployment-slot-swap) or through the portal. The following steps demonstrate how to swap slots in the portal:
 
 1. Navigate to the function app.
 1. Select **Deployment slots**, and then select **Swap**.
@@ -151,7 +151,7 @@ If a swap results in an error or you simply want to "undo" a swap, you can roll
 
 ## Remove a slot
 
-You can remove a slot via the [CLI](/cli/azure/functionapp/deployment/slot#az_functionapp_deployment_slot_delete) or through the portal. The following steps demonstrate how to remove a slot in the portal:
+You can remove a slot via the [CLI](/cli/azure/functionapp/deployment/slot#az-functionapp-deployment-slot-delete) or through the portal. The following steps demonstrate how to remove a slot in the portal:
 
 1. Navigate to **Deployment slots** in the function app, and then select the slot name.
 
@@ -173,11 +173,11 @@ You can remove a slot via the [CLI](/cli/azure/functionapp/deployment/slot#az_fu
 
 Using the [Azure CLI](/cli/azure/functionapp/deployment/slot), you can automate the following actions for a slot:
 
-- [create](/cli/azure/functionapp/deployment/slot#az_functionapp_deployment_slot_create)
-- [delete](/cli/azure/functionapp/deployment/slot#az_functionapp_deployment_slot_delete)
-- [list](/cli/azure/functionapp/deployment/slot#az_functionapp_deployment_slot_list)
-- [swap](/cli/azure/functionapp/deployment/slot#az_functionapp_deployment_slot_swap)
-- [auto-swap](/cli/azure/functionapp/deployment/slot#az_functionapp_deployment_slot_auto_swap)
+- [create](/cli/azure/functionapp/deployment/slot#az-functionapp-deployment-slot-create)
+- [delete](/cli/azure/functionapp/deployment/slot#az-functionapp-deployment-slot-delete)
+- [list](/cli/azure/functionapp/deployment/slot#az-functionapp-deployment-slot-list)
+- [swap](/cli/azure/functionapp/deployment/slot#az-functionapp-deployment-slot-swap)
+- [auto-swap](/cli/azure/functionapp/deployment/slot#az-functionapp-deployment-slot-auto-swap)
 
 ## Change App Service plan
 

articles/azure-functions/set-runtime-version.md

@@ -104,7 +104,7 @@ az functionapp config appsettings set --name <FUNCTION_APP> \
 
 Replace `<FUNCTION_APP>` with the name of your function app. Also replace `<RESOURCE_GROUP>` with the name of the resource group for your function app. Also, replace `<VERSION>` with either a specific version, or `~4`, `~3`, `~2`, or `~1`.
 
-Choose **Try it** in the previous code example to run the command in [Azure Cloud Shell](../cloud-shell/overview.md). You can also run the [Azure CLI locally](/cli/azure/install-azure-cli) to execute this command. When running locally, you must first run [az login](/cli/azure/reference-index#az_login) to sign in.
+Choose **Try it** in the previous code example to run the command in [Azure Cloud Shell](../cloud-shell/overview.md). You can also run the [Azure CLI locally](/cli/azure/install-azure-cli) to execute this command. When running locally, you must first run [az login](/cli/azure/reference-index#az-login) to sign in.
 
 # [PowerShell](#tab/powershell)
 
@@ -165,7 +165,7 @@ az functionapp config set --name <FUNCTION_APP> \
 
 Replace `<FUNCTION_APP>` with the name of your function app. Also replace `<RESOURCE_GROUP>` with the name of the resource group for your function app. Also, replace `<LINUX_FX_VERSION>` with the value of a specific image as described above.
 
-You can run this command from the [Azure Cloud Shell](../cloud-shell/overview.md) by choosing **Try it** in the preceding code sample. You can also use the [Azure CLI locally](/cli/azure/install-azure-cli) to execute this command after executing [az login](/cli/azure/reference-index#az_login) to sign in.
+You can run this command from the [Azure Cloud Shell](../cloud-shell/overview.md) by choosing **Try it** in the preceding code sample. You can also use the [Azure CLI locally](/cli/azure/install-azure-cli) to execute this command after executing [az login](/cli/azure/reference-index#az-login) to sign in.
 
 # [PowerShell](#tab/powershell)
 

articles/azure-resource-manager/management/manage-resource-groups-cli.md

@@ -25,29 +25,29 @@ The resource group stores metadata about the resources. When you specify a locat
 
 ## Create resource groups
 
-to create a resource group, use [az group create](/cli/azure/group#az_group_create).
+to create a resource group, use [az group create](/cli/azure/group#az-group-create).
 
 ```azurecli-interactive
 az group create --name demoResourceGroup --location westus
 ```
 
 ## List resource groups
 
-To list the resource groups in your subscription, use [az group list](/cli/azure/group#az_group_list).
+To list the resource groups in your subscription, use [az group list](/cli/azure/group#az-group-list).
 
 ```azurecli-interactive
 az group list
 ```
 
-To get one resource group, use [az group show](/cli/azure/group#az_group_show).
+To get one resource group, use [az group show](/cli/azure/group#az-group-show).
 
 ```azurecli-interactive
 az group show --name exampleGroup
 ```
 
 ## Delete resource groups
 
-To delete a resource group, use [az group delete](/cli/azure/group#az_group_delete).
+To delete a resource group, use [az group delete](/cli/azure/group#az-group-delete).
 
 ```azurecli-interactive
 az group delete --name exampleGroup
@@ -65,7 +65,7 @@ The following example creates a storage account. The name you provide for the st
 az storage account create --resource-group exampleGroup --name examplestore --location westus --sku Standard_LRS --kind StorageV2
 ```
 
-To deploy an ARM template or Bicep file, use [az deployment group create](/cli/azure/deployment/group#az_deployment_group_create).
+To deploy an ARM template or Bicep file, use [az deployment group create](/cli/azure/deployment/group#az-deployment-group-create).
 
 ```azurecli-interactive
 az deployment group create --resource-group exampleGroup --template-file storage.bicep
@@ -79,19 +79,19 @@ For more information about deploying a Bicep file, see [Deploy resources with Bi
 
 Locking prevents other users in your organization from accidentally deleting or modifying critical resources.
 
-To prevent a resource group and its resources from being deleted, use [az lock create](/cli/azure/lock#az_lock_create).
+To prevent a resource group and its resources from being deleted, use [az lock create](/cli/azure/lock#az-lock-create).
 
 ```azurecli-interactive
 az lock create --name LockGroup --lock-type CanNotDelete --resource-group exampleGroup
 ```
 
-To get the locks for a resource group, use [az lock list](/cli/azure/lock#az_lock_list).
+To get the locks for a resource group, use [az lock list](/cli/azure/lock#az-lock-list).
 
 ```azurecli-interactive
 az lock list --resource-group exampleGroup
 ```
 
-To delete a lock, use [az lock delete](/cli/azure/lock#az_lock_delete)
+To delete a lock, use [az lock delete](/cli/azure/lock#az-lock-delete)
 
 ```azurecli-interactive
 az lock delete --name exampleLock --resource-group exampleGroup

articles/azure-resource-manager/templates/deploy-to-resource-group.md

@@ -43,7 +43,7 @@ To deploy to a resource group, use the resource group deployment commands.
 
 # [Azure CLI](#tab/azure-cli)
 
-For Azure CLI, use [az deployment group create](/cli/azure/deployment/group#az_deployment_group_create). The following example deploys a template to create a resource group:
+For Azure CLI, use [az deployment group create](/cli/azure/deployment/group#az-deployment-group-create). The following example deploys a template to create a resource group:
 
 ```azurecli-interactive
 az deployment group create \

articles/azure-sql/database/single-database-scale.md

@@ -21,7 +21,7 @@ After initially picking the number of vCores or DTUs, you can scale a single dat
 * [Transact-SQL](/sql/t-sql/statements/alter-database-transact-sql#overview-sql-database)
 * [Azure portal](single-database-manage.md#the-azure-portal)
 * [PowerShell](/powershell/module/az.sql/set-azsqldatabase)
-* [Azure CLI](/cli/azure/sql/db#az_sql_db_update)
+* [Azure CLI](/cli/azure/sql/db#az-sql-db-update)
 * [REST API](/rest/api/sql/databases/update)
 
 > [!IMPORTANT]
@@ -122,7 +122,7 @@ You're billed for each hour a database exists using the highest service tier + c
 ### vCore-based purchasing model
 
 - Storage can be provisioned up to the data storage max size limit using 1-GB increments. The minimum configurable data storage is 1 GB. For data storage max size limits in each service objective, see resource limit documentation pages for [Resource limits for single databases using the vCore purchasing model](resource-limits-vcore-single-databases.md) and [Resource limits for single databases using the DTU purchasing model](resource-limits-dtu-single-databases.md).
-- Data storage for a single database can be provisioned by increasing or decreasing its max size using the [Azure portal](https://portal.azure.com), [Transact-SQL](/sql/t-sql/statements/alter-database-transact-sql#examples-1), [PowerShell](/powershell/module/az.sql/set-azsqldatabase), [Azure CLI](/cli/azure/sql/db#az_sql_db_update), or [REST API](/rest/api/sql/databases/update). If the max size value is specified in bytes, it must be a multiple of 1 GB (1073741824 bytes).
+- Data storage for a single database can be provisioned by increasing or decreasing its max size using the [Azure portal](https://portal.azure.com), [Transact-SQL](/sql/t-sql/statements/alter-database-transact-sql#examples-1), [PowerShell](/powershell/module/az.sql/set-azsqldatabase), [Azure CLI](/cli/azure/sql/db#az-sql-db-update), or [REST API](/rest/api/sql/databases/update). If the max size value is specified in bytes, it must be a multiple of 1 GB (1073741824 bytes).
 - The amount of data that can be stored in the data files of a database is limited by the configured data storage max size. In addition to that storage, Azure SQL Database automatically allocates 30% more storage to be used for the transaction log.
 - Azure SQL Database automatically allocates 32 GB per vCore for the `tempdb` database. `tempdb` is located on the local SSD storage in all service tiers.
 - The price of storage for a single database or an elastic pool is the sum of data storage and transaction log storage amounts multiplied by the storage unit price of the service tier. The cost of `tempdb` is included in the price. For details on storage price, see [Azure SQL Database pricing](https://azure.microsoft.com/pricing/details/sql-database/).
@@ -133,7 +133,7 @@ You're billed for each hour a database exists using the highest service tier + c
 ### DTU-based purchasing model
 
 - The DTU price for a single database includes a certain amount of storage at no additional cost. Extra storage beyond the included amount can be provisioned for an additional cost up to the max size limit in increments of 250 GB up to 1 TB, and then in increments of 256 GB beyond 1 TB. For included storage amounts and max size limits, see [Single database: Storage sizes and compute sizes](resource-limits-dtu-single-databases.md#single-database-storage-sizes-and-compute-sizes).
-- Extra storage for a single database can be provisioned by increasing its max size using the Azure portal, [Transact-SQL](/sql/t-sql/statements/alter-database-transact-sql#examples-1), [PowerShell](/powershell/module/az.sql/set-azsqldatabase), the [Azure CLI](/cli/azure/sql/db#az_sql_db_update), or the [REST API](/rest/api/sql/databases/update).
+- Extra storage for a single database can be provisioned by increasing its max size using the Azure portal, [Transact-SQL](/sql/t-sql/statements/alter-database-transact-sql#examples-1), [PowerShell](/powershell/module/az.sql/set-azsqldatabase), the [Azure CLI](/cli/azure/sql/db#az-sql-db-update), or the [REST API](/rest/api/sql/databases/update).
 - The price of extra storage for a single database is the extra storage amount multiplied by the extra storage unit price of the service tier. For details on the price of extra storage, see [Azure SQL Database pricing](https://azure.microsoft.com/pricing/details/sql-database/).
 
 > [!IMPORTANT]

articles/data-factory/how-to-create-schedule-trigger.md

@@ -252,31 +252,31 @@ This section shows you how to use Azure CLI to create, start, and monitor a sche
     - The trigger is associated with the **Adfv2QuickStartPipeline** pipeline. To associate multiple pipelines with a trigger, add more **pipelineReference** sections.
     - The pipeline in the Quickstart takes two **parameters** values: **inputPath** and **outputPath**. And you pass values for these parameters from the trigger.
 
-1. Create a trigger by using the [az datafactory trigger create](/cli/azure/datafactory/trigger#az_datafactory_trigger_create) command:
+1. Create a trigger by using the [az datafactory trigger create](/cli/azure/datafactory/trigger#az-datafactory-trigger-create) command:
 
     ```azurecli
     az datafactory trigger create --resource-group "ADFQuickStartRG" --factory-name "ADFTutorialFactory"  --name "MyTrigger" --properties @MyTrigger.json  
     ```
 
-1. Confirm that the status of the trigger is **Stopped** by using the [az datafactory trigger show](/cli/azure/datafactory/trigger#az_datafactory_trigger_show) command:
+1. Confirm that the status of the trigger is **Stopped** by using the [az datafactory trigger show](/cli/azure/datafactory/trigger#az-datafactory-trigger-show) command:
 
     ```azurecli
     az datafactory trigger show --resource-group "ADFQuickStartRG" --factory-name "ADFTutorialFactory" --name "MyTrigger" 
     ```
 
-1. Start the trigger by using the [az datafactory trigger start](/cli/azure/datafactory/trigger#az_datafactory_trigger_start) command:
+1. Start the trigger by using the [az datafactory trigger start](/cli/azure/datafactory/trigger#az-datafactory-trigger-start) command:
 
     ```azurecli
     az datafactory trigger start --resource-group "ADFQuickStartRG" --factory-name "ADFTutorialFactory" --name "MyTrigger" 
     ```
 
-1. Confirm that the status of the trigger is **Started** by using the [az datafactory trigger show](/cli/azure/datafactory/trigger#az_datafactory_trigger_show) command:
+1. Confirm that the status of the trigger is **Started** by using the [az datafactory trigger show](/cli/azure/datafactory/trigger#az-datafactory-trigger-show) command:
 
     ```azurecli
     az datafactory trigger show --resource-group "ADFQuickStartRG" --factory-name "ADFTutorialFactory" --name "MyTrigger" 
     ```
 
-1. Get the trigger runs in Azure CLI by using the [az datafactory trigger-run query-by-factory](/cli/azure/datafactory/trigger-run#az_datafactory_trigger_run_query_by_factory) command. To get information about the trigger runs, execute the following command periodically. Update the **last-updated-after** and  **last-updated-before** values to match the values in your trigger definition:
+1. Get the trigger runs in Azure CLI by using the [az datafactory trigger-run query-by-factory](/cli/azure/datafactory/trigger-run#az-datafactory-trigger-run-query-by-factory) command. To get information about the trigger runs, execute the following command periodically. Update the **last-updated-after** and  **last-updated-before** values to match the values in your trigger definition:
 
     ```azurecli
     az datafactory trigger-run query-by-factory --resource-group "ADFQuickStartRG" --factory-name "ADFTutorialFactory" --filters operand="TriggerName" operator="Equals" values="MyTrigger" --last-updated-after "2017-12-08T00:00:00" --last-updated-before "2017-12-08T01:00:00"