This project is being archived and replaced with the Build MVC apps with the Microsoft Graph .NET SDK training. As part of the archival process, we're closing all open issues and pull requests.

You can continue to use this sample "as-is", but it won't be maintained moving forward. We apologize for any inconvenience.

• Introduction
• Prerequisites
• Register the application
• Build and run the sample
• Deploy the sample to Azure
• Code of note
• Questions and comments
• Contributing
• Additional resources

This sample shows how to connect an ASP.NET 4.6 MVC web app to a Microsoft work or school (Azure Active Directory) or personal (Microsoft) account using the Microsoft Graph API to retrieve a user's profile picture, upload the picture to OneDrive, and send an email that contains the photo as an attachment and the sharing link in its text. It uses REST calls to interact with the Microsoft Graph API.

In addition, the sample uses the Microsoft Authentication Library (MSAL) for authentication. The MSAL SDK provides features for working with the Azure AD v2.0 endpoint, which enables developers to write a single code flow that handles authentication for both work or school (Azure Active Directory) and personal (Microsoft) accounts.

This library is suitable for use in a production environment. We provide the same production level support for this library as we do our current production libraries. During the preview we may make changes to the API, internal cache format, and other mechanisms of this library, which you will be required to take along with bug fixes or feature improvements. This may impact your application. For instance, a change to the cache format may impact your users, such as requiring them to sign in again. An API change may require you to update your code. When we provide the General Availability release we will require you to update to the General Availability version within six months, as applications written using a preview version of library may no longer work.

This sample requires the following:

• Visual Studio 2015
• Either a Microsoft account or work or school account

1. Sign into the Application Registration Portal using either your personal or work or school account.

2. Choose Add an app.

3. Enter a name for the app, and choose Create application.

   The registration page displays, listing the properties of your app.

4. Copy the Application Id. This is the unique identifier for your app.

5. Under Application Secrets, choose Generate New Password. Copy the password from the New password generated dialog.

   You'll use the application ID and password (secret) to configure the sample app in the next section.

6. Under Platforms, choose Add Platform.

7. Choose Web.

8. Make sure the Allow Implicit Flow check box is selected, and enter http://localhost:55065/ as the Redirect URI.

   The Allow Implicit Flow option enables the hybrid flow. During authentication, this enables the app to receive both sign-in info (the id_token) and artifacts (in this case, an authorization code) that the app can use to obtain an access token.

9. Choose Save.

1. Download or clone the Microsoft Graph Connect Sample for ASP.NET 4.6.

2. Open the sample solution in Visual Studio.

3. In the Web.config file in the root directory, replace the ida:AppId and ida:AppSecret placeholder values with the application ID and password that you copied during app registration.

4. Press F5 to build and run the sample. This will restore NuGet package dependencies and open the app.

   If you see any errors while installing packages, 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.

5. Sign in with your personal or work or school account and grant the requested permissions.

6. Choose the Get email address button. When the operation completes, the email address of the signed-in user is displayed on the page.

7. Optionally edit the recipient list and email subject, and then choose the Send email button. When the mail is sent, a Success message is displayed below the button.

8. Next steps: Check out the Microsoft Graph Snippets Sample for ASP.NET 4.6 to see examples of common Microsoft Graph operations.

If you have an Azure subscription, you can publish the sample app to an Azure website. These instructions assume you've already registered the sample app in the Application Registration Portal.

1. Sign into the Azure Portal with your Azure credentials.

2. Choose New > Web + Mobile > Web App.

3. Give the website a unique name. Choose a resource group, and click Create.

4. Select the new web app in your list of resources.

5. Choose Overview in the left-hand pane, and then choose Get publish profile (or More > Get publish profile) from the menu above the web app's Essentials pane.

6. Save the profile locally.

1. In Visual Studio, open the sample app. Right-click the Microsoft Graph REST ASPNET Connect project node and choose Publish.

2. In the Publish dialog, choose Import, and choose the publish profile file you just downloaded.

3. On the Connection tab of the Publish dialog, change the http protocol to https in the Destination URL of your new web app.

4. Copy the Destination URL, and and then click Publish. Close the browser window that opens.

5. In the Web.config file, replace the ida:RedirectUri value to the Destination URL that you just copied.

6. Choose View > Other Windows > Web Publish Activity.

7. In the Web Publish Activity window, click the Publish Web button (looks like a globe) on the toolbar. This is how you can update the published project after you make changes.

1. In the Application Registration Portal, open the application that you registered for the sample (as described in Register the application).

2. In the Web platform section, replace the http://localhost:55065/ Redirect URI with the Destination URL of your new web app. (Alternatively, you can click Add Url and add the Destination URL.)

3. Click Save.

The new Azure web app should now be ready to use.

• Startup.Auth.cs. Authenticates the current user and initializes the sample's token cache.

• SessionTokenCache.cs. Stores the user's token information. You can replace this with your own custom token cache. Learn more in Caching access tokens in a multitenant application.

• SampleAuthProvider.cs. Implements the local IAuthProvider interface, and gets an access token by using the MSAL AcquireTokenSilentAsync method. You can replace this with your own authentication provider.

• GraphService.cs. Contains methods (called by HomeController) that build and send REST calls to the Microsoft Graph API, and process the response.

  • The GetMyEmailAddress action gets the email address of the current user from the mail or userPrincipalName property.
  • The SendMail action sends an email on behalf of the current user.

• Graph.cshtml. Contains the sample's UI.

We'd love to get your feedback about this sample. You can send us your questions and suggestions in the Issues section of this repository.

Your feedback is important to us. Connect with us on Stack Overflow. Tag your questions with [MicrosoftGraph].

If you'd like to contribute to this sample, see CONTRIBUTING.md.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

• Other Microsoft Graph Connect samples
• Microsoft Graph overview

Copyright (c) 2016 Microsoft. All rights reserved.