MC1251203: Copilot extensibility: Microsoft 365 Copilot Declarative Agents model upgrade to GPT‑5.2

Microsoft 365 Copilot Declarative Agents will upgrade to the GPT-5.2 model by late March 2026, enhancing quality, accuracy, and multi-step workflows. No configuration changes are needed; users should inform builders, validate key workflows, and monitor agent behavior. No compliance issues identif...

[Introduction]

Microsoft 365 Copilot Declarative Agents are being upgraded to the GPT‑5.2 model. This update improves quality and reliability for agent scenarios such as reasoning, multi‑step workflows, tool calling, structured output generation, and document analysis. As with GPT‑5.1, users can continue to choose between Auto, Quick Response, and Think Deeper modes.

[When this will happen]

General availability (Worldwide): Rollout will begin around mid-March 2026 and is expected to complete by late March 2026.

[How this affects your organization]

Who is affected

  • Users and builders of Microsoft 365 Copilot Declarative Agents in all Microsoft 365 tenants

What will happen:

  • Declarative Agents will begin using the GPT‑5.2 foundational model.
  • Users may notice improved quality, accuracy, and formatting in responses.
  • Some agent behaviors may vary slightly due to model differences.
  • The update will roll out gradually; not all users will receive the new model at the same time.
  • No admin controls are changing, and existing settings continue to apply.

[What you can do to prepare]

No configuration changes are required. To support a smooth transition, consider the following steps:

  • Inform agent builders that the model upgrade is rolling out.
  • Validate your organization’s most important agent workflows (for example, top 5–10 prompts or use cases).
  • Check that agents continue to meet expectations for accuracy, tone, and formatting.
  • Monitor agent behavior and submit feedback through the thumbs up/down feature.
    • Include #GPT52 when reporting issues or successes.

[Compliance considerations]

No compliance considerations identified. Review as appropriate for your organization.