Microsoft’s July 2026 update for Microsoft 365 Copilot delivered over 40 distinct changes, marking one of the platform’s most significant expansion points since its launch. The headline features: Copilot Cowork is now generally available for enterprise customers, Anthropic’s Claude joins as an alternative model inside Copilot Chat, and IT administrators gain granular auto-install controls that reshape how Copilot lands on end-user machines.

What shipped in the July 2026 update

On July 14, 2026, Microsoft pushed a cumulative update to Microsoft 365 Apps that activated a broad set of Copilot capabilities for users on the Monthly Enterprise Channel. While the full change log remains unpublished, the three most impactful changes stand out:

Copilot Cowork reaches general availability

First previewed at Microsoft Build 2026, Copilot Cowork moves collaborative AI from limited trials to production. The feature lets multiple users interact with a shared Copilot session inside Word, Excel, and PowerPoint, enabling real-time co-authoring with AI assistance. A team drafting a proposal can now prompt Copilot collectively—asking for data analysis, content generation, or tone adjustments—while seeing each other’s inputs and the AI’s responses in a shared sidebar. Microsoft confirmed that Cowork respects existing sensitivity labels and data loss prevention policies, with all conversations staying inside the tenant boundary. Cowork requires an additional license: it is included in the Microsoft 365 E5 Copilot suite but costs $12 per user/month as an add-on for E3 plans.

Claude as a model option in Copilot Chat

Users with active Microsoft 365 Copilot subscriptions can now switch between OpenAI’s GPT-4o and Anthropic’s Claude model directly within the Copilot Chat pane in desktop and web apps. The toggle appears under a new “Model” dropdown in the chat header. According to Microsoft’s announcement, the Claude option delivers longer context windows and a different reasoning style that some organizations may prefer for tasks like contract review or lengthy document summarization. The feature is available immediately for all licensed Copilot users; admins can restrict model choice via new policies in the Microsoft 365 admin center.

A quiet but operationally significant change gives IT admins the power to pre-configure automatic installation of Copilot-related add-ins and runtime components across their fleet. Previously, each user had to manually enable Copilot from the app ribbon or their account settings. With the July update, a new Group Policy object and Intune configuration profile allow pushing the Copilot button, the chat pane, and backend services to all licensed users without user interaction. To balance governance, Microsoft introduced accompanying policies that let admins define which Copilot features are auto-installed, set opt-out prompts, and schedule rollout rings.

Other notable updates

Beyond the headliners, the 40-plus changes include refinements to Copilot’s grounded search accuracy, better integration with Microsoft Graph connectors, a new Excel formula assistant, enhanced email summarization in Outlook, and a set of fresh admin controls for data residency and model usage reporting. Developers also gained new Copilot extensibility endpoints, with the SDK now supporting Claude as a model target for building custom agents.

What the changes mean for you

For everyday users and information workers

If your organization has already rolled out Copilot, the Claude toggle will appear the next time you open the Copilot Chat. For many, the ability to choose a model is a welcome addition, especially for tasks where Claude’s writing style or extended context handling feels more natural. Cowork transforms collaborative editing: instead of one person driving the AI while others watch, the whole team can steer Copilot together. Early adopters note that Cowork requires a brief onboarding session to avoid confusing overlapping prompts; Microsoft provides a 5-minute in-app tutorial. When a team member initiates a Cowork session, others see a notification and can join, with each participant able to see and refine prompts in real time.

For IT administrators and governance teams

The auto-install capability solves a significant adoption headache, but automatic deployment raises compliance and change management questions. Microsoft’s admin center now includes a “Copilot deployment” dashboard where you can:

  • Set a phased rollout by user groups.
  • Pre-select which model is default (GPT-4o or Claude) for your tenant.
  • Define whether Cowork is available to everyone or only specific teams.
  • Monitor license usage and adoption metrics in real time.

Crucially, you can delay auto-install and instead notify users that the feature is available, preserving their choice. If your organization operates in heavily regulated industries, review the updated Data Protection Impact Assessment (DPIA) documents Microsoft published alongside this release—particularly around how Claude handles data retention, as it differs from OpenAI’s default contracts.

For developers and ISVs

The July update introduces new Copilot extensibility endpoints. Developers building Copilot plugins or connectors should note that the SDK now supports Claude as a model target, enabling agents that leverage Claude’s specific retrieval-augmented generation nuances. Additionally, the general availability of Cowork opens APIs for building multi-user AI experiences into line-of-business applications. Microsoft has updated the Microsoft 365 developer portal with sample code and a test tenancy configuration that simulates multi-user Copilot sessions.

How we got here: the road to multi-model and shared AI

Microsoft’s move to embed a non-OpenAI model inside Copilot has been telegraphed for months. At Build 2026, CEO Satya Nadella announced a “model-agnostic Copilot,” revealing a multi-year deal with Anthropic. The rationale: offer customers choice and mitigate dependency on a single model provider, mirroring Google’s similar strategy in Workspace and the broader enterprise trend of avoiding vendor lock-in around AI.

Copilot Cowork emerged from internal research on collaborative intelligence. During the private preview that started in April 2026, Microsoft observed a 40% productivity lift in team document scenarios compared to solo Copilot use. The feature leans heavily on the Fluid Framework for real-time synchronization.

Auto-install policies grew out of feedback from IT pros who found the previous manual-enable process cumbersome for large rollouts. In its May 2026 tech community blog, the Copilot product group hinted at “deployment enhancements” coming in Q3—the July update is the concrete output.

What to do now

If you’re an IT administrator:

  1. Audit your Copilot licenses and assign the Cowork add-on where appropriate. Check the Microsoft 365 admin center under Billing > Licenses.
  2. Review and configure model choice policies. Navigate to Settings > Org settings > Copilot > Model selection. You can enforce a tenant default, allow user choice, or disable Claude entirely.
  3. Plan your auto-install rollout. Use the Copilot deployment dashboard to create ring deployments. Microsoft recommends starting with a pilot group of early adopters, monitoring for performance impact (especially on older hardware), and then expanding in waves.
  4. Update your data governance documentation. Because Claude processes data under Anthropic’s privacy terms, ensure your data protection officer reviews the new DPIA and updates any internal AI usage policies.
  5. Communicate the changes to users. Even with auto-install, users need to know what’s new. Microsoft provides an email template and a short video in the adoption content pack.

If you’re a user:

  • If the Copilot button appears in your Office apps and you’re unsure, it means your admin has opted into auto-install. You can hide it under File > Options > Copilot.
  • Experiment with Claude for long-form or nuanced tasks. Switch models via the dropdown in Copilot Chat and try the same prompt on both to see which suits your workflow.
  • For Cowork, coordinate with your team: designate a lead prompter to start, then allow others to refine. Because responses are visible to everyone, avoid including sensitive personal data unless your admin has confirmed that Cowork sessions are ring-fenced.

Outlook

Microsoft’s July 2026 update signals a broader Copilot trajectory: less of a monolithic AI assistant and more of a customizable, collaborative platform. Rumors already point to a “bring your own model” capability by year-end, which would let enterprises plug in fine-tuned open-source models via Azure AI. The auto-install feature represents Microsoft’s quiet push toward making AI an ambient, always-on layer in productivity tools—mirroring the earlier transition from optional spell-check to omnipresent assistance. For Windows administrators, the governance implications are profound: soon, managing AI will be as routine as managing security updates. The tools are arriving; the policies need to follow.