Register an app with the Azure Active Directory v2.0 endpoint

In order to access Microsoft Planner data like Plans and Buckets, the approach taken was to use GraphServiceClient with C# – let us see the implementation step by step.

Develop line-of-business apps for Azure Active Directory

Registering the application means that developers can use Azure AD to authenticate users and request access to User resources such as email, calendar, documents and office 365 application such as Team, Planner, Graph Api.

Note that in AAD App Registrations, we have 2 types of “Application Type”: 

Develop line-of-business apps for Azure Active Directory
    • Native applications are public clients in OAuth2 parlance. Those apps are meant to run on a device and aren’t trusted to maintain a secret – hence, their entry in the directory does not have the corresponding property. Without a secret, there is no way to assert the identity of the app – hence such apps cannot gain app-level permissions and the portal UX reflects that.
    • Conversely, web apps are, again in OAuth2 parlance, confidential clients. They can get delegated tokens for their users, but they can also use client credentials to get tokens themselves. Native apps can obtain tokens for the user via the OAuth2 authorization grant.

You can find a complete overview of all supported topologies at Each scenario description point to more implementation-oriented guidance.