Skip to content

Commit 81d8eb5

Browse files
committed
few more updates
1 parent 384fe21 commit 81d8eb5

File tree

3 files changed

+3
-3
lines changed

3 files changed

+3
-3
lines changed

articles/event-grid/custom-event-to-hybrid-connection.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -80,7 +80,7 @@ You need an application that can retrieve events from the hybrid connection. The
8080
1. Compile and run the application from Visual Studio.
8181

8282
> [!IMPORTANT]
83-
> We use connection string to authenticate to Azure Relay namespace to keep the tutorial simple. We recommend that you use Microsoft Entra ID authentication in production environments. When using an application, you can enable managed identity for the application and assign an appropriate role (Azure Relay Owner, Azure Relay Listener, or Azure Relay Sender) on the Relay namespace. For more information, see [Authenticate a managed identity with Microsoft Entra ID to access Azure Relay resources](../azure-relay/authenticate-managed-identity.md).
83+
> We use connection string to authenticate to Azure Relay namespace to keep the tutorial simple. We recommend that you use Microsoft Entra ID authentication in production environments. When using an application, you can enable managed identity for the application and assign the identity an appropriate role (Azure Relay Owner, Azure Relay Listener, or Azure Relay Sender) on the Relay namespace. For more information, see [Authenticate a managed identity with Microsoft Entra ID to access Azure Relay resources](../azure-relay/authenticate-managed-identity.md).
8484
8585
## Send an event to your topic
8686

articles/event-grid/event-hubs-integration.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -241,7 +241,7 @@ You've finished setting up your event hub, dedicate SQL pool (formerly SQL Data
241241

242242

243243
> [!IMPORTANT]
244-
> We use connection string to authenticate to Azure Event Hubs namespace to keep the tutorial simple. We recommend that you use Microsoft Entra ID authentication in production environments. When using an application, you can enable managed identity for the application and assign an appropriate role (Azure Event Hubs Owner, Azure Event Hubs Data Sender, or Azure Event Hubs Data Receiver) on the Event Hubs namespace. For more information, see [Authorize access to Event Hubs using Microsoft Entra ID](../event-hubs/authorize-access-azure-active-directory.md).
244+
> We use connection string to authenticate to Azure Event Hubs namespace to keep the tutorial simple. We recommend that you use Microsoft Entra ID authentication in production environments. When using an application, you can enable managed identity for the application and assign the identity an appropriate role (Azure Event Hubs Owner, Azure Event Hubs Data Sender, or Azure Event Hubs Data Receiver) on the Event Hubs namespace. For more information, see [Authorize access to Event Hubs using Microsoft Entra ID](../event-hubs/authorize-access-azure-active-directory.md).
245245

246246

247247
## Monitor the solution

articles/event-grid/event-schema-data-manager-for-agriculture.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -102,7 +102,7 @@ The following example show schema for **Microsoft.AgFoodPlatform.PartyChanged**:
102102
"id": "<YOUR-PARTY-ID>",
103103
"createdDateTime": "2022-10-17T18:43:30Z"
104104
},
105-
"id": "000000000-0000-0000-881b-1f2d3ba9600b",
105+
"id": "000000000-0000-0000-0000-0000000000000",
106106
"source": "/subscriptions/{SUBSCRIPTION-ID}/resourceGroups/{RESOURCE-GROUP-NAME}/providers/Microsoft.AgFoodPlatform/farmBeats/{YOUR-RESOURCE-NAME}",
107107
"subject": "/parties/<YOUR-PARTY-ID>",
108108
"type": "Microsoft.AgFoodPlatform.PartyChanged",

0 commit comments

Comments
 (0)