On a hybrid device, a GPO and an Intune profile that define the same setting do not play on a level field: by default, the GPO wins, with no error message. A Policy CSP setting can reverse the priority, but its scope is narrower than what you often read. You will learn how to enable it, define what it really covers and verify its effect before rolling it out broadly.
By default, the GPO wins and Intune stays silent
On a device that is domain-joined and enrolled in Microsoft Intune, Group Policy (GPO, Group Policy Object) keeps priority as long as nothing is configured. Migrating a device to Intune therefore does not, by itself, change the balance of power: the Intune profile is delivered, but the GPO value is the one that applies.
The reason is historical. The GPO engine has been built into Windows for about twenty years, runs at startup and refreshes every 90 minutes. Intune's MDM (Mobile Device Management) channel arrived much later and yields when both target the same setting.
The trap is the absence of any signal. An organisation carrying thirty or so GPOs and stacking Intune profiles on top may believe the migration succeeded while the device still follows the old directory. The dashboard can show a successful deployment while the GPO decides the real behaviour.
A green dashboard proves nothing
Intune reports delivery of the profile, not the final arbitration on the device. In some cases, such as the firewall, Intune does report a conflict (see below). The reliable check is the device's MDM diagnostic report.
MDMWinsOverGP: the setting that reverses the priority
The MDMWinsOverGP setting belongs to the ControlPolicyConflict policy of the Policy CSP (Configuration Service Provider). When it is set to 1, the MDM policy is used and the equivalent GPO is blocked in the Group Policy console, according to the ControlPolicyConflict reference on Microsoft Learn.
| Characteristic | Documented value |
|---|---|
| Default value | 0: the GPO wins |
| Value to set | 1: the MDM policy is used, the equivalent GPO is blocked |
| Scope of application | Device |
| Minimum Windows version | Windows 10 1803 |
| Recommended frequency | Reapply at every sync |
The Microsoft Defender documentation specifies that this setting is configured only through the Policy CSP, for example with a custom OMA-URI (Open Mobile Alliance Uniform Resource Identifier) profile. There is neither a GPO setting nor a PowerShell cmdlet to set it: no point looking for any Set- command.
Creating the setting in Intune: settings catalog or OMA-URI
Two routes lead to the same result. The settings catalog is the more readable; the custom profile remains useful if you already manage your exceptions in OMA-URI.
In the Microsoft Intune admin center, create a Windows configuration profile based on the settings catalog. Add a setting, search for control policy conflict, then select MDM Wins Over Group Policy and enable it.
Name the profile explicitly, for example “MDM wins over group policy”, so that a colleague understands why a device's GPOs seem to be ignored.
For a first deployment, proceed in concentric circles.
Target a pilot group of devices
Assign the profile to a group of devices (the setting acts at device level), never to a group of users nor to the whole fleet from the start.
Let the device sync
Wait for the device's MDM sync or trigger it from the device settings. The documentation guarantees no propagation delay: validate by checking, not by the clock.
Check the result on the device
Open the advanced diagnostic report (see the verification section) and confirm that the relevant GPOs appear as blocked.
Global effect on every targeted device
The setting applies across the whole device: all GPOs equivalent to a Policy CSP setting delivered by Intune stop applying, not just the one you had in mind. If the device is unenrolled from Intune, the applicable GPOs are applied again. Test on a pilot before any widening.
The real scope: Policy CSP only
The setting is no miracle worker. Microsoft documentation states that MDMWinsOverGP applies only to Policy CSP policies. If a setting is defined in both GPO and MDM in another CSP, there is a race condition and no winner is guaranteed.
The rule is often summed up as two exceptions, Microsoft Defender and Windows Update, because these are the two workloads most teams want to migrate. The real scope is wider: any setting that belongs to another CSP is out of play.
| Area | CSP involved | MDMWinsOverGP effective? | Recommended action |
|---|---|---|---|
| Policy CSP settings | Policy CSP | Yes | The MDM profile wins, the equivalent GPO is blocked |
| Microsoft Defender | Defender CSP | No | Remove Defender settings from GPOs and keep a single management authority |
| Windows Update | Out of scope | No: the GPO keeps control | Remove the Windows Update GPOs that block access to Windows Update for Business; migration target: Windows Autopatch |
| Windows Firewall | Firewall CSP | No | Avoid custom CSPs, use Endpoint Security profiles, delete the GPO |
The firewall case is instructive. On a device with MDMWinsOverGP set to 1, a firewall disabled by GPO and enabled by an Intune profile stayed disabled, and Intune showed “Conflict”, as reported in this Q&A thread on Microsoft Learn. The setting belonged to the Firewall CSP, hence outside the scope.
For Defender, Microsoft documentation recommends removing Defender settings from GPOs when managing through MDM. It also describes “controlled configuration”, which applies only the settings from Intune or Defender security settings management and ignores conflicting GPOs, Configuration Manager and local settings.
Should you really enable MDMWinsOverGP?
Not systematically. Jason Sandys, a Microsoft employee and Q&A moderator, states in this thread on Intune and domain-joined PCs that the setting does not apply to all settings and that relying on it is risky. Another contributor strongly advises against it and prefers targeting: not applying the setting to the device on the GPO side, using WMI filters, permissions and organisational units.
Strengths
- Quick switch during a gradual migration
- A single profile to deploy, without touching existing GPOs
- Simple rollback: remove the profile
Limitations
- Scope limited to the Policy CSP
- Contention left unresolved for other CSPs
- Hides obsolete GPOs instead of cleaning them up
- Reversible on unenrolment: GPOs take control again
Implementation: spotting out-of-scope GPOs on a pilot device
Before enabling the setting, you need to know which machine GPOs touch Defender, Windows Update or the firewall: these are the ones that will keep winning. The following read-only script produces an HTML gpresult report and a CSV of the lines that match these three areas.
Prerequisites: Windows PowerShell 5.1 or later, session run as local administrator on the pilot device, no module to install. Minimum permission: local administrator (required for gpresult /scope computer). Output: an HTML file, a plain text file and a CSV in C:\ProgramData\GpoIntuneAudit. Detection relies on keywords: it serves as a first-pass filter, not as proof.
1[CmdletBinding()]2param(3 # Dossier de sortie des rapports4 [string]$OutputFolder = (Join-Path $env:ProgramData 'GpoIntuneAudit')5)6 7$ErrorActionPreference = 'Stop'8 9# gpresult en portée ordinateur exige une session élevée10$principal = [Security.Principal.WindowsPrincipal][Security.Principal.WindowsIdentity]::GetCurrent()11if (-not $principal.IsInRole([Security.Principal.WindowsBuiltInRole]::Administrator)) {12 throw 'Relancez PowerShell en tant qu''administrateur.'13}14 15New-Item -ItemType Directory -Path $OutputFolder -Force | Out-Null16$stamp = Get-Date -Format 'yyyyMMdd-HHmmss'17$htmlPath = Join-Path $OutputFolder "gpresult-$stamp.html"18$txtPath = Join-Path $OutputFolder "gpresult-$stamp.txt"19$csvPath = Join-Path $OutputFolder "gpo-hors-perimetre-$stamp.csv"20 21# Rapport HTML complet (à ouvrir dans un navigateur) et version texte détaillée22gpresult /scope computer /h $htmlPath /f | Out-Null23gpresult /scope computer /v | Out-File -FilePath $txtPath -Encoding utf824 25# Domaines que MDMWinsOverGP ne couvre pas (Defender CSP, Firewall CSP, Windows Update)26$domaines = [ordered]@{27 'Microsoft Defender' = 'Defender|Antivirus|Antimalware'28 'Windows Update' = 'Windows Update|WindowsUpdate|WSUS'29 'Pare-feu' = 'Firewall|Pare-feu'30}31 32$lignes = Get-Content -Path $txtPath33$resultats = foreach ($nom in $domaines.Keys) {34 $lignes | Select-String -Pattern $domaines[$nom] | ForEach-Object {35 [pscustomobject]@{36 Domaine = $nom37 Ligne = $_.LineNumber38 Texte = $_.Line.Trim()39 }40 }41}42 43$resultats | Export-Csv -Path $csvPath -NoTypeInformation -Encoding UTF844$resultats | Group-Object -Property Domaine | Select-Object Name, Count | Format-Table -AutoSize45 46Write-Host "Rapport HTML : $htmlPath"47Write-Host "CSV d'audit : $csvPath"To confirm the device's join status before the audit, this command displays the relevant lines:
1dsregcmd /status | Select-String -Pattern 'AzureAdJoined|DomainJoined|MdmUrl'A CSV line in the Defender or Windows Update area signals a GPO to remove or to target differently, whether MDMWinsOverGP is enabled or not.
Verifying the effect and troubleshooting
Microsoft documentation designates the MDM diagnostic report as the right way to verify: Settings > Accounts > Access work or school > Advanced Diagnostics Report. It lists the blocked GPOs. The Intune dashboard is not enough to conclude. This path opens directly with the following command:
1Start-Process 'ms-settings:workplace'Checks after deployment on the pilot
- The MDMWinsOverGP profile is assigned to a device group, not a user group
- The advanced diagnostic report lists the expected GPOs as blocked
- No Defender, Windows Update or firewall setting remains in the pilot's GPOs
- The relevant Intune profiles do not show a “Conflict” status
- The device's effective behaviour (firewall, updates) matches the intent of the Intune profile
| Symptom | Probable cause | Resolution |
|---|---|---|
| The profile is “succeeded” but the device follows the GPO | MDMWinsOverGP not applied or setting outside the Policy CSP | Check the assignment to the device group, then the MDM diagnostic report |
| Intune shows “Conflict” on a firewall profile | Firewall CSP setting, out of scope | Delete the firewall GPO, use an Endpoint Security profile |
| Defender ignores the Intune profile | Defender settings still defined in GPOs | Remove Defender settings from GPOs, keep a single management authority |
| Updates do not follow the cloud policy | Windows Update GPO blocking access to Windows Update for Business | Delete these GPOs on co-managed pilot devices |
| GPOs take control again after a reset | Device unenrolled from Intune | Re-enrol the device, check the profile, reapply the setting |
Frequently asked questions
Which wins by default between a GPO and an Intune profile?
By default, the GPO wins: the value of MDMWinsOverGP is 0. The Intune profile may appear applied while the device follows the GPO.
Is there a GPO or a PowerShell cmdlet to enable MDMWinsOverGP?
No. Microsoft documentation states that the setting is configured only through the Policy CSP, for example with a custom OMA-URI profile on ./Device/Vendor/MSFT/Policy/Config/ControlPolicyConflict/MDMWinsOverGP, of integer type and value 1.
Does MDMWinsOverGP cover Defender and Windows Update?
Not for Defender: the documentation states that the setting does not apply to the Defender CSP. For Windows Update, the GPO keeps control, and the corresponding GPOs must be removed from co-managed pilot devices.
What happens if the device is unenrolled from Intune?
The applicable GPOs are applied again. The setting lives in MDM management: without enrolment, there is no longer any arbitration in favour of Intune.
Where to start
Start with the inventory, not the setting. Audit a pilot device with the script above, sort the GPOs into three batches (migratable, out of scope, obsolete), then decide on the method.
Next actions
- Run the audit on a representative hybrid device and read the CSV
- Remove Defender, Windows Update and firewall settings from GPOs before going any further
- Create the MDMWinsOverGP profile for a pilot group of devices
- Validate each blocked GPO in the MDM diagnostic report
- Plan the target: Windows Autopatch for updates, Microsoft Defender for Business for protection, with a single management authority
If your estate has few, well-identified GPOs, target them rather than enabling the setting at device scale: this is the option favoured by some Microsoft Q&A contributors. If you have dozens of GPOs and a staggered migration, MDMWinsOverGP offers an acceptable transition, provided you clean up the settings outside the Policy CSP in parallel.
Going further
- ControlPolicyConflict Policy CSP: official reference on values, supported OS versions and the MDM diagnostic report.
- Defender CSP: confirms that MDMWinsOverGP does not apply to Defender.
- Configure ASR rules and exclusions: order of priority between local settings, GPO and MDM, with the OMA-URI configuration.
- Our Group Policy vs Intune guide to migrating device configuration: the complete migration approach.
- Microsoft Defender and Intune: the risk-free migration: the Defender workstream, which remains outside the scope of MDMWinsOverGP.



