> ## Documentation Index
> Fetch the complete documentation index at: https://docs.incident.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Microsoft Intune on mobile

> Apply Intune app protection policies to the incident.io mobile app on managed and personal devices alike.

The incident.io mobile app supports Microsoft Intune Mobile Application Management (MAM), so your organization can enforce app protection policies on the incident.io app without requiring full device enrollment (MDM).

This lets you protect corporate data on both company-owned and personal (BYOD) devices by controlling actions like copy and paste, screenshots, and selective wipe, all scoped to the incident.io app.

> [!NOTE]
>
> Microsoft Intune on mobile is available on the Enterprise plan, and requires version 1.15.10 or later of the
> incident.io app on iOS and Android.

## How it works

When Intune is enabled for your organization:

1. Users log into incident.io normally (SSO, email, etc.)
2. The app detects that your organization requires Intune and asks them to sign in with their Microsoft work account
3. incident.io checks that the account belongs to your linked Microsoft Entra tenant and matches their incident.io email
4. The app registers with Intune and your app protection policies are applied. Intune may restart the app the first time a policy applies.

After that, your policies are enforced inside the incident.io app, for example blocking screenshots or restricting data transfer, without managing the whole device.

incident.io links your organization to a single Entra tenant. That link is how we know which Microsoft accounts are yours, so connecting it is the first step in setup.

## What Intune sign-in proves

When Intune is on, incident.io accepts a mobile sign-in only after the person also signs in with a Microsoft work account that:

* Is a member, not a guest, of your linked Microsoft Entra tenant
* Has the same email as their incident.io account

