Add the application’s registration information to your app
In this step, you need to add the Application Id to your project.
App.xaml.csand replace the line containing the
private static string ClientId = "[Enter the application Id here]";
What is Next
Test your code
To test your application in Visual Studio, press F5 to run your project. The MainWindow for your application is displayed:
When you're ready to run your test, use a Microsoft Azure Active Directory account (work or school account) or a Microsoft account (live.com, outlook.com) to sign in. The first time that you run the application, you're prompted to sign in:
Provide consent for application access
The first time that you sign in to your application, you're prompted to provide your consent to allow the application to access your profile and to sign you in:
View application results
After you sign in, you should see the user profile information returned by the call to the Microsoft Graph API. The results are displayed in the API Call Results box. Basic information about the token that was acquired via the call to AcquireTokenAsync or AcquireTokenSilentAsync should be visible in the Token Info box. The results contain the following properties:
|Name||User's full name||The user’s first and last name.|
|Usernameemail@example.com||The username that is used to identify the user.|
|Token Expires||DateTime||The time at which the token expires. MSAL extends the expiration date by renewing the token as necessary.|
|Access Token||String||The token string that is sent to HTTP requests that require an Authorization header.|
More information about scopes and delegated permissions
The Microsoft Graph API requires the user.read scope to read a user's profile. This scope is automatically added by default in every application that's registered on the registration portal. Other APIs for Microsoft Graph, as well as custom APIs for your back-end server, might require additional scopes. The Microsoft Graph API requires the Calendars.Read scope to list the user’s calendars.
To access the user’s calendars in the context of an application, add the Calendars.Read delegated permission to the application registration information. Then, add the Calendars.Read scope to the acquireTokenSilent call.
The user might be prompted for additional consents as you increase the number of scopes.
Help and support
If you need help, want to report an issue, or would like to learn more about your support options, see the following article: