Skip to content

Commit 1e95ea5

Browse files
PRMerger18PRMerger18
authored
Merge pull request #129911 from baanders/9-15-shell
ADT- Remove Cloud Shell "Try it"
2 parents f1e8729 + 4f300c6 commit 1e95ea5

9 files changed

+32
-32
lines changed

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -65,15 +65,15 @@ The model looks like this:
6565

6666
To **upload this model to your twins instance**, open the Azure CLI and run the following command:
6767

68-
```azurecli-interactive
68+
```azurecli
6969
az dt model create --models '{ "@id": "dtmi:contosocom:DigitalTwins:Thermostat;1", "@type": "Interface", "@context": "dtmi:dtdl:context;2", "contents": [ { "@type": "Property", "name": "Temperature", "schema": "double" } ]}' -n {digital_twins_instance_name}
7070
```
7171

7272
[!INCLUDE [digital-twins-known-issue-cloud-shell](../../includes/digital-twins-known-issue-cloud-shell.md)]
7373

7474
You'll then need to **create one twin using this model**. Use the following command to create a twin and set 0.0 as an initial temperature value.
7575

76-
```azurecli-interactive
76+
```azurecli
7777
az dt twin create --dtmi "dtmi:contosocom:DigitalTwins:Thermostat;1" --twin-id thermostat67 --properties '{"Temperature": 0.0,}' --dt-name {digital_twins_instance_name}
7878
```
7979

@@ -222,7 +222,7 @@ While running the device simulator above, the temperature value of your digital
222222

223223
[!INCLUDE [digital-twins-known-issue-cloud-shell](../../includes/digital-twins-known-issue-cloud-shell.md)]
224224

225-
```azurecli-interactive
225+
```azurecli
226226
az dt twin query -q "select * from digitaltwins" -n {digital_twins_instance_name}
227227
```
228228

‎articles/digital-twins/how-to-integrate-azure-signalr.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -148,7 +148,7 @@ Next, publish your function to Azure, using the steps described in the [*Publish
148148

149149
1. Finally, add your Azure SignalR **connection string** from earlier to the function's app settings, using the following Azure CLI command. The command can be run in [Azure Cloud Shell](https://shell.azure.com), or locally if you have the Azure CLI [installed on your machine](https://docs.microsoft.com/cli/azure/install-azure-cli?view=azure-cli-latest):
150150
151-
```azurecli-interactive
151+
```azurecli
152152
az functionapp config appsettings set -g <your-resource-group> -n <your-App-Service-(function-app)-name> --settings "AzureSignalRConnectionString=<your-Azure-SignalR-ConnectionString>"
153153
```
154154

@@ -243,7 +243,7 @@ Using the Azure Cloud Shell or local Azure CLI, you can delete all Azure resourc
243243
> [!IMPORTANT]
244244
> Deleting a resource group is irreversible. The resource group and all the resources contained in it are permanently deleted. Make sure that you do not accidentally delete the wrong resource group or resources.
245245

246-
```azurecli-interactive
246+
```azurecli
247247
az group delete --name <your-resource-group>
248248
```
249249

‎articles/digital-twins/how-to-integrate-maps.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -135,7 +135,7 @@ namespace SampleFunctionsApp
135135

136136
You'll need to set two environment variables in your function app. One is your [Azure Maps primary subscription key](../azure-maps/quick-demo-map-app.md#get-the-primary-key-for-your-account), and one is your [Azure Maps stateset ID](../azure-maps/tutorial-creator-indoor-maps.md#create-a-feature-stateset).
137137

138-
```azurecli-interactive
138+
```azurecli
139139
az functionapp config appsettings set --settings "subscription-key=<your-Azure-Maps-primary-subscription-key> -g <your-resource-group> -n <your-App-Service-(function-app)-name>"
140140
az functionapp config appsettings set --settings "statesetID=<your-Azure-Maps-stateset-ID> -g <your-resource-group> -n <your-App-Service-(function-app)-name>
141141
```

