Intune fundamentals¶
Intune is Microsoft's cloud service for managing devices and apps. It sits on top of Microsoft Entra ID, which supplies the users, groups and device identities, and it exposes everything through Microsoft Graph. Most confusion with Intune comes from not knowing which of those three systems is responsible for a behavior. This page explains the moving parts.
What Intune manages¶
| Platform | Typical management |
|---|---|
| Windows 10 and 11 | Full MDM through the built-in Windows MDM client and configuration service providers (CSPs), plus the Intune Management Extension for Win32 apps, scripts and remediations |
| macOS | Apple MDM and declarative device management, plus the Intune agent for shell scripts and macOS apps |
| iOS and iPadOS | Apple MDM and declarative device management, or app protection only |
| Android | Android Enterprise (work profile, fully managed, dedicated), AOSP for devices without Google services, or app protection only |
| Linux | Ubuntu and Red Hat Enterprise Linux desktops: enrollment, compliance and scripts |
Intune also covers specialty devices such as visionOS and tvOS, AR/VR headsets and Teams Rooms devices. Check supported operating systems before you commit to a minimum OS version.
How the pieces fit together¶
flowchart LR
A[Admin in Intune admin center] -->|Microsoft Graph| I[Intune service]
S[Scripts and automation] -->|Microsoft Graph| I
I <-->|identity, groups,<br/>device objects| E[Microsoft Entra ID]
I -->|"wake-up notification<br/>(WNS, APNs, Google)"| D[Managed device]
D -->|check-in: pulls policies,<br/>apps and actions| I
D -->|reports state| I
I -->|compliance state| E
E -->|Conditional Access<br/>at sign-in| R[Microsoft 365 and other apps]
M[Defender for Endpoint] -->|device risk| I
Three things in this diagram explain most day-to-day behavior:
- Devices pull, Intune nudges. Intune never pushes settings directly. It sends a wake-up notification through the platform push service, and the device checks in to collect what's pending. If the device is offline or can't reach the push service, nothing happens until its next scheduled check-in.
- Entra ID owns identity and groups. Assignments target Entra groups, so group membership changes (especially dynamic groups) must process before Intune can act on them.
- Compliance flows back to Entra ID. Intune calculates whether a device is compliant and writes that to the device object in Entra ID. Conditional Access reads it at sign-in. Intune doesn't block anything by itself.
Management models¶
| Device management (MDM) | App protection (MAM) | |
|---|---|---|
| What is managed | The whole device, or a work profile on it | Individual apps and the work data inside them |
| Enrollment | Required | Not required |
| Typical use | Corporate devices, and BYOD where users accept enrollment | Personal phones and tablets, unmanaged Windows browsers |
| Wipe options | Full wipe (corporate), or retire to remove company data | Selective wipe of work data inside apps only |
| Can deploy | Settings, certificates, Wi-Fi/VPN, apps, scripts, updates | Data protection rules: PIN, copy/paste, save-as, encryption |
| Conditional Access grant | Require device to be marked as compliant | Require app protection policy |
You can and often should combine them. App protection policies can target enrolled and unenrolled devices separately by using filters.
Co-management
If you still run Configuration Manager, co-management lets a Windows device be managed by both. You move workloads (compliance, configuration, apps, updates and so on) to Intune one at a time. It's a migration tool, not a permanent design goal for most organizations.
Device identity on Windows¶
A Windows device can be in one of three Entra states. This decides how it enrolls and which features work.
| State | What it means | Typical source | Notes |
|---|---|---|---|
| Microsoft Entra joined | The device belongs to the organization and users sign in with Entra accounts | Autopilot, out-of-box setup | Recommended for all new corporate devices |
| Microsoft Entra hybrid joined | Joined to on-premises Active Directory and registered in Entra ID | Existing domain-joined estate, GPO auto-enrollment, hybrid Autopilot | Supported, but Microsoft doesn't recommend it for new deployments |
| Microsoft Entra registered | A personal device with a work account added | "Add work or school account" in Settings | Used for BYOD, app protection on Windows and some app scenarios |
Check a device's state with dsregcmd /status on the device. See Other Windows enrollment for moving away from hybrid join.
Ownership: corporate or personal¶
Every enrolled device is marked Corporate or Personal. Ownership changes what admins can see and do. For example, on personal devices Intune shows only part of the phone number, doesn't inventory apps the user installed personally, and limits some wipe options.
Ownership is set by the enrollment method. Automated Device Enrollment, Autopilot, Android Enterprise corporate methods and device enrollment managers produce corporate devices. Users enrolling through Company Portal produce personal devices, unless the device matches a corporate identifier. An admin can change ownership on the device record later.
How policy reaches a device¶
Devices check in on three kinds of triggers:
- Change-based: when you assign, change or remove a policy, app or group membership, Intune notifies online devices. Delivery ranges from immediate to a few hours.
- Scheduled: maintenance check-ins run about every 8 hours, and Intune allows only one maintenance sync every 6.5 hours. Newly enrolled devices check in much more often for the first hours.
- Manual: an admin runs Sync on the device, or the user syncs from Company Portal.
The Windows Intune Management Extension runs its own schedule for Win32 apps (hourly) and scripts. See Timings and limits for the full table.
Testing a change? Force the sync
When you pilot a change, don't wait for the schedule. Run Sync from the device page in the admin center, or ask the user to select Sync in Company Portal. On Windows you can also restart the Microsoft Intune Management Extension service to make it re-check apps and scripts.
What kind of policy do I need?¶
| Goal | Use | Where |
|---|---|---|
| Configure a setting (Wi-Fi, restrictions, Edge, Office, OS settings) | Settings catalog profile (or a template if the setting only exists there) | Devices > Manage devices > Configuration |
| Decide whether a device is trusted | Compliance policy | Devices > Manage devices > Compliance |
| Configure Defender, firewall, BitLocker, LAPS, ASR | Endpoint security policy | Endpoint security |
| Apply Microsoft's recommended security settings | Security baseline | Endpoint security > Security baselines |
| Protect work data in mobile apps | App protection policy | Apps > Protection |
| Pre-configure an app | App configuration policy | Apps > Configuration |
| Run code on Windows | Platform script or remediation | Devices > Manage devices > Scripts and remediations |
| Control OS updates | Update rings, feature, quality and driver update policies | Devices > Manage updates |
| Block access from untrusted devices | Conditional Access (in Entra ID) | Endpoint security > Conditional access or the Entra admin center |
Assignments in one minute¶
- You assign policies and apps to Entra groups of users or devices. You can also use the virtual groups All users and All devices.
- Include and exclude groups let you carve out exceptions. Don't mix user groups and device groups across include and exclude on the same assignment. The results are hard to predict.
- Assignment filters narrow an assignment by device properties (OS version, model, ownership, enrollment profile and more) at check-in time.
- Apps also have an intent: Required installs automatically, Available shows in Company Portal, Uninstall removes it.
The Targeting guide covers this in depth, including how to avoid slow dynamic groups.
When policies conflict¶
| Situation | What happens |
|---|---|
| Two configuration profiles set the same setting to different values | Intune reports a conflict and the setting may not apply. You must fix it yourself. |
| A compliance policy and a configuration profile set the same setting | The compliance policy setting wins. |
| Two compliance policies disagree | The most restrictive value applies. |
| Two app protection policies disagree | The most restrictive value applies (numeric fields behave differently). The first policy to apply usually stays in effect. |
| Custom Apple profiles (.mobileconfig) conflict | Intune doesn't evaluate the payload. Apple applies one of them unpredictably. Avoid overlap. |
| Group Policy and Intune both configure Windows Hello for Business | Group Policy wins. |
Removing a policy doesn't always undo it
On Windows, what happens when you unassign a profile depends on the CSP. Some settings revert, and some stay as they were ("tattooing"). On Android, most settings stay on the device. Wi-Fi, VPN, certificate and email profiles are removed on all platforms. To roll back reliably, assign a profile with the value you want rather than just deleting the old one.
Map of the Intune admin center¶
The admin center reorganized its Devices node in 2024 and 2025. Today the important areas are:
| Node | What's inside |
|---|---|
| Devices | All devices, Monitor reports, By platform views, Device onboarding (Enrollment), Manage devices (Configuration, Compliance, Conditional access, Scripts and remediations, Group Policy analytics), Manage updates (Windows, Apple, Android firmware), Organize devices (categories, cleanup rules, assignment filters), Device query |
| Apps | All apps, platform views, Monitor, Protection, Configuration, App selective wipe, assignment filters |
| Endpoint security | Antivirus, Disk encryption, Firewall, Endpoint detection and response, Attack surface reduction, Account protection, Endpoint Privilege Management, Security baselines, Device compliance, Defender for Endpoint connector |
| Reports | Device management reports, endpoint analytics, Windows update reports, Diagnostic settings, data warehouse |
| Tenant administration | Roles, Multi Admin Approval, Audit logs, Connectors and tokens, Assignment filters, Intune add-ons, Customization, Tenant status, Cloud PKI, Remote Help |
| Troubleshooting + support | Per-user troubleshooting view and support requests |