Microsoft Graph Connect Sample for UWP (Library)
Building apps for enterprise customers? Your app may not work if your enterprise customer turns on enterprise mobility security features like conditional device access. In this case, you may not know and your customers may experience errors.
To support all enterprise customers across all enterprise scenarios, you must use the Azure AD endpoint and manage your apps using the Azure Management Portal. For more information, see Deciding between the Azure AD and Azure AD v2.0 endpoints.
Table of contents
- Register and configure the app
- Build and debug
- Questions and comments
- Additional resources
This sample shows how to connect your Windows 10 Universal app to Office 365 using the Microsoft Graph API (previously called Office 365 unified API) to send an email. It uses the Microsoft Graph .NET Client Library to work with data returned by Microsoft Graph. The sample uses the Azure AD v2.0 endpoint, which enables users to sign in with either their personal or work or school Microsoft accounts.
This sample requires the following:
- Visual Studio 2015
- Windows 10 (development mode enabled)
- Either a Microsoft or Office 365 for business account.
Register and configure the app
- Sign into the App Registration Portal using either your personal or work or school account.
- Select Add an app.
Enter a name for the app, and select Create application.
The registration page displays, listing the properties of your app.
Under Platforms, select Add platform.
- Select Mobile platform.
Copy both the Application Id and Redirect URI values to the clipboard. You'll need to enter these values into the sample app.
The app id is a unique identifier for your app. The redirect URI is a unique URI provided by Windows 10 for each application to ensure that messages sent to that URI are only sent to that application.
Build and debug
Note: If you see any errors while installing packages during step 2, make sure the local path where you placed the solution is not too long/deep. Moving the solution closer to the root of your drive resolves this issue.
After you've loaded the solution in Visual Studio, configure the sample to use the application (client) id and redirectURI that you registered by adding the corresponding values for these keys in the Application.Resources node of the App.xaml file. `
Press F5 to build and debug. Run the solution and sign in with either your personal or work or school account.
Summary of key methods
The code in the main page of the app is relatively straight-forward and self-explanatory, as the calls for authentication and email service actually occur in the helper classes. The main page code primarily consists of event handlers for the two buttons:
This method calls the GetAuthenticatedClientAsync method to acquire a GraphServicesClient object representing the current user, which it uses to set user email address and display name. If this is successful, it also enables the send mail button and the text box where the user can enter an email address, and populates that text box with the user's own email address.
This method calls the ComposeAndSendMailAsync method, using the email address and display name variables set during ConnectButton_Click. If this method call is successful, it also updates the UI text accordingly.
With that in mind, it's worth looking at two methods in the helper classes in a little more detail:
This method of the AuthenticationHelper class authenticates the user with the Azure AD v2.0 endpoint.
It does this by creating an AppConfig object that specifies the app client ID, return URL, and the scopes requested by the app. It then uses this AppConfig object to construct an OAuth2AuthenticationProvider object, and calls the AuthenticateAsync method on the authentication provider. Finally, it creates a GraphServicesClient object using the OAuth2AuthenticationProvider object.
The SignInCurrentUserAsync method on the main page can then read user from this GraphServicesClient object and set the user email address and display name.
This method of the MailHelper class uses the Microsoft Graph SDK to authenticate the user with the Azure AD v2.0 endpoint, compose a sample email, and then send the email using the user's account.
It does this by declaring a GraphServicesClient object and setting it equal to the return value of AuthenticationHelper.GetAuthenticatedClientAsync. The method then composes the sample email, using various objects in the Microsoft.Graph namespace. Finally, it calls the SendMail method.
If you'd like to contribute to this sample, see CONTRIBUTING.MD.
Questions and comments
We'd love to get your feedback about the UWP Microsoft Graph Connect SDK project. You can send your questions and suggestions to us in the Issues section of this repository.
Your feedback is important to us. Connect with us on Stack Overflow. Tag your questions with [MicrosoftGraph] and [office365].
- Other Office 365 Connect samples
- Microsoft Graph overview
- Office 365 APIs platform overview
- Office 365 API code samples and videos
- Office developer code samples
- Office dev center
Copyright (c) 2016 Microsoft. All rights reserved.