ערוך

שתף באמצעות

Distributed IT environment with many admins in the same Microsoft Intune tenant

  • מאמר

Many organizations use a distributed IT environment where they have a single Microsoft Intune tenant with multiple local admins. This article describes one way to scale Microsoft Intune to support multiple local admins who manage their own users, devices, and create their own policies all within a single Microsoft Intune tenant. There's no right or wrong answer on how many admins you can have in your tenant. The article focuses on tenants that have many local administrators.

Distributed IT is needed in systems where a large number of local admins connect to a single Intune tenant. For example, some school systems are organized so that you have a local admin for every school in the system or region. Sometimes, this distributed environment could be 15 or more different local admins who roll up to the same central system or Microsoft Intune tenant.

Each local admin can set up groups to suit their organizational needs. The local admin typically creates groups and organizes multiple users or devices by geographic location, department, or hardware characteristics. The local admins also use these groups to manage tasks at scale. For example, the local admins can set policies for many users or deploy apps to a set of devices.

Roles you need to know

  • Central team: The Central team or group includes the global admins or primary admins in your tenant. These admins can oversee all the local admins and can provide guidance to the local admins.

  • Local admins: The local admins are local and focus on policies and profiles for their specific locations; schools, hospitals and so on.

Role based access control

This section briefly describes the different models and proposes guidelines under each model for managing policies, profiles, and apps between the Central team and the local admins. The models are:

  • Partial delegation model
  • Full delegation model
  • Central model
  • Devolved model
  • Hybrid model

Partial delegation model

The partial delegation model proposes the following guidelines for policy management between the Central team and the local admins.

✔️ Permissions

  • Create, update and delete permissions for policies, enrollment profiles, and apps should be held by the Central team.
  • Grant only read and assign permissions to the local admins.

✔️ Reuse

  • Commonly configured policies, enrollment profiles, and apps should be made available to the local admins to reuse, as much as possible.
  • Microsoft Intune uses many common configurations that fall into a few categories. Review the recommendations listed for App Protection Policies.
  • As local admins onboard, they should review the existing policies and reuse them as needed.

✔️ Exceptions

  • The Central team can create certain new policies, enrollment profiles, and apps as exceptions, when needed, on behalf of the local admins. Usually, these exceptions include any type of profile that requires unique parameters.

A partial delegation model is proposed in these two areas:

Group and assignment guidelines for local admins: What are some of the best practices for local admins to adopt while organizing groups for device management through Microsoft Intune? To find out, read the article Intune grouping, targeting, and filtering: Recommendations for best performance - Microsoft Tech Community

Feature specific guidelines: How are policies/profiles/apps managed between a central authority and the local admins with specific permissions for the different features. For more information, go to the section Feature specific guidelines.

Full delegation model

The full delegation model proposes the following guidelines for policy management between the Central team and the local admins.

  • Each local admin should have their own scope tag to separate each object that they fully manage.
  • When the local admin doesn't need to create, update or delete, then grant the local admin a role with read and assign permissions and avoid assigning any other role with full permission to them. With this approach, you can avoid combining permissions across scope tags.
  • Sometimes the local admins may need to create their own policies, profiles, and apps while sharing some common policies, profiles, and apps. In such cases, create a special group and assign the common policies, profiles, and apps, to this group. This group shouldn't be included in the Scope Group for any local admin. Scope Group. This approach prevents the create, update and delete permissions assigned to the local admins from applying to these common policies, profiles and apps.

Central model

In the central model, a single local admin team (parent) manages multiple child orgs. Factors such as geography, business unit, or size, can relate Child orgs.

  • There's only one scope tag used to cover all the managed local admins.

  • If possible, the local admin team should standardize assignments across local admins and place all their devices into a single Microsoft Entra group for assignment. When it isn't possible to create a single Microsoft Entra group, the local admin team can create different Microsoft Entra groups to make different assignments.

  • If a different local admin team manages or moves an org, the following steps must be taken:

    • All the org's devices and users must be extracted from common Microsoft Entra groups in scope of the original local admin team.

    • All policies/apps/profiles assigned uniquely for that org must have their scope tag updated for the new local admin team.

Devolved model

In the devolved model, multiple local admins (children) are managed both by their dedicated local admin and also overseen by an intermediary local admin team. Both the parent and children admins have their own scope tags to represent management boundaries.

  • If there are fewer than 50 children admins, the intermediate local admin team may be granted access by assigning all the children's scope tags to the intermediate local admin teams RBAC role assignment.
  • If there are more than 50 children admins, the intermediate local admin team should be granted their own scope tag to represent the entire collection of children admins they oversee.
  • Newly created policies under the children admin's scope tags must have the intermediate tag added by a global admin role to prevent the intermediate local admin team from losing visibility.