‎articles/digital-twins/how-to-integrate-time-series-insights.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -47,21 +47,21 @@ The Azure Digital Twins [*Tutorial: Connect an end-to-end solution*](./tutorial-
4747

4848
1. First, create an event hub namespace, which will receive events from your Azure Digital Twins instance. You can either use the Azure CLI instructions below, or use the Azure portal: [*Quickstart: Create an event hub using Azure portal*](../event-hubs/event-hubs-create.md).
4949

50-
```azurecli-interactive
50+
```azurecli
5151
# Create an Event Hubs namespace. Specify a name for the Event Hubs namespace.
5252
az eventhubs namespace create --name <name for your Event Hubs namespace> --resource-group <resource group name> -l <region, for example: East US>
5353
```
5454
5555
2. Create an event hub within the namespace.
5656
57-
```azurecli-interactive
57+
```azurecli
5858
# Create an event hub to receive twin change events. Specify a name for the event hub.
5959
az eventhubs eventhub create --name <name for your Twins event hub> --resource-group <resource group name> --namespace-name <Event Hubs namespace from above>
6060
```
6161
6262
3. Create an [authorization rule](https://docs.microsoft.com/cli/azure/eventhubs/eventhub/authorization-rule?view=azure-cli-latest#az-eventhubs-eventhub-authorization-rule-create) with send and receive permissions.
6363
64-
```azurecli-interactive
64+
```azurecli
6565
# Create an authorization rule. Specify a name for the rule.
6666
az eventhubs eventhub authorization-rule create --rights Listen Send --resource-group <resource group name> --namespace-name <Event Hubs namespace from above> --eventhub-name <Twins event hub name from above> --name <name for your Twins auth rule>
6767
```
@@ -154,12 +154,12 @@ To create the second event hub, you can either use the Azure CLI instructions be
154154
1. Prepare your *Event Hubs namespace* and *resource group* name from earlier in this article
155155

156156
2. Create a new event hub
157-
```azurecli-interactive
157+
```azurecli
158158
# Create an event hub. Specify a name for the event hub.
159159
az eventhubs eventhub create --name <name for your TSI event hub> --resource-group <resource group name from earlier> --namespace-name <Event Hubs namespace from earlier>
160160
```
161161
3. Create an [authorization rule](https://docs.microsoft.com/cli/azure/eventhubs/eventhub/authorization-rule?view=azure-cli-latest#az-eventhubs-eventhub-authorization-rule-create) with send and receive permissions
162-
```azurecli-interactive
162+
```azurecli
163163
# Create an authorization rule. Specify a name for the rule.
164164
az eventhubs eventhub authorization-rule create --rights Listen Send --resource-group <resource group name> --namespace-name <Event Hubs namespace from earlier> --eventhub-name <TSI event hub name from above> --name <name for your TSI auth rule>
165165
```
@@ -172,27 +172,27 @@ Next, you'll need to set environment variables in your function app from earlier
172172
173173
1. Get the Twins [event hub connection string](../event-hubs/event-hubs-get-connection-string.md), using the authorization rules you created above for the Twins hub.
174174
175-
```azurecli-interactive
175+
```azurecli
176176
az eventhubs eventhub authorization-rule keys list --resource-group <resource group name> --namespace-name <Event Hubs namespace> --eventhub-name <Twins event hub name from earlier> --name <Twins auth rule from earlier>
177177
```
178178
179179
2. Use the connection string you get as a result to create an app setting in your function app that contains your connection string:
180180
181-
```azurecli-interactive
181+
```azurecli
182182
az functionapp config appsettings set --settings "EventHubAppSetting-Twins=<Twins event hub connection string> -g <resource group> -n <your App Service (function app) name>"
183183
```
184184
185185
### Set the Time Series Insights event hub connection string
186186
187187
1. Get the TSI [event hub connection string](../event-hubs/event-hubs-get-connection-string.md), using the authorization rules you created above for the Time Series Insights hub:
188188
189-
```azurecli-interactive
189+
```azurecli
190190
az eventhubs eventhub authorization-rule keys list --resource-group <resource group name> --namespace-name <Event Hubs namespace> --eventhub-name <TSI event hub name> --name <TSI auth rule>
191191
```
192192
193193
2. In your function app, create an app setting containing your connection string:
194194
195-
```azurecli-interactive
195+
```azurecli
196196
az functionapp config appsettings set --settings "EventHubAppSetting-TSI=<TSI event hub connection string> -g <resource group> -n <your App Service (function app) name>"
197197
```
198198

‎articles/digital-twins/how-to-provision-using-device-provisioning-service.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -72,7 +72,7 @@ Create a Device Provisioning Service instance, which will be used to provision I
7272

7373
The following Azure CLI command will create a Device Provisioning Service. You will need to specify a name, resource group, and region. The command can be run in [Cloud Shell](https://shell.azure.com), or locally if you have the Azure CLI [installed on your machine](https://docs.microsoft.com/cli/azure/install-azure-cli?view=azure-cli-latest).
7474

75-
```azurecli-interactive
75+
```azurecli
7676
az iot dps create --name <Device Provisioning Service name> --resource-group <resource group name> --location <region; for example, eastus>
7777
```
7878

@@ -238,7 +238,7 @@ Next, you'll need to set environment variables in your function app from earlier
238238

239239
Add the setting with this Azure CLI command:
240240

241-
```azurecli-interactive
241+
```azurecli
242242
az functionapp config appsettings set --settings "ADT_SERVICE_URL=https://<Azure Digital Twins instance _host name_>" -g <resource group> -n <your App Service (function app) name>
243243
```
244244

@@ -247,7 +247,7 @@ Ensure that the permissions and Managed Identity role assignment are configured
247247
<!--
248248
* Azure AD app registration **_Application (client) ID_** ([find in portal](../articles/digital-twins/how-to-set-up-instance-portal.md#collect-important-values))
249249
250-
```azurecli-interactive
250+
```azurecli
251251
az functionapp config appsettings set --settings "AdtAppId=<Application (client)" ID> -g <resource group> -n <your App Service (function app) name>
252252
``` -->
253253

@@ -294,7 +294,7 @@ You should see the device being registered and connected to IoT Hub, and then st
294294

295295
As a result of the flow you've set up in this article, the device will be automatically registered in Azure Digital Twins. Using the following [Azure Digital Twins CLI](how-to-use-cli.md) command to find the twin of the device in the Azure Digital Twins instance you created.
296296

297-
```azurecli-interactive
297+
```azurecli
298298
az dt twin show -n <Digital Twins instance name> --twin-id <Device Registration ID>"
299299
```
300300

@@ -450,13 +450,13 @@ Next, you'll need to set environment variables in your function app from earlier
450450

451451
Add the setting with this Azure CLI command. The command can be run in [Cloud Shell](https://shell.azure.com), or locally if you have the Azure CLI [installed on your machine](https://docs.microsoft.com/cli/azure/install-azure-cli?view=azure-cli-latest).
452452

453-
```azurecli-interactive
453+
```azurecli
454454
az functionapp config appsettings set --settings "ADT_SERVICE_URL=https://<Azure Digital Twins instance _host name_>" -g <resource group> -n <your App Service (function app) name>
455455
```
456456

457457
Next, you will need to configure the function environment variable for connecting to the newly created event hub.
458458

459-
```azurecli-interactive
459+
```azurecli
460460
az functionapp config appsettings set --settings "EVENTHUB_CONNECTIONSTRING=<Event Hubs SAS connection string Listen>" -g <resource group> -n <your App Service (function app) name>
461461
```
462462

@@ -487,7 +487,7 @@ The device will be automatically removed from Azure Digital Twins.
487487

488488
Use the following [Azure Digital Twins CLI](how-to-use-cli.md) command to verify the twin of the device in the Azure Digital Twins instance was deleted.
489489

490-
```azurecli-interactive
490+
```azurecli
491491
az dt twin show -n <Digital Twins instance name> --twin-id <Device Registration ID>"
492492
```
493493

@@ -503,7 +503,7 @@ Using the Azure Cloud Shell or local Azure CLI, you can delete all Azure resourc
503503
> [!IMPORTANT]
504504
> Deleting a resource group is irreversible. The resource group and all the resources contained in it are permanently deleted. Make sure that you do not accidentally delete the wrong resource group or resources.
505505
506-
```azurecli-interactive
506+
```azurecli
507507
az group delete --name <your-resource-group>
508508
```
509509
<!--

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@ In the downloaded sample folder, the deployment script is located at _Azure_Digi
3939

4040
Here are the steps to run the deployment script in Cloud Shell.
4141
1. Go to an [Azure Cloud Shell](https://shell.azure.com/) window in your browser. Sign in using this command:
42-
```azurecli-interactive
42+
```azurecli
4343
az login
4444
```
4545
If the CLI can open your default browser, it will do so and load an Azure sign-in page. Otherwise, open a browser page at *https://aka.ms/devicelogin* and enter the authorization code displayed in your terminal.

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -48,7 +48,7 @@ If you do not have this role assignment, someone with an Owner role in your **Az
4848

4949
If you are an Owner on the subscription, you can run this command yourself. If you are not, contact an Owner to run this command on your behalf.
5050

51-
```azurecli-interactive
51+
```azurecli
5252
az dt role-assignment create --dt-name <your-Azure-Digital-Twins-instance> --assignee "<your-Azure-AD-email>" --role "Azure Digital Twins Owner (Preview)"
5353
```
5454

‎articles/digital-twins/tutorial-code.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -114,7 +114,7 @@ In order to authenticate, you need three pieces of information:
114114
>[!TIP]
115115
> If you don't know your *Directory (tenant) ID*, you can get it by running this command in [Azure Cloud Shell](https://shell.azure.com):
116116
>
117-
> ```azurecli-interactive
117+
> ```azurecli
118118
> az account show --query tenantId
119119
> ```
120120

‎articles/digital-twins/tutorial-end-to-end.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -164,13 +164,13 @@ To enable the function app to access Azure Digital Twins, the next step is to co
164164

165165
In Azure Cloud Shell, use the following command to set an application setting which your function app will use to reference your Azure Digital Twins instance.
166166

167-
```azurecli-interactive
167+
```azurecli
168168
az functionapp config appsettings set -g <your-resource-group> -n <your-App-Service-(function-app)-name> --settings "ADT_SERVICE_URL=<your-Azure-Digital-Twins-instance-URL>"
169169
```
170170

171171
Use the following command to create the system-managed identity. Take note of the *principalId* field in the output.
172172

173-
```azurecli-interactive
173+
```azurecli
174174
az functionapp identity assign -g <your-resource-group> -n <your-App-Service-(function-app)-name>
175175
```
176176

@@ -205,7 +205,7 @@ Azure Digital Twins is designed to work alongside [IoT Hub](../iot-hub/about-iot
205205

206206
In Azure Cloud Shell, use this command to create a new IoT hub:
207207

208-
```azurecli-interactive
208+
```azurecli
209209
az iot hub create --name <name-for-your-IoT-hub> -g <your-resource-group> --sku S1
210210
```
211211

@@ -245,7 +245,7 @@ This section creates a device representation in IoT Hub with the ID *thermostat6
245245

246246
In Azure Cloud Shell, create a device in IoT Hub with the following command:
247247

248-
```azurecli-interactive
248+
```azurecli
249249
az iot hub device-identity create --device-id thermostat67 --hub-name <your-IoT-hub-name> -g <your-resource-group>
250250
```
251251

@@ -333,7 +333,7 @@ In this section, you create an event grid topic, and then create an endpoint wit
333333

334334
In Azure Cloud Shell, run the following command to create an event grid topic:
335335

336-
```azurecli-interactive
336+
```azurecli
337337
az eventgrid topic create -g <your-resource-group> --name <name-for-your-event-grid-topic> -l <region>
338338
```
339339

@@ -444,7 +444,7 @@ Using the [Azure Cloud Shell](https://shell.azure.com), you can delete all Azure
444444
> [!IMPORTANT]
445445
> Deleting a resource group is irreversible. The resource group and all the resources contained in it are permanently deleted. Make sure that you do not accidentally delete the wrong resource group or resources.
446446
447-
```azurecli-interactive
447+
```azurecli
448448
az group delete --name <your-resource-group>
449449
```
450450

0 commit comments

Comments
 (0)