azure-samples / active-directory-dotnet-native-uwp-v2

A Windows Universal Platform client application using msal.net, accessing the Microsoft Graph for a user authenticating with Azure AD V2 endpoint

services	platforms	author	level	client	service	endpoint	page_type	languages	products	description	urlFragment
active-directory	dotnet	Shama-K	200	UWP	Microsoft Graph	Microsoft identity platform	sample	csharp	azure azure-active-directory windows windows-uwp office-ms-graph	This sample demonstrates how to use the Microsoft Authentication Library for .NET to get an access token and call the Microsoft Graph from a UWP app.	uwp-signing-in-graph-aad

Universal Windows Platform application signing in users with Microsoft and calling the Microsoft Graph

Getting Started	Library	Docs	Support

About this sample

Table of contents

• Universal Windows Platform application signing in users with Microsoft and calling the Microsoft Graph
  • About this sample
    • Table of contents
    • Overview
  • Steps to run
  • How to run this sample
    • Step 1: Clone or download this repository
    • Step 2: Register the sample application with your Azure Active Directory tenant
      • Choose the Azure AD tenant where you want to create your applications
      • Register the UWP App (UWP-App-calling-MSGraph)
    • Step 3: Configure the UWP App (UWP-App-calling-MSGraph) to use your app registration
    • Step 4: Run the sample
  • Community help and support
  • Contributing
  • More information

Overview

This sample demonstrates how to use the Microsoft Authentication Library (MSAL) for .NET to get an access token and call the Microsoft Graph using the MS Graph SDK from a Universal Windows Platform (UWP) application.

1. The .NET client UWP application uses the Microsoft Authentication Library (MSAL) to sign-in a user and obtain a JWT access token from Azure Active Directory (Azure AD).
2. The access token is then used as a bearer token to call Microsoft Graph and fetch the signed-in user's details.

Looking for previous versions of this code sample? Check out the tags on the releases GitHub page.

Steps to run

You can get full explanation about this sample, and build it from scratch by going to Call the Microsoft Graph API from a Universal Windows Platform (UWP) application. You would have to change a few things (see below, build from scratch)

How to run this sample

To run this sample, you'll need:

• Visual Studio 2022
• An Internet connection
• Windows SDK minimum version 10.0.17663.0
• An Azure Active Directory (Azure AD) tenant. For more information on how to get an Azure AD tenant, see How to get an Azure AD tenant
• A user account in your Azure AD tenant. This sample will not work with a Microsoft account (formerly Windows Live account). Therefore, if you signed in to the Azure portal with a Microsoft account and have never created a user account in your directory before, you need to do that now.
• AzureAD Powershell Module if opting to use the automatic set up in Step 2 (available at the Powershell Gallery)

Step 1: Clone or download this repository

From your shell or command line:

git clone https://github.com/Azure-Samples/active-directory-dotnet-native-uwp-v2.git

or download and extract the repository .zip file.

Given that the names of the referenced NuGet packages are quite long, you might want to clone it in a folder close to the root of your hard drive, to avoid file size limitations on Windows.

Step 2: Register the sample application with your Azure Active Directory tenant

Choose the Azure AD tenant where you want to create your applications

As a first step you'll need to:

1. Sign in to the Azure portal using either a work or school account or a personal Microsoft account.
2. If your account is present in more than one Azure AD tenant, select your profile at the top right corner in the menu on top of the page, and then switch directory. Change your portal session to the desired Azure AD tenant.

Register the UWP App (UWP-App-calling-MSGraph)

1. Navigate to the Microsoft identity platform for developers App registrations page.
2. Select New registration.
3. In the Register an application page that appears, enter your application's registration information:
   • In the Name section, enter a meaningful application name that will be displayed to users of the app, for example UWP-App-calling-MSGraph.
   • Under Supported account types, select Accounts in any organizational directory and personal Microsoft accounts (e.g. Skype, Xbox, Outlook.com).
4. Select Register to create the application.
5. In the app's registration screen, find and note the Application (client) ID. You use this value in your app's configuration file(s) later in your code.
6. The redirect URI is tied to the application's identity. To find it, execute the following code inside your app:

 // returns smth like S-1-15-2-2601115387-131721061-1180486061-1362788748-631273777-3164314714-2766189824
string sid = Windows.Security.Authentication.Web.WebAuthenticationBroker.GetCurrentApplicationCallbackUri().Host.ToUpper();

// This is redirect uri you need to register in the app registration portal. The app config does not need it.
string redirectUri = $"ms-appx-web://microsoft.aad.brokerplugin/{sid}";

1. In the app's registration screen, select Authentication in the menu.

   • If you don't have a platform added, select Add a platform and select the Public client (mobile & desktop) option.
   • In the Redirect URIs | add the redirect URI of your app (see above).

2. Select Save to save your changes.

3. In the app's registration screen, click on the API permissions blade in the left to open the page where we add access to the APIs that your application needs.

   • Click the Add a permission button and then,
   • Ensure that the Microsoft APIs tab is selected.
   • In the Commonly used Microsoft APIs section, click on Microsoft Graph
   • In the Delegated permissions section, select User.Read in the list. Use the search box if necessary.
   • Click on the Add permissions button at the bottom.

Step 3: Configure the UWP App (UWP-App-calling-MSGraph) to use your app registration

Open the project in your IDE (like Visual Studio) to configure the code.

