Posted inPower Platform

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

5 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 AdminsMicrosoft 365 AdminsIT ManagersService OwnersDevelopers
Why this score?
AI Confidence
HIGH
Enough detail is available to trust this assessment.
Assessment Reasoning
This update confirms revised replacement models for two GitHub Copilot harness entries and retention of prior migration dates. Tenant admins and makers must review affected agents, test new models, and validate integration and workflow behaviour before the November 12, 2026 migration. Impact is substantial because model changes can alter output quality and require testing and communication, though user-facing impact remains moderate and largely indirect.
70
🛡️ Admin Impact
HIGH
40
👥 User Impact
MEDIUM
60
⚡ Urgency
HIGH
65
🔧 Effort
HIGH
ℹ️ WHAT YOU NEED TO KNOW
📌

AT A GLANCE

Several AI models in Copilot Studio will retire soon. Affected agents will migrate automatically to new models after November 12, 2026, so it’s worth checking which ones use retiring versions.
👥

END USERS

Users may notice updated behaviour or responses from agents after the planned migration.
🛡️

IT ADMINS

Review agent configurations before migration, notify owners, and test replacement models to confirm performance and accuracy.
📅

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: table, td, tr, th {border: 1px solid #243a5e; border-collapse: collapse;} th {text-align: center; background-color: #243a5e; color: #fff;}
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-6 Luna (previously GPT-5.6 Terra)November 12, 2026
GPT-5 AutoStandardGPT Chat LatestNovember 12, 2026
GPT-5 ReasoningStandardGPT Chat LatestNovember 12, 2026
GPT 5.6 SolGitHub CopilotGPT-6.1 Sol (previously GPT-6 Sol)November 12, 2026
GPT 5.6 LunaGitHub CopilotGPT 6 LunaNovember 12, 2026

Note: For environments outside the U.S. where cross-geo data movement is restricted, 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.

Update to planned replacement models
The planned replacement models for two GitHub Copilot harness models have changed since the original announcement:
  • GPT-5 Chat: The planned replacement is now GPT-6 Luna, previously GPT-5.6 Terra.
  • GPT-5.6 Sol: The planned replacement is now GPT-6.1 Sol, previously GPT-6 Sol.
We’ve updated the planned replacement models to provide improved quality at a lower cost. All other planned replacement models and migration dates remain unchanged.

GPT Chat Latest
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. Moving to a new 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.

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: