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/digital-twins/tutorial-facilities-analyze.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -78,7 +78,7 @@ You can use the [Event Hubs](../event-hubs/event-hubs-about.md) service to creat
78
78
> [!TIP]
79
79
> Verify that you are creating an SAS Policy for your event hub instance rather than your namespace.
80
80
81
-
1. Open the **ManageSend** policy that you created, and copy the values for **Connection string--primary key** and **Connection string--secondary key** to a temporary file. You'll need these values to create an endpoint for the event hub in the next section.
81
+
1. Open the **ManageSend** policy that you created, and copy the values for **Connection string—primary key** and **Connection string—secondary key** to a temporary file. You'll need these values to create an endpoint for the event hub in the next section.
82
82
83
83
### Create an endpoint for the event hub
84
84
@@ -104,13 +104,13 @@ You can use the [Event Hubs](../event-hubs/event-hubs-about.md) service to creat
104
104
path: Name_of_your_Event_Hub
105
105
```
106
106
107
-
1. Replace the placeholders `Primary_connection_string_for_your_event_hub` with the value of **Connection string--primary key** for the event hub. Make sure the format of this connection string is as follows:
107
+
1. Replace the placeholders `Primary_connection_string_for_your_event_hub` with the value of **Connection string—primary key** for the event hub. Make sure the format of this connection string is as follows:
1. Replace the placeholders `Secondary_connection_string_for_your_event_hub` with the value of **Connection string--secondary key** for the event hub. Make sure the format of this connection string is as follows:
113
+
1. Replace the placeholders `Secondary_connection_string_for_your_event_hub` with the value of **Connection string—secondary key** for the event hub. Make sure the format of this connection string is as follows:
@@ -141,7 +141,7 @@ You can use the [Event Hubs](../event-hubs/event-hubs-about.md) service to creat
141
141
142
142
[](./media/tutorial-facilities-analyze/create-tsi.png#lightbox)
143
143
144
-
1. In the **Event Source** tab, enter a **Name**, select **Event Hub** as the **Source type**, and make sure the other values are selected correctly. Select **ManageSend** for **Event Hub access policy name**, and then select the consumer group that you created in the previous section for **Event Hub consumer group**. Select **Review + create**.
144
+
1. In the **Event Source** tab, enter a **Name**, select **Event Hub** as the **Source type**, and make sure the other values are selected correctly to reference the event hub you created. Select **ManageSend** for **Event Hub access policy name**, and then select the consumer group that you created in the previous section for **Event Hub consumer group**. Select **Review + create**.
145
145
146
146
[](./media/tutorial-facilities-analyze/tsi-event-source.png#lightbox)
Copy file name to clipboardExpand all lines: articles/digital-twins/tutorial-facilities-events.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -112,19 +112,19 @@ You can use the [Azure Logic Apps](../logic-apps/logic-apps-overview.md) service
112
112
113
113
[](./media/tutorial-facilities-events/create-logic-app.png#lightbox)
114
114
115
-
1. Open your Logic Apps resource when it's deployed, and then open the **Logic App Designer** pane.
115
+
1. Open your Logic Apps resource when it's deployed, and then open the **Logic app designer** pane.
116
116
117
-
1. Select the **When an Event Grid resource event occurs** trigger. Sign in to your tenant with your Azure account when prompted. Select **Allow access** for your Event Grid resource if prompted. Select **Continue**.
117
+
1. Select the **When an Event Grid resource event occurs** trigger. Expand the **Azure Event Grid** option, and sign in to your tenant with your Azure account when prompted. Select **Allow access** for your Event Grid resource if prompted. Select **Continue**.
118
118
119
-
1. In the **When a resource event occurs (Preview)** window:
119
+
1. In the **When a resource event occurs** window:
120
120
121
121
a. Select the **Subscription** that you used to create the event grid topic.
122
122
123
123
b. Select **Microsoft.EventGrid.Topics** for **Resource Type**.
124
124
125
125
c. Select your Event Grid resource from the drop-down box for **Resource Name**.
@@ -182,7 +182,7 @@ You can use the [Azure Logic Apps](../logic-apps/logic-apps-overview.md) service
182
182
183
183
[](./media/tutorial-facilities-events/logic-app-send-email.png#lightbox)
184
184
185
-
1. Select the **Save** button at the top of the **Logic App Designer** pane.
185
+
1. Select the **Save** button at the top of the **Logic app designer** pane.
186
186
187
187
1. Make sure to simulate sensor data by browsing to the **device-connectivity** folder of the Digital Twins sample in a command window, and running `dotnet run`.
0 commit comments