Set up a shared iPad

Get one iPad working, start to finish.

This page takes a blank enrolled iPad to a working shared device with Microsoft sign-in, the default for most teams. By the end, a person can walk up, tap their badge, reach the home screen, and open Teams or Outlook without a second login.

Most teams connect Microsoft sign-in so Teams, Outlook, and My Apps open as the same person, and it’s included in the steps below. If your users never open Microsoft apps, skip the steps marked Microsoft and leave the use_msal and azure_client_id lines out of the payload in Step 4.

Before you start

  • The iPad runs iPadOS 17 or later and is already enrolled in Microsoft Intune (supervised recommended).
  • IDmelon Authenticator is in your Intune app catalog.
  • You can sign in to the IDmelon Admin Panel and Microsoft Intune — or you can ask someone who can.
  • For Microsoft sign-in: you can also sign in to Microsoft Entra, and Microsoft Authenticator is in your Intune app catalog.

Step 1 — Create your Shared Mobile API key

The Shared Mobile API key is what makes the app a shared device; there’s no separate “shared mode” switch to flip.

  1. Open the IDmelon Admin Panel.
  2. Go to Authentication > API Key Management.
  3. Click + New API Key.
  4. Name it something you’ll recognize, like Shared iPads.
  5. Set Type to Shared Mobile.
  6. Create the key and copy it somewhere safe.

For more detail, see API Key Management.

Step 2 — Microsoft — Register the iPad app in Microsoft Entra

(skip if your team doesn’t use Microsoft apps)

This tells Microsoft to trust sign-ins coming from IDmelon on the iPad.

  1. Open Microsoft Entra and go to App registrations > New registration.
  2. Give it a name you’ll recognize, like IDmelon Shared iPad.
  3. Under Redirect URI, choose Mobile and desktop applications and enter: msauth.com.idmelon.idmelon-2://auth
  4. Register the app.
  5. Open API permissions, add the Microsoft Graph delegated permission User.Read, then Grant admin consent if your tenant requires it.
  6. On the app’s Overview, copy the Application (client) ID and keep it for Step 4.

Copying the client ID from the Entra app registration

Use the ID from your own app registration. Don’t copy the one in the screenshot.

Step 3 — Add the apps in Intune

  1. Sign in to Microsoft Intune.
  2. Go to Apps > iOS/iPadOS and add IDmelon Authenticator as an iOS store app.
  3. Microsoft: add Microsoft Authenticator the same way. Microsoft sign-in runs through it, so it must be on the device. (Skip it only if your team doesn’t use Microsoft apps.)
  4. Assign both apps to the device group that holds your shared iPads.

Adding IDmelon Authenticator in Intune

Step 4 — Push the settings

Now send the app its settings as a managed app configuration.

  1. In Intune, go to Apps > Configuration > Create > Managed devices.
  2. Set Platform to iOS/iPadOS and select IDmelon Authenticator as the target app.
  3. Set Configuration settings format to Enter XML data.
  4. Paste the payload below.
  5. Set api_key to the key from Step 1, and set azure_client_id to the Application (client) ID from Step 2.
  6. Assign the policy to the same device group, then review and create.
<dict>
  <key>api_key</key>
  <string>YOUR_SHARED_MOBILE_API_KEY</string>
  <key>shared_login_method</key>
  <dict>
    <key>type</key>
    <string>badge</string>
    <key>model</key>
    <string>hub</string>
  </dict>
  <key>use_msal</key>
  <true/>
  <key>azure_client_id</key>
  <string>YOUR_APPLICATION_CLIENT_ID</string>
</dict>

Change only the highlighted values — leave every other line exactly as it is.

Sign-in defaults to badge. To use face or another method, see Login methods.

Not using Microsoft apps? Remove the use_msal and azure_client_id lines; keep api_key and shared_login_method.

Running IDmelon on-premise? You’ll also add base_api_url. See Configuration keys.

Step 5 — Microsoft — Create the SSO extension profiles in Intune

(skip if your team doesn’t use Microsoft apps)

Single sign-on lets a signed-in session pass between apps, so users don’t authenticate again in each one. Create two Device features profiles — one for Microsoft, one for IDmelon. Both are device configuration profiles (not app configurations), and both go to your shared-iPad device group.

Microsoft Entra SSO extension

  1. Go to Devices > Configuration > Create > New policy.
  2. Set Platform to iOS/iPadOS and Profile type to Templates > Device features.
  3. Open Single sign-on app extension and set:
    • SSO app extension type: Microsoft Entra ID
    • Enable shared device mode: Yes
  4. Under App bundle IDs, add the apps that share the sign-in. These are common examples — add any other Microsoft apps your team uses:
    • com.microsoft.skype.teams
    • com.microsoft.Office.Outlook
    • com.microsoft.azureauthenticator
    • com.apple.mobilesafari
  5. Under Additional configuration, add:
    • browser_sso_interaction_enabled (Integer) = 1
    • disable_explicit_app_prompt (Integer) = 1
    • AppPrefixAllowList (String) = com.apple.,com.microsoft.,com.idmelon.
    • device_registration (String) = {{DEVICEREGISTRATION}}
  6. Assign the profile to your shared-iPad device group, then review and create.

IDmelon SSO extension

Create a second Device features profile for IDmelon.

  1. Go to Devices > Configuration > Create > New policy, iOS/iPadOS, then Templates > Device features.
  2. Open Single sign-on app extension and set:
    • SSO app extension type: Redirect
    • Extension ID: com.idmelon.idmelon-2.ssoextension
    • Team ID: 4A6ZQ29Y2F
  3. Under URLs, add:
    • https://panel.idmelon.com/auth/sign-in
  4. Assign the profile to your shared-iPad device group, then review and create.

Step 6 — Microsoft — Set Microsoft Authenticator to shared device mode

(skip if your team doesn’t use Microsoft apps)

You added Microsoft Authenticator in Step 3. Now switch it to shared device mode with its own app configuration.

  1. Go to Apps > Configuration > Create > Managed devices.
  2. Set Platform to iOS/iPadOS and target Microsoft Authenticator.
  3. Add one configuration key: sharedDeviceMode (Boolean) = true.
  4. Assign it to your shared-iPad device group, then review and create.

This goes on Microsoft Authenticator, not IDmelon Authenticator. They are two separate apps with two separate configurations.

Step 7 — Test on the iPad

  1. Open IDmelon Authenticator on a synced iPad and confirm it opens into shared mode.
  2. Tap your badge to sign in and reach the home screen.
  3. Microsoft: open Teams or Outlook and confirm it opens as you, with no second password prompt.

IDmelon Authenticator on the shared iPad Signed in to the shared iPad Microsoft sign-in prompt on the shared iPad

What’s next

See User Experience for what a healthy device looks like day to day. If something didn’t work, see Troubleshooting.