Call an Azure AD protected API in Xamarin/UWP apps

Call an Azure AD protected API in Xamarin/UWP apps

When we talk about mobile apps, a web API is generally hiding in the background, doing most of the work like connecting to a database, verifying authorization, computing data, and so on.
Like everything else, those APIs need protection against unauthorized calls that don’t come from our mobile apps.

In this post, I will explain how to leverage Azure Active Directory to protect our WebAPI without any code, and how to call this WebAPI from our mobile apps.

So, how do we do that?

In order, we will :
1) Enable Azure AD authentication on our API
2) Declare our apps in the Azure AD in order to allow them to authenticate their users and give them access to our API
3) Implement ADAL.NET in our apps to authenticate the user and retrieve an access token for our API
4) Call our API with the access token
5) ???
6) Profit

Before we begin

For this post, I will use the default ASP.NET Core WebAPI that I will host in an Azure App Service.
The mobile apps will be made with Xamarin.iOS, Xamarin.Android and UWP, core logic will be implemented inside a .NETStandard 1.4 project.

I made a sample containing the WebAPI and the mobile apps, it’s available on Github :

If you want to run the sample, you will need to have an active Azure subscription with an Azure Active Directory. Then you will need to declare your apps in the Azure AD like we will see in this post.

Configuring Azure AD for the WebAPI

Before we can do anything with Xamarin or UWP, we need to set up our WebAPI and configure the authentication against Azure Active Directory.
This used to require lots of setup code in our WebAPI in order to allow only authenticated requests, most of the times specific to only one identity provider.
Well, this time Azure really make it easy on us with a “turn key” feature that require no code at all!

I have already created an Azure App Service named “woodenmoose-authsample-api” and published in it an ASP.NET Core WebAPI, generated from the default template.

To enable authentication with Azure AD, I just need to go into the “Authentication / Authorization” panel, turn the feature on and configure it to create a new Azure AD app representing my WebAPI.
Like this :

That’s it! As promised, we protected the WebAPI with no code whatsoever, as you can see when asking for the Index action of the ValuesController.

Configuring Azure AD for the mobile apps

Our API is now protected by Azure AD and we can authenticate ourselves directly in the browser, but our mobile apps aren’t ready yet to query the API.
This is because Azure AD won’t issue access tokens to unknown clients.

So there’s a little more configuration to do.

First, we’ll create a new native app entry into the Azure AD apps registry.
I have named it “woodenmoose-authsample-mobileapp“.

The RedirectUri will be used in the mobile apps to notify the success of the authentication.
It can be any URI that you want. But if you’re going for multitenancy authentication, Azure requires you follow a specific pattern :

I have set the value to “


Next, we’ll need to allow users connected to woodenmoose-authsample-mobileapp to access the web API.
For this, we have the “Required permissions” panel in the native app entry.
In it, we will select the api entry from the Azure AD.

Like this :

And then, we set the permission needed. In our case, simply “Access woodenmoose-authsample-api“.

And finally, the last step in configuring Azure AD is to tell our api registration that if our native app registration want to issue a token to access the API, it’s ok.

So we have to change our api registration and fill the “knownClientApplications” array in the manifest with the ApplicationId of our native app registration.

We have to use the manifest, because there’s no other interface that will allow us to do so.

And that’s it for the configuration! You’re still there?
Great, because now we’re finally going to write some code!

Implementing ADAL.NET

Now that all the configuration part on Azure is done, we can implement the authentication process in our apps before we can make a call to our API.
For that, we will use ADAL.NET (standing for Active Directory Authentication Library for dotNET) which is compatible with our 3 platforms.

ADAL.NET will take care of everything.
It will display a screen where the user will log in, handle every error cases (wrong account, wrong password, account disabled, etc.) and it will handle the OAuth process.
At the end, you receive the access token that you need to query the API.
Really simple!

So, to use ADAL.NET we need to add to our core library the nuget package “Microsoft.IdentityModel.Clients.ActiveDirectory” (version 3.13.8 at the time of writing)

A few tips so NuGet will accept to install ADAL :

  • If you’re making a PCL project, you’ll need to target the PCL Profile 7 (see image below for which platforms to select)
  • If you’re making a .NETStandard project, you’ll need to target at least .NET Standard 1.4

The reason is that the ADAL package is only compatible with those versions.

Here are the required platforms if you’re making a PCL.

Once ADAL installed, we have access to the AuthenticationContext class.
With it, we can ask for the user to log in.

