Mobile threat defense for staff phones: what it adds to device management, and the main options
Device management sets rules for a phone; mobile threat defense watches for phishing links, risky Wi-Fi and compromised devices. What it catches, how it plugs into access rules, and who offers it.
A phone that passes every rule
A sales manager’s company iPhone is enrolled in device management. It has a passcode, encryption is on, the operating system is current, and the work apps are protected. On a Tuesday he taps a link in a text message that claims his parcel is held at customs, and the page that opens asks him to sign in with his work account to “confirm delivery.” Nothing in his device management policy looks at that link.
That gap is what mobile threat defense (MTD) is for. Device management (MDM) and app protection decide how a phone is configured and what work apps may do. MTD watches what is happening on and around the phone: the links being opened, the network it is joined to, whether it has been jailbroken or rooted, and whether risky apps are installed. Its findings can then decide whether the phone is allowed to reach company email and files.
Microsoft puts the case plainly in its MTD documentation: companies tend to protect PCs and leave mobile devices unmonitored, and although phones have built-in protections such as app isolation and vetted app stores, they remain open to web-based and other attacks.
What MTD looks at
The products differ in detail, but they cover the same broad areas. Microsoft’s own list for Defender for Endpoint on Android and iOS is a fair summary of the category:
| Area | What it means on a phone |
|---|---|
| Web protection | Blocks known phishing and unsafe sites opened from texts, email, chat or the browser |
| Network protection | Flags rogue Wi-Fi and rogue certificates that let someone read or alter traffic |
| Device integrity | Detects jailbroken iPhones and rooted Android phones |
| App risk | On Android, scans for malicious apps and files; on both platforms, reports app and OS vulnerabilities |
| Risk signal | Rates the phone low, medium or high risk and passes that rating to your access rules |
The last row is what turns MTD from an alert feed into a control. Intune can take the MTD vendor’s risk level and compare it with the level you allow. A phone the vendor rates as high risk, for example because it joined a network open to interception, can be marked non-compliant and blocked from Exchange and SharePoint until the problem is fixed. Intune can do the same for phones that are not enrolled at all, through app protection policies: the work apps can be blocked or selectively wiped if the MTD app reports the phone as compromised.
How it fits with what you already have
Three layers, each doing a different job:
- MDM or app protection sets the rules: passcode, encryption, minimum OS version, which apps can open work data.
- MTD checks for threats the rules do not see and produces a risk rating.
- Conditional Access (or the equivalent in your identity system) uses both to decide whether to let the phone in.
If you only have the first layer, a phone can be fully compliant and still be the one that hands over a password. If you add MTD without the third layer, you get alerts that nobody acts on at 9 p.m.
The main options
Intune lists more than a dozen MTD partners whose risk signal it can use. For a small or mid-sized organization, the choice usually follows the security platform you already run.
Microsoft Defender for Endpoint on Android and iOS. Microsoft’s own MTD covers web protection, network protection, jailbreak detection on iOS, malware scanning on Android, root detection on Android (still in preview as of November 2026) and vulnerability assessment of the OS and apps. It reports into the same Defender portal as Windows and Mac alerts, and it supports app protection (MAM) scenarios as well as enrolled phones. On iOS under MAM, Microsoft notes that it protects only the enrolled apps, while its VPN-based web protection can scan traffic from the whole device. It needs Intune, which is a separate product not included in every subscription. If you are already on Microsoft 365 with Intune and Defender, this is the shortest path.
Third-party MTD connected to Intune. Intune’s partner list includes, among others, CrowdStrike Falcon for Mobile, Jamf Mobile Threat Defense, Lookout for Work, SentinelOne, Sophos Mobile, Check Point Harmony Mobile, Zimperium, Trend Micro, Trellix, Symantec Endpoint Protection Mobile, iVerify Enterprise, Pradeo, Better Mobile, BlackBerry Protect Mobile and Trustd Mobile, each for Android and iOS. The practical reason to pick one is consolidation: if your laptops already run CrowdStrike, SentinelOne or Sophos, or your Macs and iPhones are managed with Jamf, using the same vendor on phones keeps one console and one alert queue.
MTD with a non-Microsoft device manager. If you do not use Intune, ask each vendor which device manager it integrates with and how its risk rating is enforced there, before you buy. The risk-based blocking is the part that matters.
A few points apply whichever you choose:
- One vendor per platform. Microsoft recommends a single MTD vendor per platform in a tenant. If you configure two for the same platform, every device on that platform must install and run both, and a missed scan from either marks the device non-compliant. Defender for Endpoint is the exception: it can run alongside a third-party MTD app if each has its own compliance policy for different groups.
- Privacy on personal phones. On a personally owned Android phone with a work profile, Defender protects only the work profile unless the employee also turns it on in the personal profile. Know what each product collects from a personal device and say so in your mobile policy before rollout. Microsoft’s documentation notes that app inventory sharing with MTD partners is opt-in and off by default in Intune.
- Pilot first. Microsoft suggests a pilot with exit criteria: devices appear in inventory, a test phishing page is blocked, and the test alerts show up in the portal.
What MTD does not replace
Some of the strongest phone protections are not products at all. CISA’s mobile communications guidance, revised in March 2026 and written for highly targeted people, though most of it suits any staff phone, recommends phishing-resistant FIDO authentication instead of text-message codes, a password manager, a PIN on the mobile carrier account to resist SIM swapping, regular OS and app updates, and newer hardware where possible, because older phones cannot get every security feature through software updates.
For the few staff who are likely personal targets, Apple’s Lockdown Mode, available from iOS 16, is an extreme option that blocks most message attachments, link previews and some web technologies, and stops the device from joining non-secure Wi-Fi automatically. Apple notes that a device with Lockdown Mode turned on can’t be enrolled in MDM, though one enrolled beforehand stays managed, so enroll the phone first.
A sensible order for a small organization
- Get every phone that touches company data under MDM or app protection, with Conditional Access requiring it.
- Move owners, finance staff and admins to phishing-resistant sign-in.
- Add MTD from the vendor whose console you already use, pilot it with a handful of phones, then connect its risk rating to your access rules.
- Review blocked-device reports monthly, and write down who answers when a phone is blocked after hours.
When to get help
If you are not sure how your phones are protected today, or whether your access rules actually use device risk, a short review usually finds the gap quickly.
Want to talk it through? Book a free 30-minute call with Security Medic Consulting.
Sources
- Microsoft Learn, Mobile Threat Defense with Microsoft Intune, June 24, 2026 (accessed 2026-11-05). Partner list, risk levels, enrolled and unenrolled scenarios, one vendor per platform, opt-in inventory sharing.
- Microsoft Learn, Microsoft Defender for Endpoint: Mobile Threat Defense, September 15, 2026 (accessed 2026-11-05). Capabilities, enrollment scenarios, Intune requirement, pilot criteria.
- CISA, Mobile Communications Best Practice Guidance, version 2.0 November 24, 2025, page revised March 13, 2026 (accessed 2026-11-05).
- Apple Support, About Lockdown Mode, September 14, 2026 (accessed 2026-11-05).