Hybrid model

In the hybrid model, the same parent admin is used in both Central and Devolved model at the same time. There are no special recommendations for this model.

Feature specific guidelines

Depending on the business requirements for each feature, guidelines provided in this section may recommend that you create policies per local admin and/or delegate the permissions needed for creating objects to the local administrators.

Note

The guidance provided in this section doesn't address every feature, but only covers those areas for which we have special instructions.

App protection policy

App protection policies are rules that ensure an organization's data remains safe or contained in a managed app. For more information, go to App protection policies.

The guidelines for App protection policies are split across the Central team and the local admins as follows:

Central team - Tasks

  • Review the security and business needs across the organization and generate a set of common App protection policies for local admins.
  • Review the recommendations listed to identify what security controls are appropriate before creating any App protection policies.
  • Have an established method for local admins to request customized App protection policies, if necessary, for specific business needs where the business requirements can't be achieved with the existing common policies.
  • For specific recommendations about each configuration level and the minimum apps that must be protected, review Data protection framework using App protection policies, go to App protection policies

Local admins - Permissions and Tasks

  • Provide read and assign permissions, but not create, update, delete permissions on Managed Apps, so they aren't able to create their own App protection policies.
  • Provide read and assign permissions for application configuration policy assignment to their apps.
  • Provide read and assign permissions only when there are different protection policies for managed devices and unmanaged devices. If the Central team chooses to offer only one policy for both, then application configuration policy isn't needed.
  • If application configuration policy is used, it's recommended that you assign the application configuration policy to all App instances without exception.
  • Choose from common App protection policies. Local admins can request the Central team to create custom app protection policies as an exception, and only if necessary.
  • For more information, go to App protection policies

Compliance policy

Compliance policies in Intune define the rules and settings that users and devices must meet to be compliant. For more information on compliance policies, go to Compliance policies.

Central team

The Central team should create common compliance policies for local admins to choose from and only, if necessary, create exception policies. For more information, go to Compliance policies. Creating policies includes the creation of custom compliance policy scripts because they're subject to the same scale as normal compliance policy.

For more information on how to create a compliance policy, go to Compliance policies.

Local admins

Provide local admins with read and assign permissions, but not create, update or delete permissions on Compliance policy. The read and assign permissions allow them to choose from the common compliance policies created by the central team and assign them to their users and devices.

Device configuration

In this section:

  • Device restrictions and general configuration
  • Resource access
  • Windows update rings
  • Feature updates
  • Quality updates

Device restrictions and general configuration

  • Grant local admins permission to create, update, delete within their own scope.

  • Use the Settings Catalog and security baselines to the maximum possible extent, instead of profiles created in the Configuration profiles list, to mitigate scale in the Microsoft Intune admin center.

  • In general, the central team should try to centrally monitor the content of configurations and replace lots of duplicate profiles where possible with a shared profile.

Resource access

The Full delegation model is recommended.

Windows update rings

  • We recommend that Windows update rings are managed centrally. The Central team should create as many common Windows update ring policies as they need to support the variance of the local admins.
  • The local admins shouldn't create their own Windows update rings. When you delegate to a large number of administrators, the total number of objects may become large and difficult to manage. Best practices vary for each feature. For more information, go to Windows update rings.

Feature updates

The Full delegation model is recommended.

Quality updates

The Full delegation model is recommended.

Certificates

  • We recommend you use permissions through the Central team to onboard/offboard connectors as needed. Onboard connectors for each local admin to support certificate issuance.

  • Don't grant the local admins permission to UPDATE or DELETE connectors.

Applications

Grant local admins full permissions to manage apps to the extent of their scope.

In this section:

  • Apple Volume Purchase Program

  • Windows

  • Android

For more information, go to Manage apps.

Apple Volume Purchase Program

Currently, there are no scale concerns for the supported number of Volume Purchase Program tokens. For more information, go to How many tokens can I upload..

Windows

