Update CLI reference URLs - anchor links

Author: kgremban

articles/iot-hub-device-update/configure-access-control-device-update.md

@@ -63,7 +63,7 @@ Replace the following placeholders with your own information:
 
 * *\<role>*: The Device Update role that you're assigning.
 * *\<user_group>*: The user or group that you want to assign the role to.
-* *\<account_id>*: The resource ID for the Device Update account that the user or group will get access to. You can retrieve the resource ID by using the [az iot device-update account show](/cli/azure/iot/du/account#az-iot-device-update-account-show) command and querying for the ID value: `az iot device-update account show -n <account_name> --query id`.
+* *\<account_id>*: The resource ID for the Device Update account that the user or group will get access to. You can retrieve the resource ID by using the [az iot device-update account show](/cli/azure/iot/du/account#az-iot-du-account-show) command and querying for the ID value: `az iot device-update account show -n <account_name> --query id`.
 
 ```azurecli-interactive
 az role assignment create --role '<role>' --assignee <user_group> --scope <account_id>

articles/iot-hub-device-update/configure-private-endpoints.md

@@ -103,7 +103,7 @@ You can use either the Azure portal or the Azure CLI to create private endpoints
 1. Fill all the required fields on the **Resource** tab
 
    * **Connection method**: Select **Connect to an Azure resource by resource ID or alias**.
-   * **Resource ID or alias**: Enter the Resource ID of the Device Update account. You can retrieve the resource ID of a Device Update account from the Azure portal by selecting **JSON View** on the **Overview** page. Or, you can retrieve it by using the [az iot du account show](/cli/azure/iot/du/account#az-iot-device-update-account-show) command and querying for the ID value: `az iot du account show -n <account_name> --query id`.
+   * **Resource ID or alias**: Enter the Resource ID of the Device Update account. You can retrieve the resource ID of a Device Update account from the Azure portal by selecting **JSON View** on the **Overview** page. Or, you can retrieve it by using the [az iot du account show](/cli/azure/iot/du/account#az-iot-du-account-show) command and querying for the ID value: `az iot du account show -n <account_name> --query id`.
    * **Target sub-resource**: Value must be **DeviceUpdate**
 
    :::image type="content" source="./media/configure-private-endpoints/private-endpoint-manual-create.png" alt-text="Screenshot showing the Resource page of the Create a private endpoint tab in Private Link Center.":::
@@ -130,7 +130,7 @@ Replace the following placeholders with your own information:
 * **PRIVATE_LINK_CONNECTION_NAME**: Name of the private link service connection.
 * **VIRTUAL_NETWORK_NAME**: Name of an existing virtual network associated with the subnet.
 * **SUBNET_NAME**: Name or ID of an existing subnet. If you use a subnet name, then you also need to include the virtual network name. If you use a subnet ID, you can omit the `--vnet-name` parameter.
-* **DEVICE_UPDATE_RESOURCE_ID**: You can retrieve the resource ID of a Device Update account from the Azure portal by selecting **JSON View** on the **Overview** page. Or, you can retrieve it by using the [az iot du account show](/cli/azure/iot/du/account#az-iot-device-update-account-show) command and querying for the ID value: `az iot du account show -n <account_name> --query id`.
+* **DEVICE_UPDATE_RESOURCE_ID**: You can retrieve the resource ID of a Device Update account from the Azure portal by selecting **JSON View** on the **Overview** page. Or, you can retrieve it by using the [az iot du account show](/cli/azure/iot/du/account#az-iot-du-account-show) command and querying for the ID value: `az iot du account show -n <account_name> --query id`.
 * **LOCATION**: Name of the Azure region. Your private endpoint must be in the same region as your virtual network, but can in a different region from the Device Update account.
 
 ```azurecli-interactive
@@ -192,7 +192,7 @@ There are four provisioning states:
 
 # [Azure CLI](#tab/cli)
 
-Use the [az iot du account private-endpoint-connection set](/cli/azure/iot/du/account/private-endpoint-connection#az-iot-device-update-account-private-endpoint-connection-set) command to manage private endpoint connection.
+Use the [az iot du account private-endpoint-connection set](/cli/azure/iot/du/account/private-endpoint-connection#az-iot-du-account-private-endpoint-connection-set) command to manage private endpoint connection.
 
 Replace the following placeholders with your own information:
 

articles/iot-hub-device-update/create-device-update-account.md

@@ -80,7 +80,7 @@ An IoT hub. It's required that you use an S1 (Standard) tier or above.
 
 # [Azure CLI](#tab/cli)
 
-Use the [az iot du account create](/cli/azure/iot/du/account#az-iot-device-update-account-create) command to create a new Device Update account.
+Use the [az iot du account create](/cli/azure/iot/du/account#az-iot-du-account-create) command to create a new Device Update account.
 
 Replace the following placeholders with your own information:
 
@@ -95,7 +95,7 @@ Replace the following placeholders with your own information:
 az iot du account create --resource-group <resource_group> --account <account_name> --location <region>
 ```
 
-Use the [az iot du instance create](/cli/azure/iot/du/instance#az-iot-device-update-instance-create) command to create a Device Update instance.
+Use the [az iot du instance create](/cli/azure/iot/du/instance#az-iot-du-instance-create) command to create a Device Update instance.
 
 An *instance* of Device Update is associated with a single IoT hub. Select the IoT hub that will be used with Device Update. When you link an IoT hub to a Device Update instance, a new shared access policy is automatically created give Device Update permissions to work with IoT Hub (registry write and service connect). This policy ensures that access is only limited to Device Update.
 

articles/iot-hub-device-update/create-update.md

@@ -47,7 +47,7 @@ Once you have your update files, create an import manifest to describe the updat
 > [!TIP]
 > Try the [image-based](device-update-raspberry-pi.md), [package-based](device-update-ubuntu-agent.md), or [proxy update](device-update-howto-proxy-updates.md) tutorials if you haven't already done so. You can also just view sample import manifest files from those tutorials for reference.
 
-The [az iot du init v5](/cli/azure/iot/du/update/init#az-iot-device-update-update-init-v5) command takes the following arguments:
+The [az iot du init v5](/cli/azure/iot/du/update/init#az-iot-du-update-init-v5) command takes the following arguments:
 
 * `--update-provider`, `--update-name`, and `--update-version`: These three parameters define the **updateId** object that is a unique identifier for each update.
 * `--compat`: The **compatibility** object is a set of name-value pairs that describe the properties of a device that this update is compatible with.
@@ -81,7 +81,7 @@ az iot du update init v5 \
 
 For handler properties, you may need to escape certain characters in your JSON. For example, use `'\'` to escape double-quotes if you're running the Azure CLI in PowerShell.
 
-The `init` command supports advanced scenarios, including the [related files feature](related-files.md) that allows you to define the relationship between different update files. For more examples and a complete list of optional parameters, see [az iot du init v5](/cli/azure/iot/du/update/init#az-iot-device-update-update-init-v5).
+The `init` command supports advanced scenarios, including the [related files feature](related-files.md) that allows you to define the relationship between different update files. For more examples and a complete list of optional parameters, see [az iot du init v5](/cli/azure/iot/du/update/init#az-iot-du-update-init-v5).
 
 Once you've created your import manifest and saved it as a JSON file, if you're ready to [import your update](import-update.md).