Scenario: Mobile application that calls web APIs

Learn how to build a mobile app that calls web APIs.

Getting started

If you haven't already, create your first application by completing a quickstart:


A personalized, seamless user experience is essential for mobile apps. The Microsoft identity platform enables mobile developers to create that experience for iOS and Android users. Your application can sign in Microsoft Entra users, personal Microsoft account users, and Azure AD B2C users. It can also acquire tokens to call a web API on their behalf. To implement these flows, we'll use the Microsoft Authentication Library (MSAL). MSAL implements the industry standard OAuth2.0 authorization code flow.

Daemon apps

Considerations for mobile apps:

  • User experience is key: Allow users to see the value of your app before you ask for sign-in. Request only the required permissions.
  • Support all user configurations: Many mobile business users must adhere to conditional-access policies and device-compliance policies. Be sure to support these key scenarios.
  • Implement single sign-on (SSO): By using MSAL and Microsoft identity platform, you can enable SSO through the device's browser or Microsoft Authenticator (and Intune Company Portal on Android).
  • Implement shared device mode: Enable your application to be used in shared-device scenarios, for example hospitals, manufacturing, retail, and finance. Read more about supporting shared device mode.


Keep in mind the following considerations when you build a mobile app on Microsoft identity platform:

  • Depending on the platform, some user interaction might be required the first time that users sign in. For example, iOS requires apps to show user interaction when they use SSO for the first time through Microsoft Authenticator (and Intune Company Portal on Android).
  • On iOS and Android, MSAL might use an external browser to sign in users. The external browser might appear on top of your app.
  • Never use a secret in a mobile application. In these applications, secrets are accessible to all users.

If you're new to identity and access management (IAM) with OAuth 2.0 and OpenID Connect, or even just new to IAM on the Microsoft identity platform, the following set of articles should be high on your reading list.

Although not required reading before completing your first quickstart or tutorial, they cover topics integral to the platform, and familiarity with them will help you on your path as you build more complex scenarios.

Authentication and authorization

Next steps

Move on to the next article in this scenario, App registration.