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/event-grid/subscribe-to-graph-api-events.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
@@ -70,11 +70,11 @@ Body:
70
70
71
71
Here are some of the key headers and payload properties:
72
72
73
-
-`x-ms-enable-features`: Header used to indicate your desire to participate in the private preview capability to send events to Azure Event Grid. Its value must be "EventGrid". This header must be included with the request when creating a Microsoft Graph API subscription.
73
+
-`x-ms-enable-features`: Header used to indicate your desire to participate in the preview capability to send events to Azure Event Grid. Its value must be `EventGrid`. This header must be included with the request when creating a Microsoft Graph API subscription.
74
74
-`changeType`: the kind of resource changes for which you want to receive events. Valid values: `Updated`, `Deleted`, and `Created`. You can specify one or more of these values separated by commas.
75
75
-`notificationUrl`: a URI that conforms to the following pattern: `EventGrid:?azuresubscriptionid=<you-azure-subscription-id>&resourcegroup=<your-resource-group-name>&partnertopic=<the-name-for-your-partner-topic>&location=<the-Azure-region-where-you-want-the-topic-created>`.
76
-
- resource: the resource for which you need events announcing state changes.
77
-
- expirationDateTime: the expiration time at which the subscription will expire and hence the flow of events will stop. It must conform to the format specified in [RFC 3339](https://tools.ietf.org/html/rfc3339). You must specify an expiration time that is within the [maximum subscription length allowable for the resource type](/graph/api/resources/subscription#maximum-length-of-subscription-per-resource-type) used.
76
+
- resource: the resource that generates events to announce state changes.
77
+
- expirationDateTime: the expiration time at which the subscription expires and hence the flow of events stop. It must conform to the format specified in [RFC 3339](https://tools.ietf.org/html/rfc3339). You must specify an expiration time that is within the [maximum subscription length allowable for the resource type](/graph/api/resources/subscription#maximum-length-of-subscription-per-resource-type) used.
78
78
- client state. A value that is set by you when creating a Graph API subscription. For more information, see [Graph API subscription properties](/graph/api/resources/subscription#properties).
79
79
80
80
> [!NOTE]
@@ -95,7 +95,7 @@ Here are some of the key headers and payload properties:
95
95
When you create a Graph API subscription with a `notificationUrl` bound to Event Grid, a partner topic is created in your Azure subscription. For that partner topic, you [configure event subscriptions](event-filtering.md) to send your events to any of the supported [event handlers](event-handlers.md) that best meets your requirements to process the events.
96
96
97
97
#### Microsoft Graph API Explorer
98
-
For quick tests and to get to know the API, you could use the [Microsoft Graph API explorer](/graph/graph-explorer/graph-explorer-features). For anything else beyond casuals tests or learning, you should use the Graph SDKs as described above.
98
+
For quick tests and to get to know the API, you could use the [Microsoft Graph API explorer](/graph/graph-explorer/graph-explorer-features). For anything else beyond casuals tests or learning, you should use the Graph SDKs.
0 commit comments