public class AuthenticationManager
     private string _authority;
     private string _resource;
     private string _clientId;
     private Uri _redirectUri;
     private static IPlatformParameters _platformParameters;
     private string _accessToken;

     public async Task LoginAsync()
          var authContext = 
              new AuthenticationContext(_authority);

          var authResult = 
              await authContext.AcquireTokenAsync(

          var connectedUser = authResult.UserInfo;
          _accessToken = authResult.AccessToken;
     public static void SetParameters(
            IPlatformParameters platformParameters)
          _platformParameters = platformParameters;

Our LoginAsync method needs some parameters, let me explain them :

Parameter Description Where to get it
Authority URL of the authentication authority Two values are possible

  • If multitenancy is activated :
  • Otherwise :
Resource* Guid associated to the web app registration that we want to get a token for. This value can be found in the properties of the web app registration under the name “Application ID” (Thanks Darren for correcting that)
ClientId Guid associated to the native app registration that we want to authenticate against This value can be found in the properties of the native app registration under the name “Application ID”
RedirectUri URI that the OAuth process will call if the authentication is successful This value is the one that we configured in the native app registration. It can be found in the “Redirect URIs” panel.
PlatformParameters Platform specific interface that will change how ADAL.NET works We need to pass an instance of a platform specific implementation of this interface. We will see how in the next parts

For the Resource parameter, it seems that some Azure AD will accept that you give an URI (App ID) instead of a Guid. But I recommend that you give the Guid anyway so there won’t be any surprises.

So for my case, I’ll use those values

  • Authority =
  • Resource = c21a38b2-54bb-4027-b5e4-257f7d10f3f9
  • ClientId = 150526ad-75ee-44d5-a6e1-091ef0900d77
  • RedirectUri =

We are still missing the PlatformParameters instance for ADAL.NET to work.
Instanciating PlatformParameters is different for each platform so we will see how to do so for iOS, Android, and UWP.

Implementing iOS

The first step (after adding a reference to our core project) is to add a reference to the NuGet package “Microsoft.IdentityModel.Clients.ActiveDirectory” like in our core projet.
The reason is that this package will come with a platform specific DLL (for instance Microsoft.IdentityModel.Clients.ActiveDirectory.Platform) which contains the iOS implementation of the IPlatformParameters interface.

Then all that remains is to give our core project an instance of the iOS PlatformParameters

public partial class MainViewController : UIViewController
     public override void ViewDidLoad()
         var platformParameters = new PlatformParameters(this);

ADAL.NET requires that you give it the instance of the currently displayed UIViewController, so it can resume our application once the authentication is complete.
And we’re done for iOS.

Implementing Android

Android is mostly the same as iOS, to a slight exception.
We need to reference the NuGet package “Microsoft.IdentityModel.Clients.ActiveDirectory“.

And we need to pass our Android implementation of PlatformParameters the instance of our currently displayed Activity.

public class MainActivity : Activity
     protected override void OnCreate(Bundle bundle)
         var platformParameters = new PlatformParameters(this);

     protected override void OnActivityResult(int requestCode,
                                              Result resultCode,
                                              Intent data)
         base.OnActivityResult(requestCode, resultCode, data);


Notice that I have overridden the OnActivityResult method.
AuthenticationAgentContinuationHelper.SetAuthenticationAgentContinuationEventArgs needs to be called on OnActivityResult, otherwise ADAL.NET will not be able to resume our application on authentication success.

Implementing UWP

Like iOS and Android, UWP needs to reference the NuGet Package “Microsoft.IdentityModel.Clients.ActiveDirectory“.
If you try to build now, you may notice that the build fails. Just update your “Microsoft.NETCore.UniversalWindowsPlatform” package to version 5.2.2 minimum.

Unlike iOS and Android, UWP doesn’t need to access the currently displayed Window.
So instead, we can just set up our PlatformParameters in the App.xaml.cs file

public partial class App : Application
     public App()
          this.Suspending += OnSuspending;

          var platformParameters = 
              new PlatformParameters(PromptBehavior.Auto, false);


What about Xamarin.Forms?

Well, it works the same way as we saw for iOS, Android, and UWP.
The only thing that differ is how to retrieve the current UIViewController and Activity.
See the blog post from Xamarin “Put Some Azure Active Directory in Xamarin.Forms” for more information.

Calling the API

Now that we finally have the access token, we can use it with HttpClient.
To use it, we just have to set the Authorization header.

Like this:

var client = new HttpClient();
client.DefaultRequestHeaders.Authorization =
       new AuthenticationHeaderValue("Bearer", _accessToken);

var result = 
    await client.GetAsync(new Uri(""));

That way, Azure AD will allow our request to be answered by our WebAPI.


Setting up authentication and authorization can be quite a challenge, but ADAL and Azure Active Directory simplified it for us, especially since we’re targeting 3 different platforms.
Of course, we only saw the bare minimum. ADAL.NET has plenty more features to help you deliver secured and easy to use apps like token cache, refresh session, and so on.
See the ADAL.NET GitHub for more information :

Also I have made a sample on Github demonstrating everything I showed in this post :

Happy coding!

6 thoughts on “Call an Azure AD protected API in Xamarin/UWP apps

  1. Thank you so much for the tutorial. I downloaded the code from GitHub and updated it with my own Azure AD Settings as per the instructions. However once I run the xamarin application I get: HTTP 401 – Unauthorize. I can however call the Web API via the browser, login and get the json response without any problem.

    my settings:

    Would you have any insights on this issue or have you encountered before ?
    thank you

    1. Hi
      Except for the “RedirectUri” field in the Configuration.cs file, your settings seem good.
      I see that you’re using a “” Azure AD and I do remember to have a hard time with this kind of AD.

      So I gave it another try on my personal Azure AD and encountered the same error as you: Login through web and app is ok, querying the api give 401.
      I can’t find the reason why delegation doesn’t work on this kind of tenant, while it works great on my company’s Azure AD.
      Even Microsoft documentation goes through the same steps as this post.

      I’ll try to ask around and let you know if I find something.

  2. thank you so much for looking into this. Unfortunately in my case I still get the same error even after I changed it to my company’s azure active directory. Could there be that there are different versions of the tenants ? I noticed there are a few more options in the blades. For example this section to Grant permissions the rest seems to be doing what it should: yet the request fails
    the interesting thing for me is that using the browser I have no issues calling the “aip/values” I logged in, enter the URL for the aip/values and I get a valid respond

    1. I tried with the “Application ID” GUID instead of the “App ID URI” and it works now on my tenant.
      I’ll update the post to reflect this.
      Thank you very much!

      PS: I still have to figure out why it previously worked on one AD and not another. I was told it could be related to the pricing tier of the Azure AD.

  3. Timothé,

    Thanks for the great detailed post with screenshots. The tip on using the ApplicationId for the clientId and setting of the knownClientApplications in the api manifest were the missing pieces in my project. Thanks again!

Leave a Reply

Your email address will not be published. Required fields are marked *