Skip to content

Commit

Permalink
Update requirements.md
Browse files Browse the repository at this point in the history
Updating the document to make it more specific on what Device Enrollment Restriction needs to have the Allow MDM enrollment set. How it's currently written, it seems we can just enable it on any restriction policy, but if we do this the Windows 365 provisioning will fail. Instead, we need to make sure that Allow MDM is set to allow in the default policy. I also updated the Restriction Policy docs, to include the Windows 365 under the limitations (Pull request #16066, approved and published on 10/09/2024)
  • Loading branch information
RicardoGFGomes authored Sep 10, 2024
1 parent 89053fc commit 009fbe8
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion windows-365/enterprise/requirements.md
Original file line number Diff line number Diff line change
Expand Up @@ -63,7 +63,7 @@ A subscription in Azure Government is required for Windows 365 Government custom
## Microsoft Entra ID and Intune requirements

- A valid and working Intune and Microsoft Entra tenant.
- Intune device type enrollment restrictions set to Allow Windows (MDM) platform for corporate enrollment.
- Intune default device type enrollment restrictions needs to be set to Allow Windows (MDM) platform for corporate enrollment. Check the [Device Enrollment Restrictions Limitations](/intune/enrollment/enrollment-restrictions-set#limitations) for more information.
- Infrastructure configuration: If you plan on provisioning Microsoft Entra hybrid joined Cloud PCs, you must configure your infrastructure to automatically Microsoft Entra hybrid join any devices that domain join to the on-premises Active Directory. This [configuration lets them be recognized and managed in the cloud](/azure/active-directory/devices/overview).
- Microsoft Entra Domain Services isn't supported because it doesn't support Microsoft Entra hybrid join.

Expand Down

0 comments on commit 009fbe8

Please sign in to comment.