Configure your App Service or Azure Functions app to use Microsoft Account login
This topic shows you how to configure Azure App Service or Azure Functions to use AAD to support personal Microsoft account logins.
Both personal Microsoft accounts and organizational accounts use the AAD identity provider. At this time, is not possible to configure this identity provider to support both types of log-ins.
Go to App registrations in the Azure portal. If needed, sign in with your Microsoft account.
Select New registration, then enter an application name.
Under Supported account types, select Accounts in any organizational directory (Any Azure AD directory - Multitenant) and personal Microsoft accounts (e.g. Skype, Xbox)
In Redirect URIs, select Web, and then enter
https://<app-domain-name>/.auth/login/aad/callback. Replace <app-domain-name> with the domain name of your app. For example,
https://contoso.azurewebsites.net/.auth/login/aad/callback. Be sure to use the HTTPS scheme in the URL.
Copy the Application (Client) ID. You'll need it later.
From the left pane, select Certificates & secrets > New client secret. Enter a description, select the validity duration, and select Add.
Copy the value that appears on the Certificates & secrets page. After you leave the page, it won't be displayed again.
The client secret value (password) is an important security credential. Do not share the password with anyone or distribute it within a client application.
Go to your application in the Azure portal.
Select Settings > Authentication / Authorization, and make sure that App Service Authentication is On.
Under Authentication Providers, select Azure Active Directory. Select Advanced under Management mode. Paste in the Application (client) ID and client secret that you obtained earlier. Use
https://login.microsoftonline.com/9188040d-6c67-4c5b-b112-36a304b66dad/v2.0for the Issuer Url field.
App Service provides authentication, but doesn't restrict authorized access to your site content and APIs. You must authorize users in your app code.
(Optional) To restrict access to Microsoft account users, set Action to take when request is not authenticated to Log in with Azure Active Directory. When you set this functionality, your app requires all requests to be authenticated. It also redirects all unauthenticated requests to use AAD for authentication. Note that because you have configured your Issuer Url to use the Microsoft Account tenant, only personal acccounts will successfully authenticate.
Restricting access in this way applies to all calls to your app, which might not be desirable for apps that have a publicly available home page, as in many single-page applications. For such applications, Allow anonymous requests (no action) might be preferred so that the app manually starts authentication itself. For more information, see Authentication flow.
You are now ready to use Microsoft Account for authentication in your app.
- App Service Authentication / Authorization overview.
- Advanced usage of authentication and authorization in Azure App Service
- Tutorial: Authenticate and authorize users end-to-end in Azure App Service
- Add authentication to your Mobile App: iOS, Android, Windows Universal, Xamarin.Android, Xamarin.iOS, Xamarin.Forms, Cordova.