3.2. Plan and Implement Device Configuration Profiles
💡 First Principle: A configuration profile is a declaration, not a script: it states the value a setting should have, and the device's own management client (a CSP on Windows, a payload on Apple, an app or API on Android) makes it so and reports back. You pick the platform, then the surface that exposes the setting (settings catalog, template, custom OMA-URI, imported ADMX or OEMConfig), then assign it to groups and narrow it with an assignment filter.
Why care? Profiles are the bulk of day-to-day Intune work, and they fail quietly. Questions describe the symptom; this table gives the outcome:
| Situation | What Intune does |
|---|---|
| Two configuration profiles set one setting differently | Reports a conflict; you resolve it manually |
| Compliance policy and configuration profile set the same setting | Compliance policy wins |
| Two compliance policies disagree | Most restrictive applies |
| Two app protection policies disagree | Most restrictive wins, except numeric fields |
| Profile unassigned or removed | Wi-Fi, VPN, certificate and email profiles are removed; Android settings stay; on Windows it depends on the CSP, and some settings "tattoo" |
To revert a tattooed Windows setting, deploy a policy that sets the value you want (or Not configured) rather than just deleting the old profile.
⚠️ Common Misconception: Exclusions look like simple set subtraction, so it seems natural to include a user group and exclude a device group in one assignment. That mix isn't supported: Intune doesn't evaluate user-to-device relationships, so devices you meant to exclude can still get the policy. Exclude the same group type you include, or use an assignment filter.