This proves the person has a valid Microsoft identity in your tenant. To also prove the sign-in came from the incident.io app that Intune protects, add a Conditional Access policy in Microsoft Entra for the incident.io app on iOS and Android, with its grant set to **Require app protection policy** ([step 5](#setting-up-intune)). Entra then refuses sign-ins from unmanaged apps on iOS and Android, so people can sign in only from the incident.io app your app protection policy covers. Without that policy, Entra can issue a sign-in for the incident.io app to an app that Intune doesn't manage.

We recommend step 5 for every organization that turns on Intune.

## Prerequisites

* The **Manage security settings** permission in incident.io
* A Microsoft Entra ID tenant with Intune licenses, plus admin access to the Microsoft Entra admin center and the Microsoft Intune admin center
* An app protection policy in Intune for iOS/iPadOS, Android, or both
* On Android, the Intune Company Portal app installed on each device. Intune requires it to apply app protection policies on Android.
* Everyone's incident.io email must match the email on their Microsoft work account
* For Conditional Access (step 5), a Microsoft Entra ID P1 license or higher
* For Conditional Access on iOS, Microsoft Authenticator installed on each device. Entra checks app protection through Authenticator on iOS, and through Intune Company Portal on Android.

## Setting up Intune

**1. Connect Microsoft Entra**

Navigate to [Settings → Security](https://app.incident.io/~/settings/security) and find **Microsoft Intune on mobile**. Click **Connect Microsoft Entra**, confirm your company's email domain, then sign in with your Microsoft work account. incident.io links your organization to the tenant you signed in to.

For the link to succeed:

* Your Microsoft account email must match your incident.io email
* Your account must be a member of the tenant, not a guest
* The tenant must have verified the domain you entered
* The tenant can't already be linked to another incident.io organization

> [!WARNING]
>
> Connecting Microsoft Entra is one-way. Intune sign-ins and Microsoft Teams both depend on the linked tenant, so you can't remove or change it from the dashboard. Contact support if you need to.

If your organization uses incident.io with Microsoft Teams, your tenant is already linked and you can skip this step.

**2. Enable Intune in incident.io**

Still in [Settings → Security](https://app.incident.io/~/settings/security), enable **Microsoft Intune on mobile**.

Once enabled, incident.io activates the Intune enrollment gate in the mobile app. The next time each user logs in, they are asked to register the app with Intune before they can continue. People who are already signed in are not interrupted until then.

**3. Grant admin consent for the incident.io app registration**

The incident.io mobile app uses a Microsoft Entra ID app registration to sign people in and to enroll with the Intune MAM service. A tenant admin needs to grant consent for it.

**incident.io app registration:**

* **Client ID:** `68ac5791-0672-47f9-a1e1-f2ef2b656f61`
* **App name:** incident.io

**1. Open Enterprise applications in Entra ID**

In the [Microsoft Entra admin center](https://entra.microsoft.com), go to **Identity → Applications → Enterprise applications**.

**2. Search for the incident.io app**

Search for the incident.io client ID: `68ac5791-0672-47f9-a1e1-f2ef2b656f61`.

If it doesn't appear, grant admin consent first (next step). Consenting is what adds the app to your tenant.

**3. Grant tenant-wide admin consent**

Open this URL in your browser, replacing `{TENANT_ID}` with your Entra tenant ID:

```text theme={null}
https://login.microsoftonline.com/{TENANT_ID}/adminconsent?client_id=68ac5791-0672-47f9-a1e1-f2ef2b656f61
```

Sign in as a Global Administrator or Application Administrator and accept the requested permissions.

![Microsoft permissions requested dialog for the incident.io app](https://mintcdn.com/incidentio-18bb4170/HebcvnboKE3k7I9s/images/help-centre/microsoft-intune/admin-consent.png?fit=max\&auto=format\&n=HebcvnboKE3k7I9s\&q=85\&s=d9023942184f084b93a8568debdf6b95)

**4. Verify permissions**

Back in **Enterprise applications → incident.io → Permissions**, check that both of these are granted:

* **Microsoft Graph:** `User.Read` (Sign in and read user profile)
* **Microsoft Mobile Application Management:** Read and Write the User's App Management data

Both should show a status of **Granted for \[your tenant]**. The consent screen also lists **Create chats** and **Read organizational branding information**. The same app registration powers the incident.io Microsoft Teams integration, which uses those.

> [!WARNING]
>
> Don't skip this step. Without admin consent for the Microsoft Mobile Application Management resource, the Intune SDK can't get the token it needs to enroll the app, and people see **Couldn't set up app protection** when they try to register.

**4. Add incident.io to your app protection policy**

In the Microsoft Intune admin center, go to **Apps → App protection policies** and open the policy you want to apply, or create one. Under **Apps**, add incident.io as a custom app:

| Platform | Bundle ID or package name |
| - | - |
| iOS/iPadOS | `com.incidentio.incidentio` |
| Android | `com.incidentio.incidentio` |

Under **Assignments**, include the groups whose members use incident.io. A policy applies only when both the app and the person are targeted.

> [!WARNING]
>
> In the policy's **Data protection** settings, keep **Org data notifications** set to **Allow**. incident.io pages
> responders through push notifications, so don't block them.

Policy changes can take a few hours to reach devices. People can force a sync from the Company Portal app.

**5. Require app protection with Conditional Access**

Do this step after step 4, so a policy already covers the incident.io app when Entra starts to enforce it.

In the [Microsoft Entra admin center](https://entra.microsoft.com), go to **Protection → Conditional Access → Policies** and create a new policy with these settings:

| Setting | Value |
| - | - |
| Users | Include the groups your app protection policy is assigned to. Exclude your emergency access accounts. |
| Target resources | The incident.io app (client ID `68ac5791-0672-47f9-a1e1-f2ef2b656f61`), which appears after admin consent (step 3) |
| Conditions → Device platforms | Android and iOS only |
| Conditions → Client apps | Mobile apps and desktop clients only |
| Grant | Grant access, with Require app protection policy |
| Enable policy | Report-only |

Ask a few people to sign in on mobile, then check **Monitoring → Sign-in logs** for the incident.io app. When the policy reports success, set **Enable policy** to **On**.

> [!WARNING]
>
> Leave Browser unselected under Client apps. Microsoft sign-in to the incident.io dashboard uses a browser, and so does Sign in with Microsoft in the mobile app. Including Browser would block both.

If you already have a policy that requires app protection for all resources, it covers incident.io too. It must exclude these Microsoft services, which the incident.io app uses to register with Intune. Otherwise the policy blocks the registration that would satisfy it.

| Resource | App ID |
| - | - |
| Microsoft Intune | `0000000a-0000-0000-c000-000000000000` |
| Microsoft Intune Enrollment | `d4ebce55-015a-49b5-a083-c84d1797ae8c` |
| Microsoft Mobile Application Management | `0a5f63c0-b750-4f38-a71c-4fc0d58b89e2` |

Add all three under **Target resources → Exclude**.

Once the policy is on, Entra refuses incident.io sign-ins from any app on iOS or Android that your app protection policy doesn't cover. In the incident.io app, people see the same **Continue with Microsoft** step as before.

> [!NOTE]
>
> The incident.io app in Entra also handles Microsoft sign-in to the dashboard and the Microsoft Teams integration. A policy limited to iOS, Android, and mobile apps doesn't affect either.

## Signing in on mobile

Here's what your team sees once Intune is on:

1. Sign in to the incident.io app as usual, with Slack, Microsoft, SAML, or an email code
2. The app shows **App protection required**. Tap **Continue with Microsoft** and sign in with the Microsoft work account that shares your incident.io email. If Microsoft Authenticator is installed, the sign-in goes through it.
3. The app registers with Intune. Intune may ask to restart the app the first time a policy applies.

On later launches the app opens straight to the home screen. Signing out deregisters the app from Intune and removes Intune-protected incident.io data from the device.

## What changes when Intune is on

* **Sign in on mobile via QR code** is unavailable.
* [Mobile access restrictions](https://docs.incident.io/admin/mobile-access-restrictions.md) is replaced. Your Intune policies protect sensitive information instead of redaction, and the mobile app always signs in through your primary SAML connection.
* If you enforce [SAML SSO](https://docs.incident.io/admin/saml-sso.md), it still applies. Intune adds a requirement rather than replacing one.
* Turning Intune on or off, and linking your Entra tenant, are recorded in [audit logs](https://docs.incident.io/admin/audit-logs.md).

## Troubleshooting

Most problems show up when a responder taps **Continue with Microsoft**. Fix the cause, then have them tap **Try again**.

| What the responder sees | What to do |
| - | - |
| **Couldn't set up app protection** with no other detail | The Microsoft sign-in or Intune registration failed. Check admin consent (step 3), the responder's Intune license, and their policy assignment, in that order. |
| `NOT_LICENSED`, or a message that the account isn't licensed | The account has no Intune license, or Intune couldn't reach its licensing service. Assign an Intune license in Microsoft Entra and wait a few minutes for it to apply. |
| `AUTHORIZATION_NEEDED`, or Microsoft's **Need admin approval** page | Your tenant hasn't consented to the **Microsoft Mobile Application Management** permission. Grant tenant-wide admin consent (step 3). |
| A message that the account is licensed but not targeted | No app protection policy applies to this responder. Add them to a group the policy is assigned to, and confirm the policy targets `com.incidentio.incidentio`. |
| `COMPANY_PORTAL_REQUIRED` | Android only. Intune needs the Company Portal app on the device to apply policies. Install Intune Company Portal from Google Play. No sign-in to it is needed. |
| **That Microsoft account has a different email from the one you signed in to incident.io with** | The account used for Intune is different from the one they signed in to incident.io with. Tap **Sign in again** and choose the member account with the matching email. |
| **Your sign-in expired while Microsoft Intune was setting up app protection** | Too much time passed between signing in to incident.io and finishing the Microsoft step. Tap **Sign in again** and complete the Microsoft step straight away. |
| A Microsoft page that says the app must be protected by Intune, or that asks for a broker app | Conditional Access (step 5) needs a broker app on the device. Install Microsoft Authenticator on iOS or Intune Company Portal on Android, then tap **Try again**. |
| **Couldn't set up app protection** after you turn on a Conditional Access policy for **All resources** | The policy also requires app protection for the Microsoft services that Intune registration uses. Exclude Microsoft Intune, Microsoft Intune Enrollment, and Microsoft Mobile Application Management from the policy (step 5). |
| **Sign in with Microsoft** fails in a phone browser after you turn on Conditional Access | The policy includes **Browser**. Edit the policy so **Client apps** is **Mobile apps and desktop clients** only. |
| Registration succeeded but policies aren't applying | The policy hasn't reached the device yet, or registration didn't complete. Wait for sync or force one from Company Portal. If the app isn't listed under **Apps → Monitor → App protection status**, sign out and back in. |

## FAQs

> [accordion] Do devices need to be enrolled in Intune (MDM)?
>
> No. Intune on mobile uses app protection policies (MAM), so it works on personal devices as well as MDM-enrolled
> ones. Full device enrollment through Company Portal isn't required.

> [accordion] Does Intune on mobile make sure only the Intune-protected app can sign in?
>
> Intune sign-in proves each person has a valid Microsoft identity in your tenant, with the same email as their
> incident.io account. To also require the Intune-protected app, add the Conditional Access policy in step 5. Entra
> then refuses sign-ins from unmanaged apps on iOS and Android.

> [accordion] Will my app protection policy stop responders being paged?
>
> No. Pages reach responders as push notifications, and SMS, phone call, Slack, and email escalations don't go through
> the app at all. Keep **Org data notifications** set to **Allow** in your policy so pages always get through.

> [accordion] Does this work with the 事件incidentio app in Mainland China?
>
> No. Intune on mobile is available in the incident.io app only. Read more about the [mobile app in
> China](https://docs.incident.io/on-call/china-mobile-app.md).

> [accordion] What does incident.io read from Microsoft?
>
> The basic profile of the responder signing in, which is enough to confirm their tenant and email match their
> incident.io account. incident.io doesn't read your Intune policies or device inventory.
