Skip to content

Commit 1a6aa6d

Browse files
committed
Walkthrough updates
1 parent f615985 commit 1a6aa6d

File tree

1 file changed

+4
-13
lines changed

1 file changed

+4
-13
lines changed

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

Lines changed: 4 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -126,7 +126,7 @@ To publish the function app to Azure, you'll need to create a storage account, t
126126
127127
This command publishes the project to the *digital-twins-samples-main\AdtSampleApp\SampleFunctionsApp\bin\Release\netcoreapp3.1\publish* directory.
128128
129-
1. Create a zip of the published files that are located in the *digital-twins-samples-main\AdtSampleApp\SampleFunctionsApp\bin\Release\netcoreapp3.1\publish* directory. Name the zipped folder *publish.zip*.
129+
1. Using your preferred method, create a zip of the published files that are located in the *digital-twins-samples-main\AdtSampleApp\SampleFunctionsApp\bin\Release\netcoreapp3.1\publish* directory. Name the zipped folder *publish.zip*.
130130
131131
>[!TIP]
132132
>If you're using PowerShell, you can create the zip by copying the full path to that *\publish* directory and pasting it into the following command:
@@ -184,21 +184,12 @@ There are two settings that need to be set for the function app to access your A
184184

185185
The first setting gives the function app the **Azure Digital Twins Data Owner** role in the Azure Digital Twins instance. This role is required for any user or function that wants to perform many data plane activities on the instance. You can read more about security and role assignments in [Security for Azure Digital Twins solutions](concepts-security.md).
186186

187-
1. Use the following command to see the details of the system-managed identity for the function. Take note of the **principalId** field in the output.
187+
1. Use the following command to create a system-managed identity for the function. The output will display details of the identity that's been created. Take note of the **principalId** field in the output to use in the next step.
188188

189189
```azurecli-interactive
190-
az functionapp identity show --resource-group <your-resource-group> --name <your-function-app-name>
190+
az functionapp identity assign --resource-group <your-resource-group> --name <your-function-app-name>
191191
```
192192
193-
>[!NOTE]
194-
> If the result is empty instead of showing details of an identity, create a new system-managed identity for the function using this command:
195-
>
196-
>```azurecli-interactive
197-
>az functionapp identity assign --resource-group <your-resource-group> --name <your-function-app-name>
198-
>```
199-
>
200-
> The output will then display details of the identity, including the **principalId** value required for the next step.
201-
202193
1. Use the **principalId** value in the following command to assign the function app's identity to the **Azure Digital Twins Data Owner** role for your Azure Digital Twins instance.
203194
204195
```azurecli-interactive
@@ -307,7 +298,7 @@ deviceConnectionString = <your-device-connection-string>
307298

308299
Save the file.
309300

310-
Now, to see the results of the data simulation that you've set up, navigate to *digital-twins-samples-main\DeviceSimulator\DeviceSimulator* in a local console window.
301+
Now, to see the results of the data simulation that you've set up, open a new local console window and navigate to *digital-twins-samples-main\DeviceSimulator\DeviceSimulator*.
311302

312303
>[!NOTE]
313304
> You should now have two open console windows: one that's open to the the *DeviceSimulator\DeviceSimulator* folder, and one from earlier that's still open to the *AdtSampleApp\SampleClientApp* folder.

0 commit comments

Comments
 (0)