{"id":4443,"date":"2022-11-16T11:23:44","date_gmt":"2022-11-16T19:23:44","guid":{"rendered":"https:\/\/SUMMALAI.COM\/?p=4443"},"modified":"2022-11-16T11:23:47","modified_gmt":"2022-11-16T19:23:47","slug":"how-to-create-an-azure-ad-device-group-for-windows-11-devices","status":"publish","type":"post","link":"https:\/\/SUMMALAI.COM\/?p=4443","title":{"rendered":"How to Create an Azure AD Device Group for Windows 11 Devices"},"content":{"rendered":"\n

Let\u2019s learn to create Windows 11 Azure AD Device Group<\/strong>. You will have to get ready with Windows 11 PCs sooner than later. One of the things you can start with is creating Azure AD dynamic devices for Windows 11 PCs.<\/p>\n\n\n\n

You can create Azure AD dynamic device groups based on available device properties. Well, you can\u2019t create dynamic device groups based on applications installed device (unlike\u00a0SCCM collections<\/strong>). This is expected because Azure AD is not a device management solution like Intune and SCCM.<\/p>\n\n\n\n

The\u00a0Intune assignment filters<\/strong>\u00a0are another useful method to filter devices based on their properties. I think Intune filter rules will be powerful as SCCM collection queries in the future. I\u2019ve shared details on using filter rules to\u00a0include or exclude Windows 11 devices\u00a0from an app or policy deployment.<\/p>\n\n\n\n

Useful Device Properties in Azure AD<\/strong><\/h2>\n\n\n\n

There is a bunch of device properties supported in Azure AD. However, I don\u2019t think all the Azure AD device properties are exposed to the public. Let\u2019s first check what the useful device properties<\/strong> in Azure AD from a device management perspective are.<\/p>\n\n\n\n

\"Create
Create Windows 11 Azure AD Device Group \u2013 AAD Dynamic Device Group<\/figcaption><\/figure>\n\n\n\n
AAD Device Properties<\/th>What?<\/th><\/tr><\/thead>
Account Enabled<\/td>Never Used it<\/td><\/tr>
Object ID<\/td>Never Used it<\/td><\/tr>
Display Name<\/td>Useful<\/td><\/tr>
Is Rooted<\/td>Not for Windows<\/td><\/tr>
Device OS Type<\/td>Useful<\/td><\/tr>
Device OS Version <\/td>Useful<\/td><\/tr>
Device Category<\/td>Never Used it<\/td><\/tr>
Device Manufacturer<\/td>Useful<\/td><\/tr>
Device Model<\/td>Useful<\/td><\/tr>
Device Ownership<\/td>Useful<\/td><\/tr>
Enrollment Profile Name<\/td>Useful<\/td><\/tr>
Management Type<\/td>Never Used it<\/td><\/tr>
OU Details<\/td>Never Used it<\/td><\/tr>
Device ID<\/td>Never Used it<\/td><\/tr>
Device Physical IDs<\/td>Never Used it<\/td><\/tr>
System Label<\/td>Useful<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Create Windows 11 Azure AD Device Group \u2013 AAD Dynamic Device Group<\/p>\n\n\n\n

Create Azure AD Dynamic Device Group for Windows 11<\/strong><\/h2>\n\n\n\n

Let\u2019s now build an Azure AD dynamic device group for Windows 11 PCs. I think the best reliable option is to go with OS version<\/strong> properties. However, if you plan to onboard Hololens and another kind of Windows 11 device into Azure AD\/MEM management, you should use additional properties as well.<\/p>\n\n\n\n