Working with Multi-tenant enterprise APIs secured with Azure AD in SPFx

2 minute read

Working with Multi-tenant enterprise APIs secured with Azure AD in SPFx


There are times when we need to connect to a multi-tenant enterprise API secured with Azure Active Directory from a SharePoint Framework solution. It is a bit tricky and needs some configurations.

In this article, we will explore the configurations and details of working with Multi-tenant enterprise APIs secured with Azure AD in SPFx.

Create Azure Function App

Let’s start by creating an Azure function app.

Once the function app is ready, create a new HTTP-triggered function with the Authorization level set to Anonymous.

Secure Function App with Azure AD Authentication

We will not secure the function app with Azure AD Authentication so to access it one needs to sign in with an organization account.

  1. Navigate to the function app.
  2. From the left menu, under Settings click Authentication.
  3. Click Add identity provider.

  4. Select the Identity Provider as Microsoft.

  5. Now that when you try to access the Function URL in the browser, you should get redirected to the Azure AD login page.

Make the application multi-tenant

When the Azure function is secured with the Azure AD application, only the users from the current tenant can access it. When you want to extend the API to different tenants, change the Azure AD application to multi-tenant.

Follow the below steps to make the Azure AD application as a multi-tenant:

  1. Open the app registration from the Azure portal.
  2. From the left menu, select the Expose an API.
  3. As the Azure AD app will be used by other tenants, to ensure its uniqueness across all Azure Active Directories, update the App ID URI field.

  4. Under Authentication, make the app as a multi-tenant.

Allows users from other Azure ADs to use your application

As we want the API to be used by users from other tenants as well, we have to adjust the security settings.

  1. Open the Azure Function app.
  2. From the left menu, click Authentication.
  3. Edit the configured Identity provider.

  4. Clear the value in the Issuer Url field. This will allow users from other Azure Active Directories to authenticate against your API.
  5. Set the Allowed token audiences as function URL.

Enable CORS on Azure Function

As the function app will be called from another tenant via JavaScript running on a SharePoint page, we need to enable the CORS policy.

Consume API from SPFx

Start by creating an SPFx extension.

Add permissions to the enterprise API

Issue a permission request from the SharePoint Framework project by making the below changes to the config/package-solution.json file.

    "$schema": "",
    "solution": {
        "name": "spfx-extension-client-side-solution",
        "id": "57e2d608-d570-4317-aa47-1a32e58ba441",
        "version": "",
        "includeClientSideAssets": true,
        "skipFeatureDeployment": true,
        "isDomainIsolated": false,
        "webApiPermissionRequests": [
            "resource": "spo-caller",
            "scope": "user_impersonation"

The value of the resource property refers only to the name of the Azure AD application used to secure the API.

Use the below code:

    .then((client: AadHttpClient): void=> {

Deploy the solution

Go to the API access page and approve the API request.

You might see below error:

The requested permission isn’t valid. Reject this request and contact the developer to fix the problem and redeploy the solution.

I came across this article by Elio Struyf that explains this issue and the resolution.

In the browser type below URL<Client-id>


Consuming multi-tenant enterprise APIs secured with Azure AD in SharePoint Framework is a tricky configuration. This article explores the steps and their significance.


Leave a comment