30DaysMSGraph – Day 1 – Why you should learn Microsoft Graph
“Before you ever write a single line of code, know why you are writing it” -Author Unknown
As with any good project or endeavor it is good to Start with Why. In this first blog post we will introduce why you should learn Microsoft Graph.
Microsoft Graph unifies API access to the services in the Microsoft 365 suite. Developers can now consume data through a single public endpoint (https://graph.microsoft.com) – using simple REST calls or with an SDK available on just about any platform. Authentication models are standardized. Permissions are secure, granted using OAuth protocols. And some Microsoft Graph data schemas are extensible – enabling support for custom applications.
But Microsoft Graph is about more than ease of use and standardization of access to API endpoints for modern developers. Microsoft Graph offers developers the power to access and traverse the rich sets of user-centered data, insights and updates available beneath the wide and growing range of Microsoft 365 products. Additionally, administrators can grant fine grained permissions (instead of global / service administrator or similarly elevated roles) to applications that are accessing data or can revoke access if needed. With this power, it’s possible to create and manage apps that are built to create amazing productivity experiences where and when you need them – at home, at work, at your desk or on the go.
Try It Out
Each day you can go further in your learning with hands-on “Try It Out” exercises, useful resources, and later sample solutions. All “Try It Out” exercises will be available through this GitHub repo: https://github.com/microsoftgraph/30DaysMSGraphTryItOut
- What’s new on Microsoft Graph (BUILD 2018): https://channel9.msdn.com/events/Build/2018/THR5011
Thanks for starting out with us on this 30-day trek. Join us tomorrow for an overview what’s in Microsoft Graph in Day 2. Remember you can also follow along on the Microsoft Graph blog RSS: https://aka.ms/GraphBlogRSS.