Microsoft Copilot Sept 2026 Highlights

Key insights

• Home, Code, Autopilot — Microsoft combined chat, app building, and a persistent agent into one Copilot workspace.
  Office apps (Word, Excel, PowerPoint) now open and edit inside Copilot for faster workflows.
• GPT-6.1 Sol and other new models rolled out in September 2026, including Claude Sonnet 5.5.
  Some models are included with a Copilot license in Word, Excel, PowerPoint and Chat, while usage limits and credit billing apply in other Copilot areas.
• Plugin registry replaces Agents in the Copilot UI and turns advanced agents into governed plugins.
  Admins must decide who can upload advanced agents and plugins by October 25 to control scope and governance.
• Copilot Credits now bill new services such as Copilot in SharePoint, OneDrive and Teams Phone.
  Spending policies apply to these services by default, so cost controls may start affecting users immediately.
• Entra Agent ID migration and subprocessor settings (OpenAI, Anthropic, SpaceXAI) affect which models your users receive.
  Admins should verify migrations and subprocessor choices to ensure compliance and expected model access.
• Admin checklist: review spending policies, control plugin uploads, confirm Entra Agent ID migration, and update governance before year-end.
  For users, expect less app switching, more in-Copilot editing, no-code app building, and Autopilot handling ongoing tasks.

Overview of the September 2026 Copilot update

The YouTube video by Nick DeCourcy (Bright Ideas Agency) summarizes Microsoft’s September 2026 changes to Microsoft 365 Copilot. The update repositions Copilot as a unified workspace and introduces three headline experiences called Home, Code, and Autopilot. Together, these aim to combine chat, productivity apps, and persistent agents into one interface instead of treating Copilot like a separate chatbot. As a result, users will see tighter integration with Office apps and new ways to build solutions without traditional coding.

The video outlines that Word, Excel, and PowerPoint now appear inside the Copilot environment as editable outputs rather than static drafts, which should reduce context switching. Meanwhile, the Code layer targets people who want to create lightweight tools and automations from natural-language prompts. Finally, Autopilot acts as a persistent cloud agent that can continue tasks and follow up even when a user logs off. These changes reflect a shift toward an AI work surface rather than a single assistant window.

New models and billing mechanics

September saw Microsoft add seven new models to the Copilot ecosystem, including GPT-6.1 Sol and Claude Sonnet 5.5, and it introduced mixed model routing based on subprocessor settings. Some models are included with a Copilot license for interactive use in Word, Excel, PowerPoint and Chat, while other scenarios such as Cowork and Copilot Studio consume billed Copilot Credits. This split means organizations must balance included usage against pay-as-you-go operations to control costs and performance.

Importantly, Microsoft now uses subprocessor selections for OpenAI, Anthropic and SpaceXAI to decide which models are available to users. That creates a governance lever but also a tradeoff: choosing specific subprocessors may give access to higher-performance models but could affect compliance and data residency choices. Administrators should therefore weigh model quality against regulatory and contractual constraints when setting these options for their tenants.

Agents, plugin registry and governance choices

One prominent change covered in the video is that Agents in Copilot are transitioning to a new plugin registry experience in the Copilot UI, and administrators must decide who can upload advanced agents and plugins by the October 25 deadline. The plugin registry centralizes discovery and governance but forces admins to set permissions, which creates a governance burden for organizations that want flexible innovation. In other words, the registry improves control and visibility while adding a requirement for clearer policy decisions.

Additionally, Copilot Studio agents began migrating to Entra Agent ID automatically, a move that strengthens identity and access controls. However, this migration requires testing and potential configuration work to ensure existing agents keep functioning. Organizations that delay will risk surprises, so administrators should plan the migration and inform stakeholders to avoid disruption.

Spending policies, SharePoint and Teams Phone integrations

The video stresses that spending policies are a high-priority admin item because new services — notably Copilot in SharePoint, Copilot in OneDrive and Teams Phone Agent — now consume Copilot Credits and will be included in spending policies by default. This default setting can cause unanticipated charges unless admins adjust policies to reflect organizational budgets and priorities. Consequently, balancing open access for users with cost control is a key tradeoff for every tenant.

Admins must also review auto-apply rules for new Copilot services, since default behavior may enable billable features without explicit approval. Preparing for the end of the year means auditing current usage, setting sensible spending caps, and communicating changes to finance and business owners. Failure to act could lead to unexpected spend that is difficult to trace across multiple teams and services.

Adoption tradeoffs and practical challenges

While the unified Copilot experience promises productivity gains, the video highlights several adoption challenges such as governance, training, and model variability. Organizations must balance faster workflows against the need for clear policies on what agents and plugins can access corporate data, and they should plan training to help users get value without creating security gaps. Moreover, different models behave differently, so teams should test outputs before relying on them in business processes.

Finally, the move toward embedded Office editing and no-code app creation lowers barriers for business users but raises questions about maintainability and support. Casual creators may produce useful tools quickly, yet IT and security teams must manage lifecycle, backups, and compliance for these artifacts. In short, the changes offer major potential gains but demand coordinated policy work, testing, and training to realize benefits safely.

Keywords

microsoft copilot september 2026, microsoft copilot updates 2026, copilot new features september 2026, copilot microsoft 365 update 2026, microsoft copilot pricing changes 2026, copilot ai improvements september 2026, copilot release notes september 2026, microsoft copilot roadmap 2026