Posted inPower Platform

MC1506318: Copilot Studio Ends Support for Selected AI Models and Migrates Agents to Replacement Models

4 minutesPosted inPower Platform
MWPRO IMPACT SCORE
OPERATIONAL IMPACT
61
0 25 50 75 100
HIGH IMPACT • REVIEW RECOMMENDED
Recommended Action:
Review the update and plan any required actions before rollout.
▶ What is MWPro Impact Score? Watch our 60‑second explainer

Primary Audience

Power Platform AdminsIT ManagersService OwnersDevelopersTenant Admins
Why this score?
AI Confidence
HIGH
Enough detail is available to trust this assessment.
Assessment Reasoning
The notice sets out confirmed retirement and automatic migration of several AI models used in Copilot Studio by November 2026. Admins need to identify affected agents, test replacement models, and verify workflows and integrations before the change. User disruption is indirect, as migration is automated, but agent behaviour may shift. The timeline allows planning, but preparation and coordination with agent owners are required.
72
🛡️ Admin Impact
HIGH
38
👥 User Impact
MEDIUM
60
⚡ Urgency
HIGH
65
🔧 Effort
HIGH
ℹ️ WHAT YOU NEED TO KNOW
📌

AT A GLANCE

Support is ending for several AI models in Copilot Studio. Affected agents will automatically migrate to replacement models from 12 November 2026.
👥

END USERS

Users may notice agents using updated models after migration.
🛡️

IT ADMINS

Identify agents using retiring models, notify owners, and test replacement models before migration.
📅

ROLLOUT TIMELINE

Upcoming:
November 2026

📢 Official Microsoft Message Center Announcement

Copilot Studio – Information regarding the end of support for selected AI models
Message ID: MC1506318 (Updated)
We are announcing the end of support for selected AI models on the Standard and GitHub Copilot harnesses in Copilot Studio. Beginning on each models’ applicable migration date, the selected models will no longer be available in Copilot Studio, and agents will automatically migrate to a replacement model.

How does this affect me?
Agents configured with retiring models will be automatically migrated to a supported replacement model. The planned replacement model and migration date depends on both the model and the harness used by the agent.

Review your agents by harness and model to identify those using a retiring model, then work with their owners to prepare for migration.

For the latest model availability, see the guidance for your agent’s harness:
Retiring model Harness Planned replacement model Migration date
GPT-4.1*StandardGPT Chat LatestNovember 12, 2026
GPT-4.1 MiniStandardGPT Chat LatestNovember 12, 2026
GPT-5 Chat*StandardGPT Chat LatestNovember 12, 2026
GPT-5 Chat*GitHub CopilotGPT 5.6 TerraNovember 12, 2026
GPT-5 AutoStandardGPT Chat LatestNovember 12, 2026
GPT-5 ReasoningStandardGPT Chat LatestNovember 12, 2026
GPT 5.6 SolGitHub CopilotGPT 6 SolNovember 12, 2026
GPT 5.6 LunaGitHub CopilotGPT 6 LunaNovember 12, 2026

*Note: For U.S.-based tenants with cross-geo data movement enabled, GPT-4.1 and GPT-5 will remain supported and will not retire as part of this migration. To learn more about cross-geo data movement, including availability and eligibility, see Geographical availability of Copilot.

GPT Chat Latest is the supported chat model option going forward for the Copilot Studio Standard harness. It keeps agents on the latest supported GPT chat model as snapshots within the current major model version are updated over time. Moving to a new major model version is a separate change, and customers will receive at least 30 days’ notice.

For agents on the GitHub Copilot harness, refer to the planned replacement model listed in the table above.

Choose the model that best fits your agent
You can use the planned replacement or choose a supported model that better meets your agent’s quality, performance, or cost needs.

Model availability depends on your harness, region, and administrator settings. Use the guidance for your agent’s harness: Please test your agent on the model you choose before migration begins.

What action do I need to take?
Before the migration date for each retiring model, we recommend admins and makers take the following actions:
  1. Identify affected agents in the Power Platform admin center by going to Manage > Copilot Studio and reviewing agents by harness and model.
    • The model field is currently in preview. The inventory reflects published agent configurations, so unpublished model changes might not appear. See the admin agent inventory for details.
  2. Notify the appropriate agent owners.
  3. Test the planned replacement model, or choose another supported model that better meets quality, performance, or cost requirements.
  4. Validate response accuracy, key workflows, tool and action execution, and business-critical integrations.
  5. Adjust agent instructions or configuration if testing identifies behavior changes.
  6. Review model availability, regional availability, and any cross-geo or external model-provider requirements.
We will send an announcement with retirement dates for older versions of the Claude Opus and Claude Sonnet models. In the GitHub Copilot harness, Opus 5.5 and Sonnet 5.5 are already available for your agents.

For more information, please visit:
Tags: