Skip to content

Commit 5aea22d

Browse files
committed
Add feedback
1 parent 91c14fd commit 5aea22d

File tree

3 files changed

+11
-11
lines changed

3 files changed

+11
-11
lines changed

articles/iot-operations/connect-to-cloud/howto-configure-adlsv2-endpoint.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -74,15 +74,15 @@ az iot ops dataflow endpoint create adls --resource-group <ResourceGroupName> --
7474

7575
The storage account name is the name of the Azure Data Lake Storage Gen2 account in the format `<account>.blob.core.windows.net`.
7676

77-
Here's an example command to create or replace a Azure Data Lake Storage Gen2 data flow endpoint named adls-endpoint:
77+
Here's an example command to create or replace an Azure Data Lake Storage Gen2 data flow endpoint named adls-endpoint:
7878

7979
```azurecli
8080
az iot ops dataflow endpoint create adls --resource-group myResourceGroup --instance myAioInstance --name adls-endpoint --storage-account adlsstorage
8181
```
8282

8383
#### Create or change
8484

85-
Use the [az iot ops dataflow endpoint apply](/cli/azure/iot/ops/dataflow/endpoint#az-iot-ops-dataflow-endpoint-apply) command to command to create or change an Azure Data Lake Storage Gen2 data flow endpoint.
85+
Use the [az iot ops dataflow endpoint apply](/cli/azure/iot/ops/dataflow/endpoint#az-iot-ops-dataflow-endpoint-apply) command to create or change an Azure Data Lake Storage Gen2 data flow endpoint.
8686

8787
```azurecli
8888
az iot ops dataflow endpoint apply --resource-group <ResourceGroupName> --instance <AioInstanceName> --name <EndpointName> --config-file <ConfigFilePathAndName>
@@ -304,7 +304,7 @@ az iot ops dataflow endpoint create adls --auth-type SystemAssignedManagedIdenti
304304

305305
The storage account name is the name of the Azure Data Lake Storage Gen2 account in the format `<account>.blob.core.windows.net`.
306306

307-
An example command to create or replace a Azure Data Lake Storage Gen2 data flow endpoint named `my-endpoint` is:
307+
An example command to create or replace an Azure Data Lake Storage Gen2 data flow endpoint named `my-endpoint` is:
308308

309309
```azurecli
310310
az iot ops dataflow endpoint create adls --auth-type SystemAssignedManagedIdentity --resource-group myResourceGroup --instance myAioInstance --name adls-endpoint --storage-account adlsstorage
@@ -385,7 +385,7 @@ az iot ops dataflow endpoint create adls --auth-type SystemAssignedManagedIdenti
385385

386386
The storage account name is the name of the Azure Data Lake Storage Gen2 account in the format `<account>.blob.core.windows.net`.
387387

388-
An example command to create or replace a Azure Data Lake Storage Gen2 data flow endpoint named `my-endpoint` is:
388+
An example command to create or replace an Azure Data Lake Storage Gen2 data flow endpoint named `my-endpoint` is:
389389

390390
```azurecli
391391
az iot ops dataflow endpoint create adls --auth-type SystemAssignedManagedIdentity --audience https://<account>.blob.core.windows.net --resource-group myResourceGroup --instance myAioInstance --name adls-endpoint --storage-account adlsstorage
@@ -483,7 +483,7 @@ az iot ops dataflow endpoint create adls --auth-type UserAssignedManagedIdentity
483483

484484
The storage account name is the name of the Azure Data Lake Storage Gen2 account in the format `<account>.blob.core.windows.net`. The `--auth-type` parameter specifies the authentication method, which is `UserAssignedManagedIdentity` in this case. The `--client-id`, `--tenant-id`, and `--scope` parameters specify the user-assigned managed identity client ID, tenant ID, and scope respectively.
485485

486-
An example command to create or replace a Azure Data Lake Storage Gen2 data flow endpoint named `my-endpoint` is:
486+
An example command to create or replace an Azure Data Lake Storage Gen2 data flow endpoint named `my-endpoint` is:
487487

488488
```azurecli
489489
az iot ops dataflow endpoint create adls --auth-type UserAssignedManagedIdentity --client-id ClientId --tenant-id TenantId --scope https://storage.azure.com/.default --resource-group myResourceGroup --instance myAioInstance --name adls-endpoint --storage-account adlsstorage
@@ -609,7 +609,7 @@ az iot ops dataflow endpoint create adls --auth-type AccessToken --secret-name <
609609

610610
The storage account name is the name of the Azure Data Lake Storage Gen2 account in the format `<account>.blob.core.windows.net`. The `--auth-type` parameter specifies the authentication method, which is `AccessToken` in this case. The `--secret-name` parameter specifies the name of the Kubernetes secret containing the SAS token.
611611

612-
An example command to create or replace a Azure Data Lake Storage Gen2 data flow endpoint named `my-endpoint` is:
612+
An example command to create or replace an Azure Data Lake Storage Gen2 data flow endpoint named `my-endpoint` is:
613613

614614
```azurecli
615615
az iot ops dataflow endpoint create adls --auth-type AccessToken --secret-name mySasSecret --resource-group myResourceGroup --instance myAioInstance --name adls-endpoint --storage-account adlsstorage

articles/iot-operations/connect-to-cloud/howto-configure-fabric-endpoint.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ If using system-assigned managed identity, in Azure portal, go to your Azure IoT
3838

3939
Go to Microsoft Fabric workspace you created, select **Manage access** > **+ Add people or groups**.
4040

41-
1. Search for the name of your [user-assigned managed identity set up for cloud connections](../deploy-iot-ops/howto-enable-secure-settings.md#set-up-a-user-assigned-managed-identity-for-cloud-connections) or the system-assigned managed identity. For example, *azure-iot-operations-xxxx7* .
41+
1. Search for the name of your [user-assigned managed identity set up for cloud connections](../deploy-iot-ops/howto-enable-secure-settings.md#set-up-a-user-assigned-managed-identity-for-cloud-connections) or the system-assigned managed identity. For example, *azure-iot-operations-xxxx7*.
4242
1. Select **Contributor** as the role, then select **Add**. This gives the managed identity the necessary permissions to write to the Fabric lakehouse. To learn more, see [Roles in workspaces in Microsoft Fabric](/fabric/get-started/roles-workspaces).
4343

4444
## Create data flow endpoint for Microsoft Fabric OneLake
@@ -260,7 +260,7 @@ Before you configure the data flow endpoint, assign a role to the Azure IoT Oper
260260
1. In Azure portal, go to your Azure IoT Operations instance and select **Overview**.
261261
1. Copy the name of the extension listed after **Azure IoT Operations Arc extension**. For example, *azure-iot-operations-xxxx7*.
262262
1. Go to Microsoft Fabric workspace, select **Manage access** > **+ Add people or groups**.
263-
1. Search for the name of your system-assigned managed identity. For example, *azure-iot-operations-xxxx7* .
263+
1. Search for the name of your system-assigned managed identity. For example, *azure-iot-operations-xxxx7*.
264264
1. Select an appropriate role, then select **Add**.
265265
266266
Then, configure the data flow endpoint with system-assigned managed identity settings.
@@ -445,7 +445,7 @@ fabricOneLakeSettings:
445445

446446
To use user-assigned managed identity for authentication, you must first deploy Azure IoT Operations with secure settings enabled. Then you need to [set up a user-assigned managed identity for cloud connections](../deploy-iot-ops/howto-enable-secure-settings.md#set-up-a-user-assigned-managed-identity-for-cloud-connections). To learn more, see [Enable secure settings in Azure IoT Operations deployment](../deploy-iot-ops/howto-enable-secure-settings.md).
447447

448-
Before you configure the data flow endpoint, assign a role to the user-assigned managed identity that grants permission to write to the Fabric lakehouse.:
448+
Before you configure the data flow endpoint, assign a role to the user-assigned managed identity that grants permission to write to the Fabric lakehouse.
449449

450450
1. Go to Microsoft Fabric workspace, select **Manage access** > **+ Add people or groups**.
451451
1. Search for the name of your user-assigned managed identity.

articles/iot-operations/connect-to-cloud/howto-configure-kafka-endpoint.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ Next, [create an event hub in the namespace](../../event-hubs/event-hubs-create.
3636

3737
To configure a data flow endpoint for Azure Event Hubs, we recommend using either a user-assigned or system-assigned managed identity. This approach is secure and eliminates the need for managing credentials manually.
3838

39-
After the Azure Event Hubs namespace and event hub is created, you need to assign a role to the Azure IoT Operations managed identity that grants permission to send or receive messages to the event hub.
39+
After the Azure Event Hubs namespace and event hub are created, you need to assign a role to the Azure IoT Operations managed identity that grants permission to send or receive messages to the event hub.
4040

4141
If using system-assigned managed identity, in Azure portal, go to your Azure IoT Operations instance and select **Overview**. Copy the name of the extension listed after **Azure IoT Operations Arc extension**. For example, *azure-iot-operations-xxxx7*. Your system-assigned managed identity can be found using the same name of the Azure IoT Operations Arc extension.
4242

@@ -49,7 +49,7 @@ Then, go to the Event Hubs namespace > **Access control (IAM)** > **Add role ass
4949

5050
### Create data flow endpoint for Azure Event Hubs
5151

52-
Once the Azure Event Hubs namespace and event hub is configured, you can create a data flow endpoint for the Kafka-enabled Azure Event Hubs namespace.
52+
Once the Azure Event Hubs namespace and event hub are configured, you can create a data flow endpoint for the Kafka-enabled Azure Event Hubs namespace.
5353

5454
# [Operations experience](#tab/portal)
5555

0 commit comments

Comments
 (0)