Merge pull request #228510 from jfggdl/patch-3

Update subscribe-to-graph-api-events.md

Author: prmerger-automator[bot]

articles/event-grid/subscribe-to-graph-api-events.md

@@ -9,7 +9,7 @@ ms.date: 09/01/2022
 This article describes steps to subscribe to events published by Microsoft Graph API. The following table lists the resources for which events are available through Graph API. For every resource, events for create, update and delete state changes are supported. 
 
 > [!IMPORTANT]
-> Microsoft Graph API's ability to send events to Azure Event Grid is currently in **private preview**. 
+> Microsoft Graph API's ability to send events to Azure Event Grid is currently in **private preview**. If you have questions or need support, please email us [mailto:[email protected]?subject=Support Request](<mailto:[email protected]?subject=Support Request>).
 
 |Microsoft event source |Resource(s) | Available event types | 
 |:--- | :--- | :----|
@@ -51,14 +51,13 @@ Besides the ability to subscribe to Microsoft Graph API events via Event Grid, y
 
 ## Enable Graph API events to flow to your partner topic
 
-> [!IMPORTANT]
-> In the following steps, you will follow instructions from [Node.js](https://github.com/microsoftgraph/nodejs-webhooks-sample), [Java](https://github.com/microsoftgraph/java-spring-webhooks-sample), and[.NET Core](https://github.com/microsoftgraph/aspnetcore-webhooks-sample) Webhook samples to enable flow of events from Microsoft Graph API. At some point in the sample, you will have an application registered with Azure AD. Email your application ID to <a href="mailto:[email protected]?subject=Please allow my application ID">mailto:[email protected]?subject=Please allow my Azure AD application with ID to send events through Graph API</a> so that the Microsoft Graph API team can add your application ID to allow list to use this new capability.
-
 You request Microsoft Graph API to send events by creating a Graph API subscription. When you create a Graph API subscription, the http request should look like the following sample:
 
 ```json
 POST to https://graph.microsoft.com/beta/subscriptions
 
+x-ms-enable-features: EventGrid
+
 Body:
 {
     "changeType": "Updated,Deleted,Created",
@@ -69,8 +68,9 @@ Body:
 }
 ```
 
-Here are some of the key payload properties:
+Here are some of the key headers and payload properties:
 
+- `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.
 - `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.
 - `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>`.
 - resource: the resource for which you need events announcing state changes.