Deploy the unified Microsoft Copilot application

Note

The Microsoft 365 Copilot app is now called Microsoft Copilot. If you previously used the Microsoft 365 Copilot app for work, look for the updated name and icon. Your experience is the same.

Microsoft Copilot application unification updates existing Microsoft Copilot and Microsoft 365 Copilot app installations to a single Copilot application experience. Use this article to prepare managed devices, configure the required deployment policies, and plan rollout across Windows and Mac devices.

Note

Ensure that copilot.cloud.microsoft isn't blocked within your environment. For more information, see Microsoft 365 app and network requirements for Microsoft Copilot, and Add Microsoft Copilot endpoints to your allow list.

Test the unified Copilot application on devices

Use the following instructions to deploy the unified Copilot app for Windows and Mac devices.

Windows devices

  1. Ensure EdgeUpdate is on version 1.3.253.25 or higher.
  2. Download the Copilot update policy file.
  3. Enable the Updater Experimentation And Configuration Service Control policy.
    1. On devices that already have the Microsoft Copilot application or the Microsoft 365 Copilot application installed, enable 1 on the Copilot Unification Allowed policy.
    2. On devices without the Copilot application installed, set the Install policy to Force Installs.

Mac devices

  1. Download the latest macOS installer package (.pkg).
  2. Deploy via Mobile Device Management (MDM) (Intune, Jamf, or other MDM Solutions)
    1. Create an application deployment policy in your MDM solution
    2. Upload the downloaded .pkg installer package.
    3. Assign the deployment only to the devices that you want to participate in the Unified App opt-in program.
    4. Monitor deployment progress and installation status through your MDM.

For deploying via Microsoft Intune, see Add macOS Line-of-Business (LOB) Apps to Microsoft Intune.

Note

If you have the AutoUpdateCheckPeriodMinutes policy set to 0, you won't be able to preview the updated unified Copilot application.

Prepare for broad rollout of the unified Microsoft Copilot application

Customers can begin adopting the updated Microsoft Copilot application during the initial availability phase. Starting in September, Microsoft will begin the broad rollout to commercial customers. To prepare for either phase, verify that your network allows access to the Microsoft Copilot endpoints.

We recommend reviewing the new Copilot policies and configuring your devices before deployment.

Note

Microsoft Copilot isn't currently supported in special cloud environments.

Windows prerequisites

During the initial availability phase, organizations can control when devices receive the updated Microsoft Copilot application by enabling the Copilot Unification Allowed policy. If your organization has limited bandwidth, we recommend a staged deployment to avoid a large number of devices downloading the package simultaneously.

Once Microsoft begins the broad rollout, you can continue to manage deployment manually or allow Microsoft to progressively roll out the update by enabling the Updater Experimentation And Configuration Service Control policy. If neither approach is used, devices with an existing Copilot app may download the package automatically as Microsoft completes the rollout.

If you want to prevent installation of the updated Microsoft Copilot application on Windows devices, set the Pause Copilot App Unification Rollout registry key.

Users can install Copilot from the Microsoft download site or the Microsoft Store. Offline Windows Installer (.msi) packages will also become available as the rollout expands. If you want to prevent user-initiated installations, configure your network, devices, and installation policies accordingly. You can configure the install policy to prevent user driven installation.

Additional resources

  • Last updated on