In the steps below, "ClientID" is the same as "Application ID" or "AppId".

1. Open the Native_UWP_V2\MainPage.xaml.cs file
2. Find the below line

   private const string ClientId = "4a1aa1d5-c567-49d0-ad0b-cd957a47f842"

   and replace the existing value with the application ID (clientId) of the UWP-App-calling-MSGraph application copied from the Azure portal.
3. Another option is to modify this line which is currently set to "Common" that means that an user from any Tenant can log-in into the application. To restrict the log-in to current tenant, you should change the value to tenant Id or tenant name as explained inside comment for the line.

Step 4: Run the sample

1. Run the application from Visual Studio (Debug | Start without Debugging), directly on the local machine, or after deploying to a device or an emulator.

Consider taking a moment to share your experience with us.

Community help and support

We use Stack Overflow with the community to provide support. We highly recommend you ask your questions on Stack Overflow first and browse existing issues to see if someone has asked your question before. Make sure that your questions or comments are tagged with [msal.dotnet].

If you find and bug in the sample please raise the issue on GitHub Issues.

If you find a bug in msal.Net, please raise the issue on MSAL.NET GitHub Issues.

To provide a recommendation, visit our User Voice page.

Contributing

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 [email protected] with any additional questions or comments.

More information

For more information see MSAL.NET's conceptual documentation:

• Quickstart: Register an application with the Microsoft identity platform (Preview)
• Quickstart: Configure a client application to access web APIs (Preview)
• Recommended pattern to acquire a token in public client applications
• Acquiring tokens interactively in public client applications

active-directory-dotnet-native-uwp-v2's Issues

2 factor authentication error.

I'm getting an error '

An error occurred 

No valid client certificate found in the request. No valid certificates found in the user's certificate store. Please try again choosing a different authentication method. 

when attempting to login with an account that has 2 factor authentication enabled.
Steps to reproduce:

1. Build and run this sample. (active-directory-dotnet-native-uwp-v2)
2. Click 'Call Microsoft Graph API'
3. Login with account that has 2 factor authentication enabled (an @Microsoft.com account for example).
4. Click 'Sign in with PIN or smartcard'
5. A message about a pop up is briefly displayed. Followed by the error mentioned above.

How can I login using my 2 factor PIN or certificate?

Cannot authenticate using this example with my work's AD

I have created/registered an Azure AD application in the Azure portal against my work's AD and I am using its ClientID in this demo app.

Whenever I try and login I enter my work email address and the pop up redirects to my work's log in page. Once I type in my password I am redirected to a blank page with the following error message:

We can't connect to the service you need right now. Check your network connection or try this again later.

I can successfully log in to the Graph explorer with my work email address and then access the Graph API there to access the information I need.

I've tried running Fiddler to find out where the popup is trying to go but Fiddler running stops it from working at all.

Is there anything else I need to do to get the PublicClientApplication.AcquireTokenAsync to work with work's AD?

[DOCS] #UWP specific considerations anchor does not exist

In the README there is no anchor for 'UWP specific considerations': https://github.com/Azure-Samples/active-directory-dotnet-native-uwp-v2#UWP-specific-considerations

Replace the redirect URI by https://login.microsoftonline.com/common/oauth2/nativeclient

Why?
Public client application should not use urn:ietf:wg:oauth:2.0:oob but https://login.microsoftonline.com/common/oauth2/nativeclient

What needs to be done?

1. Create a new app to use the https://login.microsoftonline.com/common/oauth2/nativeclient redirect URI
2. Change the code of the sample to use .WithDefaultRedirectUri
3. Change the apps.json and the sample.json to specify https://login.microsoftonline.com/common/oauth2/nativeclient
4. Update the text of the quickstart article (see (https://docs.microsoft.com/en-us/azure/active-directory/develop/quickstart-v2-uwp)
5. Use 2 branches (for the download zip file) until the portal reflects the new version of the quickstart.

MSAL and WIA

Hello,
Could you please update this documentation, as MSAL does not support WIA yet. I know this is something on the roadmap and you are working on, could we perhaps get an ETA for when might be available?
Thanks

app.json appsetting path is wrong

Please fix the issue based on change in #39

Step 3 in the readme is not needed

Step 3 asks to provision an app in the app portal. This does not seem to be needed as the current client id works fine.

Windows Hello PIN/Smartcard issue resolved?

Can somebody please check if the issue mentioned in the README below Known limitation is resolved by enabling Shared User Certificates on package.appxmanifest's Capabilities tab?

More info: https://docs.microsoft.com/en-us/azure/active-directory/develop/tutorial-v2-windows-uwp#enable-integrated-authentication-on-federated-domains-optional

Update this sample to use WAM.

• Update the sample to use WAM. Nothing else should be used on UWP
• Update the README.md

why MSAL freeze on UWP app on AcquireTokenInteractive?

often after entering the password and clicking on proceed I am blocked without receiving errors. sometimes it works correctly if i repeating the operation several times.

https://stackoverflow.com/questions/71103563/why-msal-freeze-on-uwp-app-on-acquiretokeninteractive

Can't authenticate @live.com user

Hi,

I followed the steps, registered a new app and changed the client id in the code. When I login with my work account it works fine and I'm authenticated. But when I try to login with my personal Microsoft account there's an error after I write my email and click Next:

We're unable to complete your request
Microsoft account is experiencing technical problems. Please try again later.

Why is that?