HANDS ON SharePoint
HANDS ON Teams
HANDS ON Lists
HANDS ON tek
M365 Admin
Microsoft Copilot in Microsoft Teams: Improved time-based responses in chat and channels
Microsoft Teams is enhancing Copilot’s ability to understand and respond to time-related queries, providing more accurate answers for terms like “yesterday” or “last month.” This feature requires a Copilot for Microsoft 365 license and will roll out in July 2024, with no admin action needed.
Coming soon to Microsoft Teams: Improvements to how Copilot in Teams understands and responds to time-related queries in chat and channels. With this rollout, Copilot will provide more precise and relevant responses to prompts such as “yesterday,” “last week,” and “last month.” A Microsoft Copilot for Microsoft 365 license is required to use this feature.
This message applies to Copilot in Teams chat and channels on Desktop, Mac, and the web in new Teams, as well as Teams Mobile (iOS and Android).
This message is associated with Microsoft 365 Roadmap ID 397768.
When this will happen:
Targeted Release: We will begin rolling out early July 2024 and expect to complete by mid-July 2024.
General Availability (Worldwide): We will begin rolling out mid-July 2024 and expect to complete by late July 2024.
How this will affect your organization:
Before this rollout, when users asked Copilot about a long time period (such as “Summarize the key action items from March”), Copilot was limited to the last 30 days of data (left side of screenshot). After the rollout, Copilot will be able to detect and respond to the specified time period (such as March). We have also simplified the timestamp (right side of screenshot):
The default state is on, and all Copilot licensed users will have access to the improved feature.
What you need to do to prepare:
This rollout will happen automatically by the specified dates with no admin action required before the rollout. You may want to notify your users about this change and update any relevant documentation as appropriate.
Before rollout, we will update this post with revised documentation.
Message ID: MC801583
