Run automated integration tests

As a developer, you want to run automated integration tests on the apps you develop. Calling your API protected by Microsoft identity platform (or other protected APIs such as Microsoft Graph) in automated integration tests is a challenge. Azure AD often requires an interactive user sign-in prompt, which is difficult to automate. This article describes how you can use a non-interactive flow, called Resource Owner Password Credential Grant (ROPC), to automatically sign in users for testing.

To prepare for your automated integration tests, create some test users, create and configure an app registration, and potentially make some configuration changes to your tenant. Some of these steps require admin privileges. Also, Microsoft recommends that you do not use the ROPC flow in a production environment. Create a separate test tenant that you are an administrator of so you can safely and effectively run your automated integration tests.


Microsoft recommends you do not use the ROPC flow in a production environment. In most production scenarios, more secure alternatives are available and recommended. The ROPC flow requires a very high degree of trust in the application, and carries risks which are not present in other authentication flows. You should only use this flow for testing purposes in a separate test tenant, and only with test users.


  • The Microsoft identity platform only supports ROPC within Azure AD tenants, not personal accounts. This means that you must use a tenant-specific endpoint ({TenantId_or_Name}) or the organizations endpoint.
  • Personal accounts that are invited to an Azure AD tenant can't use ROPC.
  • Accounts that don't have passwords can't sign in with ROPC, which means features like SMS sign-in, FIDO, and the Authenticator app won't work with that flow.
  • If users need to use multi-factor authentication (MFA) to log in to the application, they will be blocked instead.
  • ROPC is not supported in hybrid identity federation scenarios (for example, Azure AD and Active Directory Federation Services (AD FS) used to authenticate on-premises accounts). If users are full-page redirected to an on-premises identity provider, Azure AD is not able to test the username and password against that identity provider. Pass-through authentication is supported with ROPC, however.
  • An exception to a hybrid identity federation scenario would be the following: Home Realm Discovery policy with AllowCloudPasswordValidation set to TRUE will enable ROPC flow to work for federated users when on-premises password is synced to cloud. For more information, see Enable direct ROPC authentication of federated users for legacy applications.

Create a separate test tenant

Using the ROPC authentication flow is risky in a production environment, so create a separate tenant to test your applications. You can use an existing test tenant, but you need to be an admin in the tenant since some of the following steps require admin privileges.

Create and configure a key vault

