# Resolve competing Autopilot profiles using their creation order

> Which Autopilot profile wins when a device group receives more than one deployment profile?

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260917-004-resolve-competing-autopilot-profiles-using-their-creation-order/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-17T16:34:56+00:00
- Modified: 2026-09-17T16:35:03+00:00
- Last reviewed by DSE: 2026-09-17
- Resource type: Guide
- DSE priority: Information
- Topics: Cybersecurity, IT
- Reading time: 1 minutes

## What you need to know

Which Autopilot profile wins when a device group receives more than one deployment profile?

## Potentially affected

Use this review when troubleshooting an unexpected Windows Autopilot deployment profile or consolidating overlapping group assignments. Record the specific device and all relevant assignments before changing the configuration.

## DSE recommendation

DSE recommends removing unintended assignment ambiguity instead of relying on names or edit recency to explain the outcome.

## Article

## Source facts

When a group is assigned multiple Windows Autopilot profiles, Microsoft says the oldest-created profile wins the conflict. The profile’s creation date is available in its Essentials information. Changes to a profile do not reach an already enrolled Intune device until that device is reset and enrolled again. [Microsoft Learn](https://learn.microsoft.com/en-us/autopilot/profiles).

## Applicability

Use this review when troubleshooting an unexpected Windows Autopilot deployment profile or consolidating overlapping group assignments. Record the specific device and all relevant assignments before changing the configuration.

## DSE recommendation

DSE recommends removing unintended assignment ambiguity instead of relying on names or edit recency to explain the outcome. Compare the creation dates of applicable profiles and document the intended winner. Separate the assignment correction from any proposed reset: obtain the normal operational authorization and data-handling plan for that distinct action.

## Verification

Before an approved deployment, inspect the device’s assigned profile and compare it with the intended configuration. Retain the competing profile identities, creation dates, group membership and final assignment. If testing a profile edit on an existing device, state the enrollment state in the results so an unchanged running configuration is not presented as evidence that the revised deployment profile failed.

## Official references

[Microsoft Learn: Configure Windows Autopilot profiles](https://learn.microsoft.com/en-us/autopilot/profiles). Source reviewed September 17, 2026.

## Primary reference

- Name: Configure Windows Autopilot profiles | Microsoft Learn
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/autopilot/profiles
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Resolve competing Autopilot profiles using their creation order,” DSE Security, https://update.dsesecurity.com/updates/dse-20260917-004-resolve-competing-autopilot-profiles-using-their-creation-order/
Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/
Usage and citation policy: https://update.dsesecurity.com/usage/
Copyright © 2026 Detection Systems & Engineering. All rights reserved.