Intune groups
Overview
Devices and users are organised into groups and have a naming convention that start with the local authority or school number to identify them. These groups are nested under a top-level local authority group to form a hierarchy of schools within that local authority and are split into two branches (devices and users) to provide separation and flexibility. Configuration items are assigned to groups, so using a hierarchical structure allows common assignments to be placed once at a higher level and inherited by the groups nested within it.
This group structure can be viewed within Intune for Education, and only displays the part of the hierarchy that the administrator is scoped for. In Intune for Education, policy assignments and app deployments can also be made directly on an individual group.
Each school has 3 device groups (Provisioning Devices, Student Devices, and Teacher Devices), and 2 user groups (Students and Teachers) which are maintained by the Hwb provisioning service with data from the school’s Management Information System (MIS).
Additional groups can be created through the User Management Portal to provide flexibility in assigning apps and configuration policies to different sets of devices or users. All user and device groups are created at the same level and cannot be nested further. It’s best practise to create an additional group for a specific purpose and then join a user or device to multiple groups to combine their effects.
Examples:
- An IT suite of computers may require a different app to other computers in the school. By creating an additional device group called “ICT Suite 1” and assigning the app to this group in Intune, it will only be deployed to devices in this group.
- School Devices
- Provisioning Devices
- Student Devices
- Teacher Devices
- iPads
- ICT Suite 1
- School Devices
- Members of the senior management team may require access to a secure share hosted on SharePoint on any device they log into. By creating an additional user group called “Senior Management Team” and assigning a configuration profile set to sync the document library with their OneDrive client, the secure share will be made available to these users on all devices they use.
- School Users
- Students
- Teachers
- Senior Management Team Users
- School Users
Device and User groups cannot be created or managed through Intune by delegated administrators. This must be done through the User Management Portal, as per the guides below.
Provisioning devices group
The Provisioning Devices group is a special group, created by the Hwb team, to automatically put enrolled devices into the administrative scope of the school or local authority. There are several rules to determine membership of the provisioning devices group, and at least one of these must be met to be able to see and manage the device.
- GroupTag = Device Provisioning Identifier*
Only applicable to Windows devices deployed through Autopilot. - Device Name Prefix = Device name starts with the Device Provisioning Identifier*
Applicable to all devices, but is the only rule that can be satisfied when enrolling Windows devices using a provisioning package. - Enrolment profile name prefix = Enrolment profile name starts with the local authority or school number
This is applicable to iPads only – Windows devices using Autopilot should use the GroupTag instead. For LAs, enrolment profiles should start with their 3-digit code followed by a space to satisfy the rule (e.g. “660 Enrolment profile name”).
*The Device Provisioning Identifier (DPId) is a unique 5-character code assigned to each school (4-characters for LAs). These can be looked-up on the Intune Device Groups page in the User Management Portal.
There may be a delay in devices showing up in the provisioning devices group due to the dynamic rules needing to process. Once a device is visible in the provisioning devices group it may need to be joined to other groups to receive the relevant apps and policies, which can be done using the Intune Groups page in the User Management Portal.
We do not recommend applying any apps or policies to the provisioning devices group, it should be treated as a placeholder for devices only. Separate groups should be used for Autopilot enrolment profiles, and policies for common configurations should be applied to the parent devices group.
Managing device groups through the User Management Portal
Device groups can be managed through the Intune Device Groups page in the User Management Portal – Administration -> Intune Device Groups
In this section you can:
- view existing device groups
- create new device groups
- view devices in an existing device group
- move or add devices in a device group to another device group
- view the Device Provisioning Identifier for your local authority or school
- lookup Bitlocker keys and LAPS managed passwords on Windows devices
Managing user groups through the User Management Portal
User groups can be managed through the Intune Device Groups page in the User Management Portal – Administration -> Intune User Groups
In this section you can:
- view default Intune user groups
- create and view custom user groups
- add or remove users to a custom user group
You can only manage members of a custom Intune group. Default groups are managed by the Hwb Provisioning service.