Skip to content

Commit 5cf93f5

Browse files
committed
Formatting
1 parent 4ff470b commit 5cf93f5

File tree

4 files changed

+9
-9
lines changed

4 files changed

+9
-9
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -227,8 +227,8 @@ Using the system-assigned managed identity is the recommended authentication met
227227
Before creating the dataflow endpoint, assign a role to the managed identity that has write permission to the storage account. For example, you can assign the *Storage Blob Data Contributor* role. To learn more about assigning roles to blobs, see [Authorize access to blobs using Microsoft Entra ID](../../storage/blobs/authorize-access-azure-active-directory.md).
228228

229229
1. In Azure portal, go to your Azure IoT Operations instance and select **Overview**.
230-
1. Copy the name of the extension listed after **Azure IoT Operations Arc extension**. For example, `azure-iot-operations-xxxx7`.
231-
1. Search for the managed identity in the Azure portal by using the name of the extension. For example, search for `azure-iot-operations-xxxx7`.
230+
1. Copy the name of the extension listed after **Azure IoT Operations Arc extension**. For example, *azure-iot-operations-xxxx7*.
231+
1. Search for the managed identity in the Azure portal by using the name of the extension. For example, search for *azure-iot-operations-xxxx7*.
232232
1. Assign a role to the Azure IoT Operations Arc extension managed identity that grants permission to write to the storage account, such as *Storage Blob Data Contributor*. To learn more, see [Authorize access to blobs using Microsoft Entra ID](../../storage/blobs/authorize-access-azure-active-directory.md).
233233
1. Create the *DataflowEndpoint* resource and specify the managed identity authentication method.
234234

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ To send data to Microsoft Fabric OneLake in Azure IoT Operations Preview, you ca
3333
To configure a dataflow endpoint for Microsoft Fabric OneLake, we suggest using the managed identity of the Azure Arc-enabled Kubernetes cluster. This approach is secure and eliminates the need for secret management.
3434

3535
1. In Azure portal, go to your Azure IoT Operations instance and select **Overview**.
36-
1. Copy the name of the extension listed after **Azure IoT Operations Arc extension**. For example, `azure-iot-operations-xxxx7`.
36+
1. Copy the name of the extension listed after **Azure IoT Operations Arc extension**. For example, *azure-iot-operations-xxxx7*.
3737
1. In the Microsoft Fabric workspace you created, select **Manage access** > **+ Add people or groups**. Search for the Azure IoT Operations Arc extension by its name and select it. Select **Contributor** as the role, then select **Add**.
3838
1. Create the *DataflowEndpoint* resource and specify the managed identity authentication method.
3939

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

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -38,8 +38,8 @@ Next, [create an event hub in the namespace](../../event-hubs/event-hubs-create.
3838
To configure a dataflow endpoint for a Kafka endpoint, we recommend using the managed identity of the Azure Arc-enabled Kubernetes cluster. This approach is secure and eliminates the need for secret management.
3939

4040
1. In Azure portal, go to your Azure IoT Operations instance and select **Overview**.
41-
1. Copy the name of the extension listed after **Azure IoT Operations Arc extension**. For example, `azure-iot-operations-xxxx7`.
42-
1. Search for the managed identity in the Azure portal by using the name of the extension. For example, search for `azure-iot-operations-xxxx7`.
41+
1. Copy the name of the extension listed after **Azure IoT Operations Arc extension**. For example, *azure-iot-operations-xxxx7*.
42+
1. Search for the managed identity in the Azure portal by using the name of the extension. For example, search for *azure-iot-operations-xxxx7*.
4343
1. Assign the Azure IoT Operations Arc extension managed identity to the Event Hubs namespace with the `Azure Event Hubs Data Sender` or `Azure Event Hubs Data Receiver` role.
4444

4545
### Create dataflow endpoint
@@ -409,8 +409,8 @@ kafkaSettings:
409409
To use system-assigned managed identity for authentication, assign a role to the Azure IoT Operation managed identity that grants permission to send and receive messages from Event Hubs.
410410

411411
1. In Azure portal, go to your Azure IoT Operations instance and select **Overview**.
412-
1. Copy the name of the extension listed after **Azure IoT Operations Arc extension**. For example, `azure-iot-operations-xxxx7`.
413-
1. Search for the managed identity in the Azure portal by using the name of the extension. For example, search for `azure-iot-operations-xxxx7`.
412+
1. Copy the name of the extension listed after **Azure IoT Operations Arc extension**. For example, *azure-iot-operations-xxxx7*.
413+
1. Search for the managed identity in the Azure portal by using the name of the extension. For example, search for *azure-iot-operations-xxxx7*.
414414
1. Assign a role to the Azure IoT Operations Arc extension managed identity that grants permission to send and receive messages such as *Azure Event Hubs Data Owner*, *Azure Event Hubs Data Sender*, or *Azure Event Hubs Data Receiver*. To learn more, see [Authenticate an application with Microsoft Entra ID to access Event Hubs resources](../../event-hubs/authenticate-application.md#built-in-roles-for-azure-event-hubs).
415415
1. Specify the managed identity authentication method in the Kafka settings. In most cases, you don't need to specify other settings.
416416

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -466,8 +466,8 @@ To use system-assigned managed identity for authentication, you don't need to cr
466466
Before you configure the endpoint, make sure that the Azure IoT Operations managed identity has the necessary permissions to connect to the MQTT broker.
467467

468468
1. In Azure portal, go to your Azure IoT Operations instance and select **Overview**.
469-
1. Copy the name of the extension listed after **Azure IoT Operations Arc extension**. For example, `azure-iot-operations-xxxx7`.
470-
1. Search for the managed identity in the Azure portal by using the name of the extension. For example, search for `azure-iot-operations-xxxx7`.
469+
1. Copy the name of the extension listed after **Azure IoT Operations Arc extension**. For example, *azure-iot-operations-xxxx7*.
470+
1. Search for the managed identity in the Azure portal by using the name of the extension. For example, search for *azure-iot-operations-xxxx7*.
471471
1. Assign a role to the Azure IoT Operations Arc extension managed identity that grants permission to connect to the MQTT broker. For example, with Azure Event Grid MQTT broker, assign the managed identity to the Event Grid namespace or topic space with [an appropriate role](../../event-grid/mqtt-client-microsoft-entra-token-and-rbac.md#authorization-to-grant-access-permissions).
472472
1. Configure the endpoint with system-assigned managed identity settings.
473473

0 commit comments

Comments
 (0)