Authenticate to Microsoft Apps on Android Devices

Created: Modified: Documentation

NOTE: This topic applies to Android devices. To configure authentication to Microsoft apps on iOS devices, see this article.

Imprivata GroundControl integrates with Microsoft for automatic sign in and sign out.

  • Automatic sign-in.
  • Automatic sign-out: Cleanly close all apps supporting the Microsoft Authentication Library (MSAL) and shared device mode.

These benefits save significant time for your workers each day, increase mobile adoption, and remove private data once no longer needed. As a secondary benefit, password management allows your organization to increase password complexity, and increase security, without creating additional burden on your staff.


There are strict requirements, which may limit when this feature may be used:

  • Microsoft’s apps must be aware of Microsoft’s Shared Device Mode. Supported apps include:
    • Microsoft Teams
    • Microsoft Outlook
    • Microsoft Edge
    • Power Apps
    • Viva Engage
  • Devices must be in Microsoft’s “shared device mode,” which typically requires touching each device to authenticate once as an Azure admin user.
Expected Behavior
  1. On device check out, users will see the standard white Check Out screen with their name. However, this screen now includes a blue button to continue to sign into Microsoft’s authentication system.

  2. Users open the Microsoft Teams app to complete the sign into Teams. When opened, Teams prompts for a login.
  3. When the device is returned to the Launchpad, GroundControl automatically signs out of Teams and the Microsoft authentication system with no prompt and no action required by the user.
Microsoft’s Shared Device Mode

Unlike most apps, Microsoft uses device-wide authentication, saving an authentication token. This way, a single sign-in can be shared among multiple apps. Similarly, a single sign-out should cause all apps in the group to be signed out. But Microsoft’s authentication system is generally optimized for 1:1 mobile devices.

To modify these behaviors for shared use, Microsoft has introduced what it calls shared device mode. Microsoft’s shared device mode modifies the Microsoft sign-in workflow to be more suitable for shared devices. In addition, apps can be built to be aware of Microsoft’s shared device mode, and can modify their behavior to be optimized for shared device workflows.

Install and Configure Microsoft Authenticator

Microsoft requires its Authenticator app to be installed to enable shared device mode.

  1. For Android devices, obtain the Authenticator app from Google Play Store and distribute it to all your shared devices.
  2. Install Microsoft Authenticator app:
    1. Open the app and skip all of the blue first user experience screens.
    2. Click the top menu and select Settings.
    3. In the Work or school accounts section, click Register your device with your organization.
    4. Type the username of the Azure Active Directory Device Administrator account.
    5. Type the password for the user and click Sign in.
    6. After the device registration process completes, the Authenticator screen displays a message about shared device mode.
  3. For the pool of shared devices, create an app configuration (AppConfig) for Microsoft Authenticator, with a single key/value pair to enable Microsoft’s shared device mode:
sharedDeviceMode      (Boolean)     true

  • Microsoft IntuneImprivata recommends that you assign the application configuration to a filtered group. The filter can be set up based on enrollmentProfileName.
  • VMware Workspace ONE (AirWatch): Change “Boolean” to another type then change it back to work around a UI bug. “True” should be uppercase.
Configure and Deploy Imprivata OneSign Profiles

Mobile apps require a profile to feed usernames and passwords from Imprivata OneSign.

Create and deploy Imprivata OneSign application profiles for the Microsoft Authenticator app and other apps on the devices, using the Imprivata Admin Console.

For more information, see Create Imprivata OneSign Profiles and Integrate Imprivata OneSign.

Sample Android Profile
<!-- Profiles for auto sign in for use with the MSAL library-->
    <app nm="" desc="Microsoft Authenticator" profileType="2" appType="0" logoutMethod="0">
        <env type="100" nm="Android">
            <scn nm="" auto="0" dgs="1">
                <!-- Controls 'nm' attributes can be different depenging on the identity provider - 
                    do not forget to replace them with the actual values-->
                <ctl nm="i0116" var="USR" />
                <ctl nm="i0118" var="PWD" />

    <!-- Microsoft apps integrated with MSAL. To enable MSAL log-out, please set the attribute 'logoutMethod' to "0". -->
    <app nm="" desc="Microsoft Teams" profileType="2" appType="0" logoutMethod="0">
        <env type="100" nm="Android">
            <scn nm="" auto="1" dgs="1">
                <ctl nm="" var="USR" />
                <ctl nm="i0118" var="PWD" />
                <!-- This control is for clickless sso - add it to fully automate the sign in process-->
                <ctl nm="" action="click" />

    <!-- Microsoft apps not integrated with MSAL -->
    <app nm="" desc="Microsoft Outlook" profileType="2" appType="0" logoutMethod="4">
        <env type="100" nm="Android">
            <scn nm="" auto="1" dgs="1">
                <ctl nm="" var="USR" />
                <ctl nm="i0118" var="PWD" />
                <ctl nm="" action="click" />
                <ctl nm="" action="click" test="SKIP" />
                <!-- Skipping User Welcome screens -->
                <ctl nm="" action="click" text="SKIP" />
                <ctl nm="" action="click" text="SKIP" />

For devices where MSAL-controlled apps and non MSAL-controlled apps are installed on the same device, verify during profile deployment whether the credentials are shared among the apps with the shared credentials store or with the domain.

For more information, see Deploy the Application Profile and Share Credentials.