Skip to content

[Guide] Document default team configuration for Autopilot hosts #49603

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
melpike merged 6 commits into from
Aug 6, 2026
Merged

[Guide] Document default team configuration for Autopilot hosts #49603

Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
2b1c183
Document default team configuration for Autopilot hosts
melpike Jul 20, 2026
4c172f8
Update articles/windows-mdm-setup.md
melpike Jul 24, 2026
92f5402
Update articles/windows-mdm-setup.md
melpike Jul 24, 2026
afca043
Revise MDM setup instructions for default fleet
melpike Jul 24, 2026
fa90ab9
Updated docs based on implementation and QA.
getvictor Aug 3, 2026
3de6a54
Doc fixes to match latest code changes.
getvictor Aug 4, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
40 changes: 40 additions & 0 deletions articles/windows-mdm-setup.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -219,6 +219,46 @@ Testing automatic enrollment requires creating a test user in Microsoft Entra ID

2. After it's been wiped, open your workstation and follow the setup steps. On the screen in which you're asked to sign in, you should see the title "Welcome to [your organization]!" next to the logo you uploaded in step 4.

### Set a default fleet for new hosts

_Available in Fleet Premium_

By default, Windows hosts enrolled via Autopilot are added to "Unassigned". You can configure a default fleet so that new hosts enrolled into MDM are automatically assigned to a specific fleet, similar to how [Apple Business default fleets](https://fleetdm.com/guides/macos-mdm-setup#set-a-default-team-for-hosts-enrolled-via-abm) work.

> **Note:** The default fleet applies only to hosts that enroll through end user-driven enrollment (Microsoft Entra). Hosts that install Fleet's agent before enrolling in MDM keep the fleet from their enroll secret instead.

#### In the UI

1. Head to **Settings > Integrations > MDM > Windows MDM** and select **Edit**.

2. Under **User driven enrollment**, use the **Default fleet** dropdown to select the fleet that new hosts enrolled into MDM should be assigned to.

> **Note:** The **Default fleet** dropdown is disabled until Fleet is connected to Microsoft Entra. Connect Entra first using the steps above.

3. Select **Save**.

#### Via GitOps (YAML)

Add the `windows_enrollment` key under `mdm` in your global (org) settings YAML file:

```yaml
mdm:
windows_enrollment:
default_fleet: "💻 Workstations"
```

To clear the default and send new hosts to "Unassigned", set `default_fleet` to an empty string (`""`).

#### How hosts are assigned

A host is assigned to the default fleet only when it enrolls in MDM before Fleet's agent is installed. That's the order Autopilot uses. Fleet applies the default at the moment it links the MDM enrollment to the host record, so:

- Changing the default fleet affects only hosts that enroll after the change. Hosts already in Fleet stay where they are.
- Hosts that already exist in Fleet keep their current fleet when they re-enroll, including hosts you deliberately left in "Unassigned".
- Hosts you moved to another fleet manually aren't moved back to the default.
- Deleting the fleet you set as the default clears the setting, and new hosts go to "Unassigned" until you set a new one.

> **Warning:** Some virtual machines report a placeholder hardware serial such as `System Serial Number` instead of a unique one. Fleet matches a new host to its MDM enrollment by serial number. If two or more unmatched enrollments share a serial, Fleet leaves the host in "Unassigned". This affects Windows MDM enrollment generally, not only default fleets. Configure unique serial numbers on your virtual machines.

## Automatic Windows MDM migration

Expand Down
Loading