Configure your App Service app to use Azure Active Directory sign-in
At this time, AAD V2 (including MSAL) is not supported for Azure App Services and Azure Functions. Please check back for updates.
This article shows you how to configure Azure App Services to use Azure Active Directory as an authentication provider.
- In the Azure portal, navigate to your App Service app. In the left navigation, select Authentication / Authorization.
- If Authentication / Authorization is not enabled, select On.
- Select Azure Active Directory, and then select Express under Management Mode.
- Select OK to register the App Service app in Azure Active Directory. This creates a new app registration. If you want to choose an existing app registration instead, click Select an existing app and then search for the name of a previously created app registration within your tenant. Click the app registration to select it and click OK. Then click OK on the Azure Active Directory settings page. By default, App Service provides authentication but does not restrict authorized access to your site content and APIs. You must authorize users in your app code.
- (Optional) To restrict access to your site to only users authenticated by Azure Active Directory, set Action to take when request is not authenticated to Log in with Azure Active Directory. This requires that all requests be authenticated, and all unauthenticated requests are redirected to Azure Active Directory for authentication.
- Click Save.
You can also provide configuration settings manually. This is the preferred solution if the Azure Active Directory tenant you wish to use is different from the tenant with which you sign into Azure. To complete the configuration, you must first create a registration in Azure Active Directory, and then you must provide some of the registration details to App Service.
Sign in to the Azure portal, and navigate to your App Service app. Copy your app URL. You will use this to configure your Azure Active Directory app registration.
Navigate to Active Directory, then select the App registrations, then click New application registration at the top to start a new app registration.
In the Create page, enter a Name for your app registration, select the Web App / API type, in the Sign-on URL box paste the application URL (from step 1). Then click to Create.
In a few seconds, you should see the new app registration you just created.
Once the app registration has been added, click on the app registration name, click on Settings at the top, then click on Properties
In the App ID URI box, paste in the Application URL (from step 1), also in the Home Page URL paste in the Application URL (from step 1) as well, then click Save
Now click on the Reply URLs, edit the Reply URL, paste in the Application URL (from step 1), then append it to the end of the URL, /.auth/login/aad/callback (For example,
https://contoso.azurewebsites.net/.auth/login/aad/callback). Click Save.
You can use the same app registration for multiple domains by adding additional Reply URLs. Make sure to model each App Service instance with its own registration, so it has its own permissions and consent. Also consider using separate app registrations for separate site slots. This is to avoid permissions being shared between environments, so that a bug in new code you are testing does not affect production.
At this point, copy the Application ID for the app. Keep it for later use. You will need it to configure your App Service app.
Close the Registered app page. On the App registrations page, click on the Endpoints button at the top, then copy the WS-FEDERATION SIGN-ON ENDPOINT URL but remove the
/wsfedending from the URL. The end result should look like
https://login.microsoftonline.com/00000000-0000-0000-0000-000000000000. The domain name may be different for a sovereign cloud. This will serve as the Issuer URL for later.
Back in the Azure portal, navigate to your App Service app. Click Authentication/Authorization. If the Authentication/Authorization feature is not enabled, turn the switch to On. Click on Azure Active Directory, under Authentication Providers, to configure your app.
(Optional) By default, App Service provides authentication but does not restrict authorized access to your site content and APIs. You must authorize users in your app code. Set Action to take when request is not authenticated to Log in with Azure Active Directory. This option requires that all requests be authenticated, and all unauthenticated requests are redirected to Azure Active Directory for authentication.
In the Active Directory Authentication configuration, click Advanced under Management Mode. Paste the Application ID into the Client ID box (from step 8) and paste in the URL (from step 9) into the Issuer URL value. Then click OK.
On the Active Directory Authentication configuration page, click Save.
You are now ready to use Azure Active Directory for authentication in your App Service app.
Configure a native client application
You can register native clients, which provides greater control over permissions mapping. You need this if you wish to perform sign-ins using a client library such as the Active Directory Authentication Library.
- Navigate to Azure Active Directory in the Azure portal.
- In the left navigation, select App registrations. Click New app registration at the top.
- In the Create page, enter a Name for your app registration. Select Native in Application type.
- In the Redirect URI box, enter your site's /.auth/login/done endpoint, using the HTTPS scheme. This value should be similar to https://contoso.azurewebsites.net/.auth/login/done. If creating a Windows application, instead use the package SID as the URI.
- Click Create.
- Once the app registration has been added, select it to open it. Find the Application ID and make a note of this value.
- Click All settings > Required permissions > Add > Select an API.
- Type the name of the App Service app that you registered earlier to search for it, then select it and click Select.
- Select Access <app_name>. Then click Select. Then click Done.
You have now configured a native client application that can access your App Service app.
Send feedback about: