Graph-Controls | Windows 10 development using the Microsoft Graph | Runtime Evironment library

Leverage the official Microsoft Authentication Library (MSAL) to enable authentication in any NetStandard application. Note: You can use the Scopes property to preemptively request permissions from the user of your app for data your app needs to access from Microsoft Graph.
Register your app in Azure AAD Before requesting data from Microsoft Graph, you will need to register your application to get a ClientID. After finishing the initial registration page, you will also need to add an additional redirect URI. Click on "Add a Redirect URI", then "Add a platform", and then on "Mobile and desktop applications". Check the https://login.microsoftonline.com/common/oauth2/nativeclient checkbox on that page. Then click "Configure".
Install the CommunityToolkit.Authentication.Msal package.
Set the GlobalProvder to a new instance of MsalProvider with clientId and pre-configured scopes: using CommunityToolkit.Authentication; string clientId = "YOUR-CLIENT-ID-HERE"; string[] scopes = new string[] { "User.Read" }; ProviderManager.Instance.GlobalProvider = new MsalProvider(clientId, scopes);
Try out the WindowsProvider to enable authentication based on the native Windows Account Manager (WAM) APIs in your UWP apps, without requiring a dependency on MSAL.
Associate your app with the Microsoft Store. The app association will act as our minimal app registration for authenticating consumer MSAs. See the WindowsProvider docs for more details.
Install the CommunityToolkit.Authentication.Uwp package
Set the GlobalProvider to a new instance of WindowsProvider with pre-configured scopes: using CommunityToolkit.Authentication; string[] scopes = new string[] { "User.Read" }; ProviderManager.Instance.GlobalProvider = new WindowsProvider(scopes);