Microsoft 365 Copilot: Prepare for meetings with Copilot in classic Outlook for Windows [MC1228331]

Message ID: MC1228331

[Introduction]

We are bringing the Prepare for a meeting with Copilot capability to classic Outlook for Windows. This feature allows users with a Microsoft 365 Copilot license to access meeting‑related context—such as documents, communications, and tasks—directly from the Outlook Calendar. Users can also chat with Copilot to review or explore additional meeting details as needed. This capability is available only to users with a Microsoft 365 Copilot license.

This message is associated with Microsoft 365 Roadmap ID 542186.

[When this will happen]

• Public Preview: We began rolling out in late January 2026 and expect to complete by late February 2026.
• General Availability (Worldwide): We will begin rolling out in early March 2026 and expected completion by late March 2026.

[How this affects your organization]

Who is affected: Users of classic Outlook for Windows who have an active Microsoft 365 Copilot license.

What will happen

A new Prepare for a meeting with Copilot option will appear in the Calendar module. Users will be able to access it in two places:

• From the Copilot menu in the meeting window: 

  

• By right‑clicking an upcoming meeting in the calendar:

   

Copilot will present meeting‑related information pulled from existing Microsoft 365 sources (email, documents, and tasks).

The feature is on by default for licensed users.

There is no change for users without a Copilot license.

No admin configuration changes or new policy controls are introduced.

[What you can do to prepare]

• Confirm that users who need this capability have an active Microsoft 365 Copilot license.
• Update internal support materials if your helpdesk references meeting‑preparation workflows.
• If your organization does not want users to access this feature, remove the Copilot license from those users.
• Ensure users are running the latest build of classic Outlook for Windows.

[Compliance considerations]

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

Source: Microsoft

Latest Posts