In this article, I will introduce you to the MS Graph API which is a powerful way to interact with Office 365 data.
Here are the objectives of this article:
- What is MS Graph API?
- How it came into picture?
- What are its features, benefits and limitations?
- MS Graph Explorer
- MS Graph SDK
Let’s start with MS Graph API.
What is MS Graph API?
The official MS documentation defines MS Graph API as:
“You can use the Microsoft Graph API to interact with the data of millions of users in the Microsoft cloud. Use Microsoft Graph to build apps for organizations and consumers that connect to a wealth of resources, relationships, and intelligence, all through a single endpoint: https://graph.microsoft.com”
In a nutshell, MS Graph API gives you a single REST API endpoint which you can call to interact with “almost anything” in Office 365.
How it came into picture?
Prior to MS Graph API, Microsoft had different APIs for it’s different Office 365 and cloud products. Outlook, OneDrive, OneNote, Yammer all had their different APIs to interact with them.
Consider the following steps involved while dealing with different Office 365 APIs in an application:
- Find the URL/endpoint of the API
- Authenticate / get access token
- Get results from the API
- Repeat for each service
- Manage multiple tokens for each API
It made a developer’s life difficult if one had to connect to many different APIs in an application.
As a solution, Microsoft launched the MS Graph API which is also called “One endpoint to rule them all”.
Why should you learn MS Graph API?
Office 365 is undoubtedly most widely used office produce worldwide. Millions of people are using the commercial versions of Office 365 suite or one or another of its products like Outlook, OneNote, etc.
On an average, a user in any office will use 2-3 hours working on different Office suite product like Outlook, Excel, Project, etc. Millions of new emails, events, etc. are generated in Outlook and millions of files are stored on OneDrive.
If you want to access all this information stored in Office 365 or on Azure, then you need MS Graph API.
- Single well-known resource
MS Graph API is the easiest way to interact with Office 365 data. Using MS Graph API, you can get mostly everything from a single endpoint https://graph.microsoft.com.
- Ease of development
It liberates a developer from calling different Office 365 APIs and doing multiple token management.
- Logical navigation
The entities of Office 365 are accessible in a logical way thru MS Graph API. Look again at the picture posted at the top of this article. You will see that once you access a user, all other entities related to it – files, messages, notes, etc. – are then accessible in a logical manner.
You don’t have to remember how an entity will be accessed, it follows a logical manner of graph structure.
- Platform flexibility
MS Graph API does not mandate you to learn a new programming language. It can work with many different languages/platforms and Microsoft has launched SDKs to work with different platforms. You can work with MS Graph API in Windows/Android/iOS platforms. You can read more on it on last section of this article “MS Graph SDK”
- MS Identity Stack
MS Graph API does not introduce any new authentication mechanism where users have to go to register and then remember one more user name and password.
Instead, MS Graph API uses the Microsoft identity stack (which is used by 85% of fortune 500) – means that your users can login using the same familiar Azure AD / Microsoft Office 365 login credentials in your application.
MS Graph API uses Open ID Connect for authentication and OAUTH 2.0 for access tokens.
- Open Standards
MS Graph API is based on and it supports many open web standards making it flexible and highly interoperable. Some of these standards are:
REST – heart of MS Graph API implementation, any device/technology able to make http call and able to interpret JSON can work with MS Graph API
JSON – lightweight format for request and response data
OAUTH – provides API access token management, MS Graph API supports OAUTH v2.0
ODATA – MS Graph API supports open data protocol v4.0 which is also called “The best way to REST”. It uses URL query string operators to make simple, standard and readable expressions.
I have written some articles on using optional ODATA query parameters with MS Graph API which can be found here:
- Using optional query parameters with Microsoft Graph API – Part One
- Using optional query parameters with Microsoft Graph API – Part Two
Using webhooks, MS Graph API can send you notification for any changes in entities for which you have subscribed to. Instead of keeping on querying MS Graph API to see if there are any changes, you can use webhooks mechanism to have notification sent to you in case of any action/event happening. For example, you can subscribe to get notified when a new message arrives.
- Intelligence & Insights
MS Graph API does not only do simple input and output operations on your organization’s Office 365 entities. Instead of that, MS Graph API also has intelligence inbuilt in it which can help you to find treading documents around a user, people frequently contacted, etc. It can also help you find the best meeting times in a team.
- Custom data extensions
You can extend MS Graph API results with custom data i.e. you can add custom data to MS Graph without using any external data source. This is helpful when you want to store some custom data relevant to your application e.g. profile setting or favorite theme, etc.
There are two types of extensions: Open extensions which are flexible and allows you to store any untyped data; and Schema extensions where you can define your own complex strongly typed schema, which can be shared between your different applications.
- Delta query
Using delta query, it become easier to track data changes in entities. Instead of getting list of all entities and comparing them one by one to identify any changes, just fire a call using delta query which will give you only the changes i.e. inserted, updated, deleted data since your last call.
Using MS Graph API’s JSON Batching you can combine multiple requests in one HTTP call and optimize application performance. Instead of looping thru multiple calls in your application, you can fire all related / unrelated calls in one batch in one go.
The most visible one is some of its features are still in beta, but MS Graph team keeps launching new features in live regularly.
For a list of all MS Graph API known issues, refer here.
MS Graph API Explorer
MS Graph API Explorer is a great tool to get started with MS Graph API and learn first-hand how it works. Graph Explorer is a developer sandbox where you can fire actual Graph API call and see its result.
You can access MS Graph API Explorer here.
I have written some articles on how to use MS Graph Explorer which can be found here:
- A First Look at The New Microsoft Graph Explorer – Part One
- A First Look at The New Microsoft Graph Explorer – Part Two
- A First Look at The New Microsoft Graph Explorer – Part Three
Microsoft Graph SDK
MS Graph team has done some great work in launching SDKs for different platforms which makes development with MS Graph API easy.
You don’t have to code everything from scratch, ready to start code is available in SDK.
The following SDKs are available:
If you are a java developer, then recently Microsoft has launched Java SDK for MS Graph API in preview.
If you want to add MS Graph SDK in any of your C# application, then open Visual Studio and simply search for “Microsoft Graph” in NuGet package manager to get started:
That’s it for introduction to MS Graph API in this article. Wait for my next article where I will show how you can start programming in MS Graph API.
Till then following links will be useful to get started with MS Graph API: