Event Grid is a highly scalable, serverless event broker you can use to integrate applications using event-driven architectures. We are now announcing the availability (preview) of new event sources through the integration of Microsoft Graph API (MGA) with Azure Event Grid. Through this partnership, Microsoft Graph API notifications publishes events associated to its supported event sources. With Azure Event Grid you are now able to subscribe to events from the following resources ():
Most new events reflect state changes that are triggered when a resource is created, updated or deleted. For example, if you are interested in receiving user state changes, you could subscribe to event types “Microsoft.Graph.UserCreated, Microsoft.Graph.UserUpdated, and Microsoft.Graph.UserDeleted”.
Build event-driven applications that react to events published by Microsoft Graph API
You can use events published by MGA to build solutions, on Azure or elsewhere, to carry out important business functions. The runtime architecture involves a user that creates, updates, or deletes a resource, the communication of the resource state to MGA (an internal implementation detail), MGA publishing events to a customer’s partner topic, and event subscriptions configured to select and deliver events to event handlers that process the events. For example, the following diagram shows the runtime architecture for the use case where an Azure AD Admin updates a user in a tenant that triggers a Microsoft.Graph.UserUpdated event.
Following are some use cases you can now realize. This is not a comprehensive list, but it should give you a good idea of the possibilities.
Automate onboarding procedures when a new user is created.
Remove access to users that have moved to another department and grant new access to users for their new department.
Based on a user location change, user is now added to a new group.
Events (Outlook calendar meetings)
Sync your custom application with updates to meeting invites that your application tracks.
Use Microsoft Outlook Contacts as your system of record and sync your applications when a contact is added, updated or deleted.
Receive a copy of the chat messages and show them or otherwise have them processed by your custom application.
Communicate or share the “joinWebUrl” for Team meetings that your solution tracks.
Microsoft SharePoint and OneDrive
Read or process a file, for example an image, when a new file has been uploaded.
Send an email that describes required actions to a user when a SharePoint list has a new row.
React to potential security issues by subscribing to security alert events. You can consult the list of security providers that support alert subscriptions on this article.
React to incoming print jobs by collecting relevant job metadata or perform modifications in the print job, including aborting the job or redirecting the job from the current print queue to another queue.
To subscribe to Microsoft Graph API events, follow the instructions in and in this section of the article click on the Microsoft Graph API link. At the end of those instructions, you will have a partner topic created on your Azure subscription. From that point on, you can configure event subscriptions to select and forward events to event handler(s) that best meet your requirements for processing the events.
New to Azure Event Grid or not sure if it is the right message broker for your needs?
If you have a question whether Event Grid meets your requirements, please consult this article to help you understand the different message brokers that Azure provides and their applicability for different use cases.
We are here to help you through your journey. Following are the ways you can get your issues or questions answered by our teams:
Problems with Event Grid? Please create a support request using the Azure Portal.