Merge pull request #296460 from baanders/3-17-ki

[SCOPED] ADT: Add known CLI issue

Author: denrea

articles/digital-twins/concepts-3d-scenes-studio.md

@@ -49,7 +49,7 @@ To share your scenes with someone else, the recipient will need at least *Reader
 ## Set up
 
 To work with 3D Scenes Studio, you'll need the following required resources:
-* An [Azure Digital Twins instance](how-to-set-up-instance-cli.md)
+* An [Azure Digital Twins instance](how-to-set-up-instance-portal.md)
     * You'll need *Azure Digital Twins Data Owner* or *Azure Digital Twins Data Reader* access to the instance
     * The instance should be populated with [models](concepts-models.md) and [twins](concepts-twins-graph.md)
 

articles/digital-twins/concepts-cli.md

@@ -30,6 +30,8 @@ Some of the actions you can do using the command set include:
 
 The command set is called `az dt`, and is part of the [Azure IoT extension for Azure CLI](https://github.com/Azure/azure-iot-cli-extension). You can view the full list of commands and their usage as part of the reference documentation for the `az iot` command set: [az dt command reference](/cli/azure/dt).
 
+[!INCLUDE [digital-twins-cli-issue](../../includes/digital-twins-cli-issue.md)]
+
 ## Uses (deploy and validate)
 
 Apart from generally managing your instance, the CLI is also a useful tool for deployment and validation.

articles/digital-twins/how-to-create-app-registration.md

@@ -19,6 +19,8 @@ ms.service: azure-digital-twins
 
 This article describes how to create an [Microsoft Entra ID](../active-directory/fundamentals/active-directory-whatis.md) *app registration* that can access Azure Digital Twins. This article includes steps for the [Azure portal](https://portal.azure.com) and the [Azure CLI](/cli/azure/what-is-azure-cli).
 
+[!INCLUDE [digital-twins-cli-issue](../../includes/digital-twins-cli-issue.md)]
+
 When working with Azure Digital Twins, it's common to interact with your instance through client applications. Those applications need to authenticate with Azure Digital Twins, and some of the [authentication mechanisms](how-to-authenticate-client.md) that apps can use involve an app registration.
 
 The app registration isn't required for all authentication scenarios. However, if you're using an authentication strategy or code sample that does require an app registration, this article shows you how to set one up and grant it permissions to the Azure Digital Twins APIs. It also covers how to collect important values that you need to use the app registration when authenticating.
@@ -240,6 +242,8 @@ The app registration should show up in the list along with the role you assigned
 
 # [CLI](#tab/cli)
 
+[!INCLUDE [digital-twins-cli-issue](../../includes/digital-twins-cli-issue.md)]
+
 Use the [az dt role-assignment create](/cli/azure/dt/role-assignment#az-dt-role-assignment-create) command to assign the role (you must have [sufficient permissions](how-to-set-up-instance-cli.md#prerequisites-permission-requirements) in the Azure subscription). The command requires you to pass in the name of the role you want to assign, the name of your Azure Digital Twins instance, and either the name or the object ID of the app registration.
 
 ```azurecli-interactive

articles/digital-twins/how-to-create-data-history-connection.md

@@ -171,6 +171,8 @@ This command also creates three tables in your Azure Data Explorer database to s
 
 # [CLI](#tab/cli) 
 
+[!INCLUDE [digital-twins-cli-issue](../../includes/digital-twins-cli-issue.md)]
+
 Use the command in this section to create a data history connection and the tables in Azure Data Explorer. The command always creates a table for historized twin property updates, and it includes parameters to create the tables for relationship lifecycle and twin lifecycle events.
 
 >[!NOTE]

articles/digital-twins/how-to-create-endpoints.md

@@ -20,6 +20,8 @@ This article explains how to create an *endpoint* for Azure Digital Twin events
 
 Routing [event notifications](concepts-event-notifications.md) from Azure Digital Twins to downstream services or connected compute resources is a two-step process: create endpoints, then create event routes that send data to those endpoints. This article covers the first step, setting up endpoints that can receive the events. Later, you can create [event routes](how-to-create-routes.md) that specify which events generated by Azure Digital Twins are delivered to which endpoints.
 
+[!INCLUDE [digital-twins-cli-issue](../../includes/digital-twins-cli-issue.md)]
+
 ## Prerequisites
 
 * An Azure account, which you can [set up for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
@@ -86,6 +88,8 @@ Now the Event Grid topic, event hub, or Service Bus topic is available as an end
 
 # [CLI](#tab/cli) 
 
+[!INCLUDE [digital-twins-cli-issue](../../includes/digital-twins-cli-issue.md)]
+
 The following examples show how to create endpoints using the [az dt endpoint create](/cli/azure/dt/endpoint/create) command for the [Azure Digital Twins CLI](/cli/azure/dt). Replace the placeholders in the commands with the details of your own resources.
 
 To create an Event Grid endpoint:

articles/digital-twins/how-to-create-routes.md

@@ -37,6 +37,8 @@ Next, follow the instructions below if you intend to use the Azure CLI while fol
 
 [!INCLUDE [azure-cli-prepare-your-environment-h3.md](~/reusable-content/azure-cli/azure-cli-prepare-your-environment-h3.md)]
 
+[!INCLUDE [digital-twins-cli-issue](../../includes/digital-twins-cli-issue.md)]
+
 ## Create an event route
 
 After [creating an endpoint](how-to-create-endpoints.md), you'll need to define an *event route* to actually send data to the endpoint. These routes let developers wire up event flow, throughout the system and to downstream services. A single route can allow multiple notifications and event types to be selected. Read more about event routes in [Endpoints and event routes](concepts-route-events.md).
@@ -80,6 +82,8 @@ When finished, select the **Save** button to create your event route.
 
 # [CLI](#tab/cli2)
 
+[!INCLUDE [digital-twins-cli-issue](../../includes/digital-twins-cli-issue.md)]
+
 Routes can be managed using the [az dt route](/cli/azure/dt/route) commands for the Azure Digital Twins CLI. 
 
 For more information about using the CLI and what commands are available, see [Azure Digital Twins CLI command set](concepts-cli.md).

articles/digital-twins/how-to-enable-private-link.md

@@ -168,6 +168,8 @@ Once a private endpoint has been created for your Azure Digital Twins instance,
 
 For more information and examples, see the [az dt network private-endpoint reference documentation](/cli/azure/dt/network/private-endpoint).
 
+[!INCLUDE [digital-twins-cli-issue](../../includes/digital-twins-cli-issue.md)]
+
 ### Get more Private Link information
 
 You can get more information about the Private Link status of your instance with the [az dt network private-link](/cli/azure/dt/network/private-link) commands. Operations include:
@@ -200,6 +202,8 @@ To disable or enable public network access in the [Azure portal](https://portal.
 
 # [CLI](#tab/cli-2)
 
+[!INCLUDE [digital-twins-cli-issue.md](../../includes/digital-twins-cli-issue.md)]
+
 In the Azure CLI, you can disable or enable public network access by adding a `--public-network-access` parameter to the `az dt create` command. While this command can also be used to create a new instance, you can use it to edit the properties of an existing instance by providing it the name of an instance that already exists. (For more information about this command, see its [reference documentation](/cli/azure/dt#az-dt-create) or the [general instructions for setting up an Azure Digital Twins instance](how-to-set-up-instance-cli.md#create-the-azure-digital-twins-instance)).
 
 To disable public network access for an Azure Digital Twins instance, use the `--public-network-access` parameter like this:

articles/digital-twins/how-to-ingest-iot-hub-data.md

@@ -57,6 +57,8 @@ You then need to create one twin using this model. Use the following command to
 az dt twin create  --dt-name <instance-hostname-or-name> --dtmi "dtmi:contosocom:DigitalTwins:Thermostat;1" --twin-id thermostat67 --properties '{"Temperature": 0.0}'
 ```
 
+[!INCLUDE [digital-twins-cli-issue](../../includes/digital-twins-cli-issue.md)]
+
 When the twin is created successfully, the CLI output from the command should look something like this:
 ```json
 {

articles/digital-twins/how-to-set-up-instance-cli.md

@@ -44,6 +44,8 @@ Use these values in the following [az dt command](/cli/azure/dt) to create the i
 az dt create --dt-name <name-for-your-Azure-Digital-Twins-instance> --resource-group <your-resource-group> --location <region>
 ```
 
+[!INCLUDE [digital-twins-cli-issue](../../includes/digital-twins-cli-issue.md)]
+
 There are several optional parameters that can be added to the command to specify additional things about your resource during creation, including creating a managed identity for the instance or enabling/disabling public network access. For a full list of supported parameters, see the [az dt create](/cli/azure/dt#az-dt-create) reference documentation.
 
 ### Create the instance with a managed identity

articles/digital-twins/troubleshoot-error-403-digital-twins.md

@@ -54,6 +54,8 @@ If you're an Owner on the subscription, you can run this command yourself. If yo
 az dt role-assignment create --dt-name <your-Azure-Digital-Twins-instance> --assignee "<your-Azure-AD-email>" --role "Azure Digital Twins Data Owner"
 ```
 
+[!INCLUDE [digital-twins-cli-issue](../../includes/digital-twins-cli-issue.md)]
+
 For more information about this role requirement and the assignment process, see [Set up your user's access permissions](how-to-set-up-instance-CLI.md#set-up-user-access-permissions).
 
 If you have this role assignment already and you're using a Microsoft Entra app registration to authenticate a client app, you can continue to the next solution if this solution didn't resolve the 403 issue.