Android

  • Local admins should choose from existing store apps or ask the central team to add new Android store apps. Local admins shouldn't create new Android store apps. The total number of objects may become large and difficult to manage.

  • Local admins can create Android line-of-business apps, as needed, within the cross-platform, line-of-business app and web-link limit.

  • Central team must add Managed Google Play apps.

    • The central team can only see Managed Google Play apps available in their tenant's country/region. If the central team needs a Managed Google Play app only available in some countries/regions, they may need to work with the app developer to get it listed correctly.
    • The central team should manage all content related to managed Google Play apps, including private apps, web apps, and collections. For example, if a customer plans on using the Managed Google Play iframe to publish private apps, they have to do that with a single developer account owned by the central team.
    • The central team can select a single scope tag as the Managed Google Play scope tag. It has a special dropdown in the Managed Google Play connector page. The scope tag will apply to all Managed Google Play apps after the central team adds them to the console, but won't apply retroactively to apps that have already been added. It's highly recommended that the central team set the scope tag before they add apps and then assign each regional team that scope tag. Otherwise, regional admins may not be able to see their Managed Google Play apps.

  • Only one OEMConfig policy is supported per device, except for Zebra devices. With Zebra devices, it's highly recommended that you have the smallest number of policies possible because the time to enforce the policy is additive. For example, if you assign six policies with the assumption that they'll layer on top of each other, it takes around 6X longer to start working on the device than a single policy.

Note

Exercise extreme consideration and caution when setting high-priority update mode on many different apps and groups. This is for multiple reasons:

  • Although many apps can be set to high-priority mode, only one app update can be installed at a time. One large app update could potentially block many smaller updates until the large app is done installing.
  • Depending on when apps release new updates, there could be a sudden spike in your network usage if app releases coincide. If Wi-Fi is not available on some devices, there could also be a spike in cellular usage.
  • Although disruptive user experiences have already been mentioned, the problem grows as more apps are set to high-priority update mode.

For more information on scale concerns regarding Managed Google Play app updates using high-priority update mode, go this Techcommunity article.

Enrollment profiles

In this section:

  • Autopilot
  • Enrollment status page (ESP)
  • Apple business manager (ABM)
  • Android Enterprise profiles
  • Enrollment restrictions
  • Device categories

Autopilot

  • Grant local admins the permissions to read Autopilot devices and upload new Autopilot devices.
  • Local admins shouldn't create Autopilot profiles. When you delegate to a large number of administrators, the total number of objects may become large and difficult to manage. The best practice varies per feature area. For more information on Autopilot, go to Use Autopilot to enroll Windows devices in Intune.

Enrollment status page

  • Local admins should select from existing Enrollment status page profiles to assign, or they should request the Central team to create an exception profile, only if necessary.
  • Local admins shouldn't create Enrollment status page profiles. When you delegate to a large number of administrators, the total number of objects may become large and difficult to manage. The best practice varies per feature area. For information on Enrollment status page, go to Set up the Enrollment Status Page.

Apple Business Manager

If possible, local admins shouldn't be granted create, update or delete permissions on enrollment profiles. If local admins are given permissions to create Apple Business Manager profiles it also gives them create, update and delete permissions in Autopilot. However, local admins shouldn't create Autopilot profiles.

When you delegate to a large number of administrators, the total number of objects may become large and difficult to manage. The best practice varies per feature area. For more information, go to Use Apple Business Manager to enroll Apple devices in Intune.

Android Enterprise profiles

  • The Central team should create Android Enterprise corporate-owned dedicated devices enrollment profiles for each local admin for device grouping.
  • If possible, local admins shouldn't be granted create, update or delete permissions on Android Enterprise devices. These restrictions prevent local admins from modifying the tenant-wide Android Enterprise settings and the global fully managed enrollment profile.

Enrollment restrictions

  • The same set of permissions govern both Device configuration and Enrollment restrictions. When you grant permissions to create for device configuration, then you're also granting permissions to create for enrollment restrictions. However, local admins shouldn't be given permission to create enrollment restriction profiles. So, they should be instructed not to create new Enrollment restrictions profiles.

  • Enrollment device limit restrictions define how many devices each user can enroll. The enrollment device limit restrictions should cover all possible device limits for local admins to share. For more information, go to What are enrollment restrictions.

  • The Central team should standardize Device Type restrictions as much as possible and add new restrictions but only as special exceptions after a local admin has reviewed existing restrictions.

Device categories

The Device categories (Devices > Device categories) feature doesn't have its own permissions family. Instead, its permissions are governed by the permissions set under Organization. Go to Tenant administration > Roles. Select a custom or built-in role and select Properties. Here you can assign permissions, one of them being Organization. So, if you need read permissions for Device categories, then set read permissions in Organization.

Central teams can create Device Categories. However, local admins shouldn't be allowed to create, update, or delete device categories, as it would require granting them permissions on Organization, giving them access to other tenant-level features governed by Organization permissions.

For more information, go to Device categories.

Endpoint analytics

  • The Central team should create as many common Endpoint Analytics baselines as they need to support the variance of the Local admins.
  • If possible, local admins shouldn't create their own Endpoint Analytics baselines. When you delegate to a large number of administrators, the total number of objects may become large and difficult to manage. The best practice varies per feature area.
  • For more information, go to Configuring settings in Endpoint analytics.