You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/iot-operations/connect-to-cloud/tutorial-dataflow-asset-event-grid.md
+20-3Lines changed: 20 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@ ms.date: 07/23/2024
15
15
In this tutorial, you set up a dataflow from an asset to Azure Event Grid. You configure the source to read data from an asset, the destination to send data to Azure Event Grid, and apply a transformation to the data.
16
16
17
17
1. Create the asset.
18
-
1. Create an MQTT broker endpoint.
18
+
1. Create an MQTT broker endpoint by creating a file named `mqtt-endpoint.yaml` with the following content:
@@ -45,7 +51,13 @@ In this tutorial, you set up a dataflow from an asset to Azure Event Grid. You c
45
51
mode: enabled
46
52
```
47
53
48
-
1. Create a dataflow with the asset as the source and Azure Event Grid as the destination.
54
+
1. Apply the configuration to create the Azure Event Grid endpoint.
55
+
56
+
```bash
57
+
kubectl apply -f eventgrid-endpoint.yaml
58
+
```
59
+
60
+
1. Create a dataflow with the asset as the source and Azure Event Grid as the destination by creating a file named `dataflow.yaml` with the following content:
Copy file name to clipboardExpand all lines: articles/iot-operations/connect-to-cloud/tutorial-dataflow-mqtt-event-grid.md
+25-7Lines changed: 25 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,9 +12,9 @@ ms.date: 07/23/2024
12
12
13
13
# Tutorial: Create bi-directional MQTT bridge to Azure Event Grid using dataflows
14
14
15
-
In this tutorial, you will set up a bi-directional MQTT bridge between an MQTT broker and Azure Event Grid using dataflows. To expedite the process, you will use the default settings for the MQTT broker and Azure Event Grid endpoints, and no transformation will be applied.
15
+
In this tutorial, you set up a bi-directional MQTT bridge between an MQTT broker and Azure Event Grid using dataflows. To expedite the process, default settings for the MQTT broker and Azure Event Grid endpoints are used. No transformation are applied.
16
16
17
-
1. Create an MQTT broker endpoint.
17
+
1. Create an MQTT broker endpoint for the MQTT source by creating a file named `mqtt-endpoint.yaml` with the following content:
@@ -44,7 +50,21 @@ In this tutorial, you will set up a bi-directional MQTT bridge between an MQTT b
44
50
mode: enabled
45
51
```
46
52
47
-
1. Give AIO permission to send messages to the Azure Event Grid endpoint.
53
+
1. Apply the configuration to create the Azure Event Grid endpoint.
54
+
55
+
```bash
56
+
kubectl apply -f eventgrid-endpoint.yaml
57
+
```
58
+
59
+
1. Run the following command to get the Azure IoT Operations managed identity.
60
+
61
+
```bash
62
+
az k8s-extension show
63
+
```
64
+
65
+
1. Get the `identity` from the output.
66
+
67
+
1. Grant Azure IoT Operations permission to send messages to the Azure Event Grid endpoint.
48
68
49
69
```bash
50
70
az role assignment create --role "EventGrid TopicSpaces Publisher" --assignee <AIO identity> --scope <Azure Event Grid endpoint resource ID>
@@ -54,9 +74,7 @@ In this tutorial, you will set up a bi-directional MQTT bridge between an MQTT b
54
74
az role assignment create --role "EventGrid TopicSpaces Subscriber" --assignee <AIO identity> --scope <Azure Event Grid endpoint resource ID>
55
75
```
56
76
57
-
You can find the AIO managed identity in the Azure IoT Operations portal or use `az k8s-extension show` , under `identity` .
58
-
59
-
1. Create two dataflows with the MQTT broker endpoint as the source and the Azure Event Grid endpoint as the destination, and vice versa. No need to configure transformation.
77
+
1. Create two dataflows with the MQTT broker endpoint as the source and the Azure Event Grid endpoint as the destination, and vice versa. No need to configure transformation. Create a file named `dataflow.yaml` with the following content:
0 commit comments