We recommend you securely store the test usernames and passwords as secrets in Azure Key Vault. When you run the tests later, the tests run in the context of a security principal. The security principal is an Azure AD user if you're running tests locally (for example, in Visual Studio or Visual Studio Code), or a service principal or managed identity if you're running tests in Azure Pipelines or another Azure resource. The security principal must have Read and List secrets permissions so the test runner can get the test usernames and passwords from your key vault. For more information, read Authentication in Azure Key Vault.

  1. Create a new key vault if you don't have one already.
  2. Take note of the Vault URI property value (similar to https://<your-unique-keyvault-name> which is used in the example test later in this article.
  3. Assign an access policy for the security principal running the tests. Grant the user, service principal, or managed identity Get and List secrets permissions in the key vault.

Create test users

Create some test users in your tenant for testing. Since the test users are not actual humans, we recommend you assign complex passwords and securely store these passwords as secrets in Azure Key Vault.

  1. In the Azure portal, select Azure Active Directory.
  2. Go to Users.
  3. Select New user and create one or more test user accounts in your directory.
  4. The example test later in this article uses a single test user. Add the test username and password as secrets in the key vault you created previously. Add the username as a secret named "TestUserName" and the password as a secret named "TestPassword".

Create and configure an app registration

Register an application that acts as your client app when calling APIs during testing. This should not be the same application you may already have in production. You should have a separate app to use only for testing purposes.

Register an application

Create an app registration. You can follow the steps in the app registration quickstart. You don't need to add a redirect URI or add credentials, so you can skip those sections.

Take note of the Application (client) ID, which is used in the example test later in this article.

Enable your app for public client flows

ROPC is a public client flow, so you need to enable your app for public client flows. From your app registration in the Azure portal, go to Authentication > Advanced settings > Allow public client flows. Set the toggle to Yes.

Since ROPC is not an interactive flow, you won't be prompted with a consent screen to consent to these at runtime. Pre-consent to the permissions to avoid errors when acquiring tokens.

Add the permissions to your app. Do not add any sensitive or high-privilege permissions to the app, we recommend you scope your testing scenarios to basic integration scenarios around integrating with Azure AD.

From your app registration in the Azure portal, go to API Permissions > Add a permission. Add the permissions you need to call the APIs you'll be using. A test example further in this article uses the and permissions.

Once the permissions are added, you'll need to consent to them. The way you consent to the permissions depends on if your test app is in the same tenant as the app registration and whether you're an admin in the tenant.

App and app registration are in the same tenant and you're an admin

If you plan on testing your app in the same tenant you registered it in and you are an administrator in that tenant, you can consent to the permissions from the Azure portal. In your app registration in the Azure portal, go to API Permissions and select the Grant admin consent for <your_tenant_name> button next to the Add a permission button and then Yes to confirm.

App and app registration are in different tenants, or you're not an admin

If you do not plan on testing your app in the same tenant you registered it in, or you are not an administrator in your tenant, you cannot consent to the permissions from the Azure portal. You can still consent to some permissions, however, by triggering a sign-in prompt in a web browser.

In your app registration in the Azure portal, go to Authentication > Platform configurations > Add a platform > Web. Add the redirect URI "https://localhost" and select Configure.

There is no way for non-admin users to pre-consent through the Azure portal, so send the following request in a browser. When you are prompted with the login screen, sign in with a test account you created in a previous step. Consent to the permissions you are prompted with. You may need to repeat this step for each API you want to call and test user you want to use.

// Line breaks for legibility only{tenant}/oauth2/v2.0/authorize?

Replace {tenant} with your tenant ID, {your_client_ID} with the client ID of your application, and {resource_you_want_to_call} with the identifier URI (for example, "") or app ID of the API you are trying to access.

Exclude test apps and users from your MFA policy

Your tenant likely has a conditional access policy that requires multifactor authentication (MFA) for all users, as recommended by Microsoft. MFA won't work with ROPC, so you'll need to exempt your test applications and test users from this requirement.

To exclude user accounts:

  1. Navigate to the Azure portal and sign in to your tenant. Select Azure Active Directory. Select Security in the left navigation pane and then select Conditional Access.
  2. In Policies, select the conditional access policy that requires MFA.
  3. Select Users or workload identities.
  4. Select the Exclude tab and then the Users and groups checkbox.
  5. Select the user account(s) to exclude in Select excluded users.
  6. Select the Select button and then Save.

To exclude a test application:

  1. In Policies, select the conditional access policy that requires MFA.
  2. Select Cloud apps or actions.
  3. Select the Exclude tab and then Select excluded cloud apps.
  4. Select the app(s) you want to exclude in Select excluded cloud apps.
  5. Select the Select button and then Save.

Write your application tests

Now that you're set up, you can write your automated tests. The following .NET example code uses Microsoft Authentication Library (MSAL) and xUnit, a common testing framework.

Set up your appsettings.json file

Add the client ID of the test app you previously created, the necessary scopes, and the key vault URI to the appsettings.json file of your test project.

  "Authentication": {
    "AzureCloudInstance": "AzurePublic", //Will be different for different Azure clouds, like US Gov
    "AadAuthorityAudience": "AzureAdMultipleOrgs",
    "ClientId": <your_client_ID>

  "WebAPI": {
    "Scopes": [
      //For this Microsoft Graph example.  Your value(s) will be different depending on the API you're calling
      //For this Microsoft Graph example.  Your value(s) will be different depending on the API you're calling

  "KeyVault": {
    "KeyVaultUri": "https://<your-unique-keyvault-name>"

Set up your client for use across all your test classes

Use SecretClient() to get the test username and password secrets from Azure Key Vault. The code uses exponential back-off for retries in case Key Vault is being throttled.

DefaultAzureCredential() authenticates with Azure Key Vault by getting an access token from a service principal configured by environment variables or a managed identity (if the code is running on an Azure resource with a managed identity). If the code is running locally, DefaultAzureCredential uses the local user's credentials. Read more in the Azure Identity client library content.

Use Microsoft Authentication Library (MSAL) to authenticate using the ROPC flow and get an access token. The access token is passed along as a bearer token in the HTTP request.

using Xunit;
using System.Threading.Tasks;
using Microsoft.Identity.Client;
using System.Security;
using System.Net;
using System.Net.Http;
using System.Net.Http.Headers;
using Microsoft.Extensions.Configuration;
using Azure.Identity;
using Azure.Security.KeyVault.Secrets;
using Azure.Core;
using System;

public class ClientFixture : IAsyncLifetime
    public HttpClient httpClient;

    public async Task InitializeAsync()
        var builder = new ConfigurationBuilder().AddJsonFile("<path-to-json-file>");

        IConfigurationRoot Configuration = builder.Build();

        var PublicClientApplicationOptions = new PublicClientApplicationOptions();
        Configuration.Bind("Authentication", PublicClientApplicationOptions);
        var app = PublicClientApplicationBuilder.CreateWithApplicationOptions(PublicClientApplicationOptions)

        SecretClientOptions options = new SecretClientOptions()
            Retry =
                    Delay= TimeSpan.FromSeconds(2),
                    MaxDelay = TimeSpan.FromSeconds(16),
                    MaxRetries = 5,
                    Mode = RetryMode.Exponential

        string keyVaultUri = Configuration.GetValue<string>("KeyVault:KeyVaultUri");
        var client = new SecretClient(new Uri(keyVaultUri), new DefaultAzureCredential(), options);

        KeyVaultSecret userNameSecret = client.GetSecret("TestUserName");
        KeyVaultSecret passwordSecret = client.GetSecret("TestPassword");

        string password = passwordSecret.Value;
        string username = userNameSecret.Value;
        string[] scopes = Configuration.GetSection("WebAPI:Scopes").Get<string[]>();
        SecureString securePassword = new NetworkCredential("", password).SecurePassword;

        AuthenticationResult result = null;
        httpClient = new HttpClient();

            result = await app.AcquireTokenByUsernamePassword(scopes, username, securePassword)
        catch (MsalException) { }

        string accessToken = result.AccessToken;
        httpClient.DefaultRequestHeaders.Authorization = new AuthenticationHeaderValue("bearer", accessToken);

    public Task DisposeAsync() => Task.CompletedTask;

Use in your test classes

The following example is a test that calls Microsoft Graph. Replace this test with whatever you'd like to test on your own application or API.

public class ApiTests : IClassFixture<ClientFixture>
    ClientFixture clientFixture;

    public ApiTests(ClientFixture clientFixture)
        this.clientFixture = clientFixture;

    public async Task GetRequestTest()
        var testClient = clientFixture.httpClient;
        HttpResponseMessage response = await testClient.GetAsync("");
        var responseCode = response.StatusCode.ToString();
        Assert.Equal("OK", responseCode);