Microsoft Lets Admins Pin Copilot to the Windows Taskbar for Selected User Groups

Microsoft is rolling out a new Microsoft 365 admin center setting that gives administrators more control over where the Microsoft Copilot app appears on Windows taskbars. Starting in late September 2026, organizations with Intune-managed Windows devices can pin Copilot to the taskbar for specific user groups rather than applying the setting broadly.

The change is designed for organizations that want to introduce Copilot gradually. Administrators can target departments, pilot teams, Copilot champions, or other predefined groups, provided the Copilot app is already installed on the relevant Windows devices.

The rollout is scheduled for worldwide General Availability and is expected to be completed by the end of September 2026.

What Microsoft Is Changing

The new option appears in the Microsoft 365 admin center under Copilot > Settings > Pin Microsoft Copilot App to Windows Taskbar.

Instead of treating taskbar pinning as an organization-wide decision, administrators can use a group picker to select the users who should receive the pinned Copilot app.

That distinction matters because the setting controls the taskbar experience, not the installation of the application itself.

Microsoft specifically notes that the feature does not install Copilot. The app must already be present on an eligible, Intune-managed Windows device for the pinning setting to have an effect.

The key points for administrators are:

Pin Copilot for one or more selected user groups.
Target groups by department, function, pilot program, or other deployment strategy.
Apply the setting only to eligible Intune-managed Windows devices.
Ensure the Copilot app is installed before relying on taskbar pinning.
Configure the feature with an Intune Administrator or Global Administrator role.

Why Group-Based Pinning Matters

For many organizations, deploying a new AI application is not simply a matter of making it available to everyone at once.

IT teams may want to start with a smaller group, gather feedback, provide training, and expand access as users become familiar with the application. The new taskbar control gives administrators another way to align the Windows interface with that phased approach.

A pilot group, for example, can receive the pinned Copilot app while other employees continue using their existing desktop configuration.

The same approach can be used for departmental deployments. An organization could create groups for teams such as Sales or HR and pin Copilot after those employees complete the relevant onboarding process.

This makes the taskbar setting part of a broader deployment strategy rather than simply a cosmetic Windows configuration.

How the New Copilot Setting Works

Administrators first need to create the user groups they intend to target. Those groups can reflect the organization’s preferred Copilot rollout model.

Once the groups are available, the administrator can access the Copilot settings area in the Microsoft 365 admin center and use the group picker to select them for pinning.

The process can be summarized as follows:

Create the appropriate user groups.
Confirm that the Microsoft Copilot app is installed on the Windows devices that should receive the setting.
Open the Copilot settings in the Microsoft 365 admin center.
Select the groups that should receive taskbar pinning.
Expand the deployment to additional groups as the organization’s rollout progresses.

Microsoft also indicates that administrators can eventually select the option to pin Copilot for all devices when they are ready to broaden the deployment.

The Feature Does Not Install Copilot

One of the most important details in Microsoft’s announcement is the distinction between installation and pinning.

The new control changes the taskbar experience on eligible devices where Copilot is already installed. It does not act as an application deployment mechanism.

That means organizations planning to use the feature need to account for application installation separately.

This distinction could also prevent a common deployment misunderstanding: selecting a group for taskbar pinning will not automatically put the Copilot application onto every Windows machine belonging to those users.

IT teams should therefore verify their existing Copilot application deployment before configuring the new taskbar policy.

Designed for Pilot Groups and Departments

Microsoft highlights several potential deployment scenarios for the feature.

Copilot champions and pilot users

Organizations introducing Copilot to a limited audience can create a pilot or champions group and pin the app for those users first.

This approach allows IT and business teams to establish an initial deployment group before expanding the configuration to additional employees.

Department-based deployment

Organizations can also use departmental groups.

For example, Sales or HR could receive the pinned Copilot application after completing an internal onboarding program. Additional departments could then be added as their respective rollout plans progress.

Gradual organization-wide deployment

The group-based model can also support a staged transition toward broader availability.

Rather than moving immediately from a limited pilot to every Windows device, administrators can add groups incrementally and monitor their deployment process along the way.

What Organizations Need Before Using It

The feature has several prerequisites that administrators should check before configuring it.

The environment needs to include Intune-managed Windows devices, and the Microsoft Copilot app must already be installed on the devices being targeted.

Administrators also need the appropriate permissions. Microsoft states that users with the Intune Administrator or Global Administrator role can see and configure the setting.

That makes this primarily an IT administration feature rather than an end-user preference.

What This Means for Windows Users

For employees in a selected group, the most visible change is straightforward: the Microsoft Copilot app can appear pinned to the Windows taskbar.

The broader significance is that the appearance of Copilot on the desktop can now be managed according to group membership.

Employees outside the selected groups are not automatically included simply because the organization has enabled the feature. The configuration can instead reflect the organization’s chosen rollout structure.

This gives administrators another layer of control over how Copilot is introduced into managed Windows environments.

AI Governance Considerations

Microsoft’s update also identifies the feature as involving a user-facing generative AI experience.

The announcement states that the change includes an administrative control that can be managed through group membership. Organizations should therefore consider the taskbar configuration alongside their existing policies for Copilot access, identity, permissions, training, and AI governance.

The taskbar pin itself does not determine every aspect of Copilot access, but it does affect how prominently the application is presented to users.

For organizations with formal AI adoption programs, that makes the setting potentially relevant to their broader deployment and governance processes.

What IT Teams Should Check Now

Organizations preparing to use the new control can review a few practical items before configuring it:

Review existing Copilot installation: Confirm that the app is installed on the Windows devices that will be targeted.
Define deployment groups: Decide whether groups should be organized around pilots, departments, functions, or another strategy.
Check administrator permissions: Confirm that the person managing the setting has an Intune Administrator or Global Administrator role.
Review onboarding plans: If Copilot is being introduced gradually, align taskbar pinning with the organization’s training and adoption schedule.
Plan expansion: Determine when additional groups should receive the pinned application.

These steps can help prevent the taskbar setting from being treated as a standalone deployment mechanism.

Rollout Begins in Late September 2026

Microsoft says worldwide General Availability begins in late September 2026, with the rollout expected to complete by late September.

For administrators, that means the new control is arriving during the current September 2026 deployment window rather than as a feature scheduled for a later release.

Organizations that manage Windows through Intune can therefore begin checking the Microsoft 365 admin center for the new Copilot setting as the rollout reaches their tenant.

What Comes Next for Copilot Administration

The update reflects a broader shift toward more granular controls for workplace AI deployments.

Rather than forcing organizations to treat Copilot availability as a single organization-wide configuration, group-based taskbar pinning gives IT teams a way to connect the Windows desktop experience with existing user-group structures.

The immediate change is limited to taskbar pinning: it does not install the Copilot app. But for organizations already deploying Copilot, the ability to target specific groups could become a useful part of phased rollout planning.

As Microsoft continues expanding Copilot across Microsoft 365 and Windows, administrators will likely need to manage not only whether employees have access, but also how and when AI tools are introduced into their daily workflows. This new setting adds another control to that administrative toolkit.