Microsoft recently announced that it will stop automatically installing the Microsoft 365 Copilot app on devices with Microsoft 365 desktop clients. This move affects IT strategy and administration, requiring a new approach to managing deployments. This article breaks down the change, its implications, and offers guidance for IT professionals.
What Changed
Microsoft has decided to stop auto-installing their Copilot app on systems running Microsoft 365 desktop clients. Previously, the application was silently added, creating challenges in managing unwanted software and network resources.
Why It Matters
The cessation of forced installs offers IT administrators more control over software deployments. It reduces unintended bandwidth usage and aligns software installations with organizational policies.
Impact on Organizations
Organizations will see a change in how Microsoft 365 Copilot is deployed and managed. Key considerations include:
- Reduced need for post-installation audits
- Decreased network traffic from unplanned downloads
- Increased compliance with software deployment policies
What to Do Next
Here’s what IT administrators should consider doing:
- Review Microsoft 365 setup and deployment procedures
- Coordinate with end-users on application access needs
- Establish a policy for manual installation where necessary
Potential Issues and Solutions
Potential issues include user requests for manual installations and troubleshooting deployment inconsistencies. Solutions involve maintaining clear communication and establishing a streamlined request process.
Command Line Examples
Here are some useful commands for managing the Microsoft 365 Copilot app:
Get-Command Copilot
Remove-AppxPackage -Name Microsoft.Copilot
Sources
For more information, visit: BleepingComputer.
Transparency Note: This article was assisted by AI, with source verification through automated tools, ensuring accuracy and reliability without human biases.