| (Updated) Update to agents in SharePoint: Simpler launch experience and new site AI settingsCategory:SharePoint Online
Microsoft Copilot (Microsoft 365)Nummer:MC1315219Status:planForChange | Updated June 22, 2026: We have updated the content. Thank you for your patience. [Introduction] We’re updating how agents in SharePoint work to provide a simpler experience for agents selected on a site. As a refresher, Get started with agents in SharePoint – Microsoft Support, there are two types of agents in SharePoint: - Ready-made agent – Every SharePoint site comes with a “ready-made agent”, automatically scoped to the content on that site. These agents, scoped to the SharePoint site, require no building from site admins or site owners.
- Custom-built agent – With site editing permissions, you can create custom agents with a specific content scope, identity, and behavior.
With this update, we’re introducing a new Site AI settings to give site owners more control over which agents are highlighted on their sites. Approved agents will no longer appear in the Agent Picker, so these agents should be placed directly on the site page for better discoverability. There is also a change to who can create custom-built agents from SharePoint. The “Create an agent” menu option is only available to users with the M365 Copilot License. SharePoint Agent Pay-As-You-Go covers consumption usage for custom-built agents only. [When this will happen] General Availability (Worldwide): We began rolling out in mid-November 2024 and expect rollout to complete by mid-June 2026 (previously early June). [How this affects your organization] Who is affected - All Microsoft 365 tenants using SharePoint Online
- Site owners and content authors managing how custom agents are discovered on their site
What will happen - Site owners will manage the site’s “Default” agent through the main agent setting in the new Site AI settings panel in SharePoint site settings.
- For existing sites, the current “Default” agent will automatically become the site’s main agent.
- For new sites, the main agent will be the ready-made agent
- Users no longer access approved agents through the agent picker and overflow menu in the chat pane. All approved agents remain in the Site Assets\Copilots\Approved folder.
- To help users discover agents, site owners and builders should surface agents directly on pages using supported web parts or shared agent links.
- Users with SharePoint Agent Pay-As-You-Go access only will no longer see the New Agent or “AI Actions -> Create an agent” menu options. Create an agent in SharePoint | Microsoft Support
This feature is on by default and does not require tenant-level configuration changes. [What you can do to prepare] No immediate admin action is required. We recommend the following preparation steps: - Ask site owners and builders to review the approved agents on their sites in the Site Assets\Copilots\Approved folder.
- Encourage site owners to add or update agent links on pages using supported web parts, such as: Agent Link web part, Editorial Card web part, and adding shared .agent file links in Text web part
- Inform users that agents they recently used can be found in:
- Build “Owned by me” section by choosing the Agents filter,
- OneDrive web Home > Recent view (filterable by agent), or
- Microsoft 365 Copilot agents list
Learn more: [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization.
|
| (Updated) Microsoft 365 Copilot app: Simplified, chat-centered experienceCategory:Microsoft Copilot (Microsoft 365)
Microsoft 365 Copilot ChatNummer:MC1325422Status:planForChange | Updated June 22, 2026: We are starting rollout of the updated Microsoft 365 Copilot app experience to worldwide audiences. This updated experience was previously rolled out to Frontier audiences in May. The worldwide rollout will begin standard release on June 22. Users will see a “New Copilot” toggle in the top right of their app that lets them switch between the current experience and the updated experience. The updated experience will be turned on by default. This toggle gives users control to: - Switch back at any time if it doesn’t meet their needs
- Share feedback when they switch back to help us improve
- This is a temporary opt-out experience as we roll out updates and learn from feedback.
On July 15 for standard release, the toggle will be removed and the updated experience will be default on without the option for users to switch back to the previous experience. On August 22, the updated experience will start rolling out worldwide for deferred release. [Introduction] We are introducing updates to the Microsoft 365 Copilot app that deliver a more streamlined, chat-centered experience. These updates simplify the chat and response layout, improve navigation, and introduce new ways for users to organize work—helping them stay focused, maintain context, and move work forward efficiently. [When this will happen] - Frontier: Available now
- Generally available with opt-out toggle: Available now
- Generally available, no opt-out toggle: July 2026
- Generally available, deferred release: August 2026
[How this affects your organization] Who is affected - All users accessing the Microsoft 365 Copilot app on the web or desktop
- Applies to Microsoft 365 Copilot (Premium) and Copilot Chat (Basic) tenants
What will happen Throughout the Copilot app, experiences have a new, cleaner look with simplified headers and text input components. In addition, users will see the following updates: Streamlined navigation - The navigation pane has a new pinned section where users can pin frequently used agents, apps, and Copilot experiences (like Notebooks, Microsoft 365 apps, chat conversations, etc.) directly in the navigation pane for easy access.
- The app launcher moves to the waffle menu in the top right of the expanded navigation pane where users can access apps and experiences like Create, Notebooks, Outlook, Teams, Word, Excel, PowerPoint, and custom apps. Some users in an early test group may have already seen this change roll out a few weeks prior.
- The agents section in the navigation pane is simplified to a flyout menu, where users can hover over to see their pinned and recently used agents, as well as access agent store and agent builder. Users can also select the agents label to open the agent store directly.
- The new Tasks tab in the navigation pane opens a consolidated view of the user’s long-running Copilot activity, including scheduled chats and agent activity, so they can easily track autonomous Copilot tasks and take action when needed.
- Users can collapse the Copilot app navigation pane by selecting the icon in the top left corner of the pane (“collapse navigation” text string appears when the user hovers over the icon).
Chat update - Work and web grounding controls are consolidated into a single “Work IQ” toggle in the upper-left corner of the chat screen. Work IQ is enabled by default and combines enterprise data with web grounding to provide more complete responses. Users can turn off Work IQ to disable enterprise data tools and switch to web-only grounding. When Work IQ is turned off, prompt suggestions and the CIQ menu are limited to web-based suggestions, and the Sources menu is disabled. Agents continue to function as usual.
- The Copilot Chat layout has been simplified with a rich prompting canvas that preserves formatting when pasting content, refreshed prompt suggestions and header text, and a streamlined menu for adding content, agents, and images.
- Copilot Chat response’s structure is clearer for more scannable information, citations, and more relevant suggested actions.
Agent update - When a user opens an agent from the agent flyout menu in the navigation pane or from the Agent Store and lands on the agent home screen, they will see details about where the agent came from, including a profile card of the agent maker and tooltips alongside the organization name. The ghost text in the agent chat input includes the agent’s name to clearly show that the interaction is with the agent.
These updates will roll out to all Microsoft 365 users with access to the Copilot app. Default behavior - When these updates roll out to Frontier users, the new experience will be their default experience. This allows Microsoft to generate sufficient feedback to inform decisions impacting full GA deployment.
- When these updates roll out to worldwide users in June, the new experience will be available via an opt-in toggle. The experience will be disabled by default.
- In July, these features will become available by default for all users. The opt-in toggle will be removed at this time.
Screenshot 1 – Microsoft 365 Copilot app home screen view: 
Screenshot 2 – Microsoft 365 Copilot app home screen with expanded navigation view: 
Screenshot 3 – Chat response in Copilot app view:  [What you can do to prepare] No action is required to enable this change. To prepare for these changes, we recommend that administrators: - Inform users about the updated Copilot app experience
- Share updated Microsoft support documentation (https://support.microsoft.com/Microsoft-365-Copilot/what-is-the-microsoft-365-copilot-app) with users when it has been updated with the new experience in June (aligned to when the updates roll out to general audiences).
- If applicable, update internal guidance and training materials to reflect changes to navigation, chat experience, and where users access key capabilities.
- If participating in preview programs (e.g., Frontier), validate the experience in your environment and provide feedback to help shape final GA
Learn more: [Compliance considerations]
| Consideration |
Impact |
Notes |
| |
|
| Changes how data is processed/accessed |
Yes |
Expanded use of Copilot across chats, agents, and workspaces |
| Introduces/modifies AI/ML interactions |
Yes |
Increased agent orchestration and chat-based workflows |
| | |
| New generative AI interactions |
Yes |
Deeper chat-centric creation and agent-driven actions |
|
| (Updated) Scoped SharePoint search in Teams (SharePoint app, also called Viva Connections)Category:SharePoint Online
Microsoft TeamsNummer:MC1332816Status:stayInformed | Updated June 22, 2026: We have updated the timeline. Thank you for your patience. [What and Why:] We’re improving search behavior when users use the SharePoint app inside Microsoft Teams. When users search from Teams while they’re in the SharePoint app (also known as Viva Connections), search results and suggestions will be scoped to SharePoint content, helping users find relevant information faster without leaving Teams. This message is associated with Microsoft 365 Roadmap ID 562015. [Rollout Schedule:]
- General Availability (Worldwide): We will begin rolling out end of June 2026 (previously mid-June) and expect to complete by mid-July 2026.
- General Availability (GCC, GCC High): We will begin rolling out in end of June 2026 (previously mid-June) and expect to complete by mid-August 2026.
- General Availability (DoD): We will begin rolling out in end of June 2026 (previously mid-June) and expect to complete by late August 2026.
[Impact on Your Organization:]
Who is affected: Users of the SharePoint app in Teams (Viva Connections) across all clouds Platforms/Services: - Microsoft Teams
- SharePoint Online
- Viva Connections
What will happen:
- When users select the Search icon in Teams while inside the SharePoint app (Viva Connections), search results are scoped to SharePoint global search.
- SharePoint search suggestions will appear directly in Teams.
- Pressing Enter opens the SharePoint search results page in SharePoint.
- The feature is enabled by default.
- Existing SharePoint permissions and search security trimming are respected.
- No changes are required to existing admin configurations or policies.
Screenshot: Search results are scoped to SharePoint when search is initiated from within the SharePoint app in Teams: 
Learn more: Viva Connections on mobile devices | Microsoft Support (will be updated before rollout) [Action Required / Recommendations:] No action is required from administrators. Consider the following recommendations: - Inform helpdesk and end users that search behavior within the SharePoint app in Teams is becoming more targeted and SharePoint‑specific.
- Update internal documentation or training materials that reference Teams or SharePoint search behavior.
- Review SharePoint search configuration and content hygiene (optional) to ensure optimal results quality.
[Compliance considerations:]
No compliance considerations identified, review as appropriate for your organization. |
| (Updated) Microsoft Purview | Data Lifecycle Management: Retention policies for Microsoft Planner contentCategory:Microsoft PurviewNummer:MC1384412Status:stayInformed | Updated June 22, 2026: We have updated the timeline. Thank you for your patience. [What and Why:]
We’re introducing support in Microsoft Purview Data Lifecycle Management (DLM) to apply retention and deletion policies to Microsoft Planner content. This enhancement allows compliance administrators to manage Planner tasks using enterprise-grade governance controls, helping organizations meet regulatory and internal compliance requirements while reducing manual data management. This change is associated with Microsoft 365 Roadmap ID 486828.
[Rollout Schedule:]
- General Availability (Worldwide): Rollout begins in mid-July 2026 (previously mid-June) and is expected to complete by early August 2026 (previously mid-June).
[Impact on Your Organization:]
Who is affected: Compliance and IT administrators managing Microsoft Purview and Microsoft Planner. Platforms/Services: - Microsoft Purview
- Microsoft Planner
- Microsoft 365
What will happen:
- Admins can create and apply DLM retention policies to Microsoft Planner tasks.
- Planner tasks will be retained or deleted automatically based on their individual creation date or last modified date.
- Policies can be scoped to user and group-backed Planner plans.
- There is no immediate user experience change unless a retention or deletion policy is configured and enforced.
- Existing Purview compliance capabilities remain unchanged and are respected.
[Action Required / Recommendations:] If you do not require retention or deletion controls for Planner: - No action is required at this time.
If you want to manage Planner data lifecycle: - Review your organization’s compliance and data retention requirements for Planner content.
- Configure Data Lifecycle Management retention policies in Microsoft Purview for:
- Planner roster plans
- Planner group-backed plans
- Update internal compliance documentation to include Planner data governance.
- Inform compliance and legal stakeholders of the new coverage for Planner content.
Compliance Considerations:
| Area |
Explanation |
| Retention policies, holds, or deletion workflows |
This change introduces the ability to apply Microsoft Purview Data Lifecycle Management retention and deletion policies to Microsoft Planner tasks, enabling automated retention or deletion based on task creation or last modification date. |
| Processing, storage, or access to existing customer data |
Existing Microsoft Planner task data can now be governed by retention policies, which may alter how long data is stored and when it is deleted, based on administrator-defined lifecycle rules. |
| Admin monitoring, reporting, or compliance management |
Admins gain expanded compliance governance capabilities in Microsoft Purview, allowing monitoring and enforcement of Planner data lifecycle policies alongside other Microsoft 365 workloads. |
| GDPR / Data Subject Rights (access, deletion, correction) |
Automated deletion of Planner tasks based on retention policies may impact how personal data is deleted in accordance with defined retention periods and regulatory requirements. |
|
| (Updated) Microsoft Purview | Data Lifecycle Management – Power Automate integration with records managementCategory:Microsoft PurviewNummer:MC1385583Status:stayInformed | Updated June 22, 2026: We have updated the timeline. Thank you for your patience. [What and Why:]
Microsoft Purview Records Management will integrate with Power Automate to allow administrators to run custom workflows when retention-labeled items reach the end of their retention period. This enables automated post-retention handling using Power Automate across Microsoft 365 workloads.
This message is associated with Roadmap ID 558859.
[Rollout Schedule:]
General Availability (GCC, GCCH, and DoD): Rollout begins in mid-July 2026 (previously mid-June) and is expected to complete by late September 2026 (previously late August).
[Impact on Your Organization:]
Who is affected: Records Management and Compliance administrators Platforms/Services: - Microsoft Purview
- Power Automate
- SharePoint Online
- OneDrive for Business
- Exchange Online
What will happen:
- New actions are available in the Microsoft 365 Compliance connector:
- Apply a retention label on the item
- Relabel an item at the end of retention
- Delete an item at the end of retention
- Trigger a new instance of the flow if an item can’t be located
- Admins can select a pre‑existing Power Automate flow to run when a retention label expires.
- Existing retention labels and retention settings are not changed.
- The feature is not enabled by default; flows must be explicitly selected during retention label configuration.
- There is no user impact unless administrators configure and apply flows.
[Action Required / Recommendations:]
No action is required. Review internal documentation and evaluate whether to use end-of-retention workflows.
Learn more: Customize what happens at the end of the retention period | Microsoft Learn [Compliance considerations:]
| Area |
Explanation |
| Alteration of how existing customer data is processed |
Retention‑labeled content can now trigger Power Automate workflows at the end of the retention period, extending how post‑retention actions are executed. |
| Retention policies, holds, or deletion workflows |
Retention labels can invoke Power Automate flows at expiration in addition to built‑in disposition actions. |
| Admin monitoring and compliance demonstration |
Administrators may use Power Automate workflows to add logging, approvals, or notifications related to retention expiration. |
| Third‑party or cross‑service integration |
Microsoft Purview Records Management integrates with Power Automate through the Microsoft 365 Compliance connector. |
| Admin controls |
Configuration is admin‑controlled through retention label settings and selection of pre‑existing Power Automate flows. |
|
| (Updated) Microsoft Teams: Governance for built-in agents in the Teams admin centerCategory:Microsoft TeamsNummer:MC1387573Status:stayInformed | Updated June 22, 2026: We have updated the timeline. Thank you for your patience. [What and Why] We are introducing a new governance experience in the Teams admin center that enables admins to manage built-in Teams agents in a dedicated, centralized location. These built-in agents, including Channel Agent, Facilitator and Copilot Agent in Teams are integrated directly into core Teams experiences and do not require installation from the app store. This update improves administrative clarity and control by separating governance for built-in agents from traditional apps and bringing them into a single, dedicated management surface. This enables more precise policy management and supports enterprise-ready AI governance at scale. This message is associated with Microsoft 365 Roadmap ID 564766. [Rollout Schedule] - General Availability (Worldwide, GCC): Early July 2026 through mid-July 2026
[Impact on Your Organization] Who is affected - Microsoft 365 tenant admins managing Teams apps and experiences
Platforms/Services
-
Teams admin center (web)
- Microsoft Teams
What will happen - A new admin experience will be available at: Teams admin center > Teams apps > Built-in Teams agents
- Built-in agents will be managed separately from traditional apps and agents.
- Admins will be able to:
- Allow or block individual built-in agents
- Assign access to specific users or groups
- Configure agent-specific settings
- Built-in Teams agents will no longer be governed by the Org-wide app setting for Microsoft apps.
- Existing agent-level configurations will remain unchanged after rollout.
- For users who already have the app installed, we will carry those installs forward and make the app available to those same users.
- Going forward, install action will no longer be available in the admin center UX for these built-in agents, as they do not require separate installation.
- The feature will be available by default as part of the updated admin experience.
[Action Required / Recommendations] No action is required before rollout. We recommend that you: - Review your current org-wide app settings for Microsoft apps, as they will no longer apply to built-in Teams agents.
- Review and update agent-level permissions and configurations as needed in the new admin experience.
- Review install settings and audience for this change.
- Inform your admins and helpdesk teams about the new management surface and controls in the Teams admin center.
- Update internal documentation that references Teams app governance.
Learn more: [Compliance considerations] | Question | Answer | | Does the change alter how admins can monitor, report on, or demonstrate compliance activities? | Yes. Admins gain a new, dedicated governance surface for built-in Teams agents, improving visibility and management granularity. | | Does the change include an admin control and can it be controlled through Entra ID group membership? | Yes. Admins can assign access to specific users or groups, implying Entra ID group-based control. | | Does the change allow a user to enable and disable the feature themselves? | Yes. Admins can allow or block individual agents, effectively enabling/disabling availability. |
|
| Microsoft Entra: Self-service password reset CAPTCHA protection updatedCategory:Microsoft EntraNummer:MC1400824Status:planForChange | [What and Why] We are updating bot protection in Microsoft Entra self-service password reset (SSPR) by replacing the legacy CAPTCHA with modern backend throttling and behavior-based abuse detection. This change improves security, accessibility, and reliability by reducing friction for users while strengthening protection against automated attacks and account enumeration. No configuration changes are required. This change is fully managed by Microsoft. [Rollout Schedule] General Availability (Worldwide): Rollout will begin in late July 2026 and is expected to complete by mid-August 2026. [Impact on Your Organization] Who is affected - All Microsoft Entra tenants using self-service password reset (SSPR)
Platforms/Services - Microsoft Entra, self-service password reset (web flow)
What will happen - The legacy CAPTCHA challenge will be removed from the SSPR experience.
- Users will continue to reset passwords as they do today without additional prompts.
- Backend throttling and behavior-based detection will protect against bots and abuse.
- No users will be blocked from completing SSPR.
- There is no impact to users’ ability to reset their passwords.
- No changes to authentication methods, policies, or configurations.
- No new admin controls will be introduced.
- The feature is enabled by default and managed by Microsoft.
[Action Required/Recommendations] No action is required. As an optional best practice: - Inform your helpdesk that CAPTCHA prompts will no longer appear in SSPR flows.
- Update internal documentation if it references CAPTCHA during password reset.
[Compliance considerations] No compliance considerations identified, review as appropriate for your organization. |
| Microsoft Viva: New Copilot usage and cost insightsCategory:Microsoft Viva
Microsoft Copilot (Microsoft 365)Nummer:MC1400825Status:planForChange | Updated June 22, 2026: We have updated the content. Thank you for your patience. [What and Why] We are introducing cost management insights in Microsoft Viva to help organizations track Copilot credit usage across AI services and better manage budgets. This capability provides visibility into usage-based costs for AI services such as Cowork and WorkIQ API and helps organizations understand how Copilot credits are consumed across services and groups. Cost management insights are enabled by default, giving managers, Insights analysts, and administrators immediate access to usage and cost data. This feature does not change Copilot pricing or billing. It provides reporting and visibility into existing usage and costs to support better oversight and decision-making. This message is associated with Microsoft Roadmap ID 566302. [Rollout Schedule] - General Availability (Worldwide): June 30, 2026
[Impact on Your Organization] Who is affected - Managers with at least 5 direct reports (scoped access)
- Insights analysts
- Global administrators
- Organizations using Copilot with usage-based billing enabled
Platforms/Services - Microsoft Viva Insights
- Microsoft 365 admin center (Cost Management)
- Advanced Insights
- AI services in scope include Cowork and WorkIQ API
What will happen - Cost management insights are enabled by default to provide immediate access to usage-based cost data.
 - Managers with at least 5 direct reports can view Copilot credit usage within their scope, including usage by service and group, as well as associated policy and user limit data.
- Insights analysts and global administrators can access cost management data across the tenant.
- A new query template in Advanced Insights provides insights into AI spend and Copilot credit usage.
- Analysts can export data as .csv or connect to Power BI for reporting.
- Spending policy names may be visible to managers only when at least one direct report is actively using that policy.
- A spending policy defines which users or groups can consume AI services and the amount of Copilot credits they can use.
- Manager access is limited to scoped data. Tenant-wide leader access is not included in this release.
- Admins can disable manager access in Viva Insights settings.
- Admins can manage analyst access through global partition membership and can exclude specific users from appearing in insights data.
- Cost insights are not subject to minimum group size requirements.
- Use of Cowork and WorkIQ API requires usage-based billing to be configured in the Microsoft 365 admin center.
[Action Required/Recommendations] No action is required to enable this feature. However, you may consider the following: - Review Viva Insights settings for manager access to these insights. The setting will be available on June 25th.
- Confirm that usage-based billing is configured in the Microsoft 365 admin center if you plan to use Cowork or WorkIQ API.
- Validate membership of the global partition for Insights analyst access.
- Review spending policy names in Cost Management to ensure no sensitive naming is exposed to managers. Policy names are visible only when a manager has at least one direct report using that policy.
- Prepare Insights analysts to use the Advanced Insights query template for analyzing AI spend and Copilot credit usage.
[Compliance considerations] There are no additional compliance considerations beyond those described above.
|
| Microsoft Purview | Data Lifecycle Management: Retention support expanded to all supported Microsoft Copilot appsCategory:Microsoft PurviewNummer:MC1400827Status:preventOrFixIssue | [What and Why] This update expands Microsoft Purview Data Lifecycle Management retention policies to include all supported Microsoft Copilot apps within Microsoft Copilot experiences available in your tenant. Previously, retention policies did not consistently cover Copilot-generated interactions across all apps, which could result in gaps in retention coverage. This update resolves that issue by ensuring organizations can apply consistent records management and compliance controls to Copilot-generated content, helping meet regulatory requirements and strengthening enterprise-ready AI governance. [Rollout Schedule] General Availability (Worldwide): Rollout began on June 17, 2026, and is expected to complete by June 22, 2026. [Impact on Your Organization] Who is affected - Compliance and Purview administrators responsible for managing retention policies for Microsoft Copilot experiences
Platforms/Services - Microsoft Purview Data Lifecycle Management
- Microsoft Copilot experiences (across supported apps and services)
What will happen - Retention policies will automatically include all supported Copilot apps when Microsoft Copilot experiences are selected.
- Copilot-related items with item class IPM.SkypeTeams.Message.Copilot.* will be retained under applicable policies.
- Existing retention policies that already scope Microsoft Copilot experiences will automatically apply to all supported Copilot apps.
- No changes to existing policy configurations are required.
- This change is enabled by default.
[Action Required/Recommendations] No immediate action is required. However, you may consider the following: - Review your existing Microsoft Purview retention policies that include Microsoft Copilot experiences to understand updated coverage.
- Update internal compliance or records management documentation to reflect expanded Copilot app coverage.
- Inform compliance and legal stakeholders of this change for awareness.
Learn more: Learn about retention for Copilot & AI apps | Microsoft Purview | Microsoft Learn [Compliance considerations] | Does the change affect Purview compliance capabilities (such as DLP, eDiscovery, retention)? | Yes. Expands coverage of retention policies | | Does the change modify retention policies, holds, or deletion workflows? | Yes. Retention scope expands to include all Copilot apps when Copilot experiences are selected. |
|
| Create branded presentations using Copilot in PowerPointCategory:Microsoft Copilot (Microsoft 365)Nummer:MC1400828Status:stayInformed | [What and Why:]
Microsoft is introducing the ability for users to create on-brand presentations directly within Copilot in PowerPoint by selecting a brand kit during content generation. This enhancement ensures consistency, reduces manual formatting effort, and enables faster creation of polished presentations aligned with organizational standards. This supports personal and team productivity.
[Rollout Schedule:]
- Public Preview (Worldwide): Began in early June 2026 and completes by late June 2026
- General Availability (Worldwide): Begins in mid-June 2026 and completes by late June 2026
[Impact on Your Organization:]
Who is affected: Users with Microsoft 365 Copilot (Premium) licenses and organizations using brand kits
Platforms/Services: PowerPoint (Desktop, Web)
What will happen:
[Action Required / Recommendations:] No immediate action is required. However, we recommend the following to maximize value:
- Ensure users have Microsoft 365 Copilot Enterprise licenses.
- Configure brand manager policies (optional).
- Inform helpdesk and training teams.
- Update internal documentation.
- Communicate rollout and usage guidance to users.
Learn more: [Compliance considerations:]
| Consideration |
Explanation |
| Introduces or modifies AI/ML capabilities |
Copilot in PowerPoint uses generative AI and now incorporates brand selection into the content creation workflow. |
| New way for users to interact with generative AI |
Users can explicitly select a brand kit, influencing formatting and design of AI-generated presentations. |
| Includes admin control |
Admins can configure brand manager policies to define and distribute official brand kits. |
| User can enable or disable aspects of the feature |
Users can create and manage personal brand kits if organizational policies are not configured. |
|
| Stay Up to Date in Employee Self-ServiceCategory:Microsoft Copilot (Microsoft 365)Nummer:MC1400829Status:planForChange | [What and Why:]
We’re introducing Stay Up to Date, a new capability in the Employee Self-Service (ESS) agent that proactively surfaces personalized updates on the ESS landing page. This feature helps employees stay informed about IT, HR, and workplace requests without needing to search across systems. By presenting actionable updates as prioritized cards that launch contextual conversations, Stay Up to Date improves productivity, reduces status-check inquiries, and supports more efficient self-service experiences.
[Rollout Schedule:]
- General Availability (Worldwide): We will begin rolling out in late July 2026 and expect to complete by mid-August 2026.
[Impact on Your Organization:]
Who is affected:
- Organizations with an active ESS deployment and Microsoft 365 Copilot licenses
- Employees using ESS for IT, HR, or workplace requests
- IT and HR admins managing ESS experiences
Platforms/Services:
- Microsoft 365 Copilot
- Employee Self-Service (ESS) agent
What will happen:
- A new Stay Up to Date carousel will appear on the ESS landing page
- Employees will see personalized update cards for ticket status, follow-ups, and time-sensitive actions
- Each card includes a status indicator, summary, and link to resume a related conversation
- Cards are prioritized and expire automatically
- The feature is enabled by default for eligible tenants
- At least one configured connector (e.g., ServiceNow) with ticket-related topics capable of reading ticket data
- Stay Up to Date does not create or modify tickets; it surfaces updates from configured systems only
[Action Required/Recommendations:]
No action is required to enable this feature for eligible tenants. However, we recommend administrators review the following:
- Verify that your ESS deployment includes at least one configured connector with ticket-related topics.
- Communicate this change to helpdesk and support teams to prepare for reduced status inquiry volume.
- Update internal ESS documentation to reflect proactive updates on the landing page.
If desired, manage the feature: - Go to Microsoft 365 admin center → Copilot → Settings → Employee Self-Service
- Select your agent
- Navigate to Insights cards settings
- Toggle Stay Up to Date on or off and save
Learn more: Customize the Employee Self-Service agent | Microsoft Learn
[Compliance considerations:]
| Compliance Area |
Assessment |
| Introduces or modifies AI/ML capabilities interacting with customer data |
Uses Copilot capabilities to surface personalized updates from enterprise data sources. |
| Alters how existing customer data is processed or accessed |
Reads and surfaces ticket data from connected systems (e.g., IT, HR tools) in ESS. |
| Provides a new way for users to interact with generative AI |
Users can initiate contextual Copilot conversations directly from update cards. |
| Adds integration with third-party software |
Depends on connectors (e.g., ServiceNow, Workday, SAP) for ticket data. |
| Introduces admin control |
Feature can be enabled or disabled in Microsoft 365 Admin Center. |
| Stores new customer data |
Surfaces existing data; documentation does not specify new storage or caching behavior. |
| New communication method between users or tenants |
Enables contextual conversations tied to updates, but not a new standalone communication channel. |
| Impact to Purview (DLP, labeling, audit, retention, etc.) |
No explicit changes stated; depends on how underlying data sources are governed. |
| Changes to compliance monitoring or reporting |
No explicit changes documented; monitoring may depend on existing Copilot/ESS telemetry. |
| Changes to GDPR data subject rights |
No direct changes stated; feature surfaces existing data already governed by Microsoft 365 controls. |
| User ability to enable/disable feature | Controlled at admin level; users interact but do not manage availability. |
|
| Microsoft Teams: Room optimization mode relocated to context-dependent optionCategory:Microsoft TeamsNummer:MC1400830Status:planForChange | [What and Why] Microsoft Teams is updating the location and naming of the room optimization experience, previously called “add shared display,” to a context dependent “optimize for room” option. This change improves usability and helps users more easily configure Teams for shared and in-room meeting scenarios. The updated experience automatically optimizes audio, video, and display behavior to support more effective hybrid collaboration. This message is associated with Microsoft 365 Roadmap ID 564912. [Rollout Schedule] - General Availability (Worldwide): Begins in mid-July 2026 and expected to complete by late July 2026.
[Impact on Your Organization] Who is affected - Users who run Microsoft Teams meetings on laptops connected to shared or room-based equipment, such as conference rooms or bring your own device meeting setups.
Platforms/Services What will happen - The “add shared display” option is renamed to “optimize for room.”
- The option is moved to a context dependent location in the Teams interface.
- When enabled, Teams will optimize the meeting experience for room scenarios.
- Connected room peripherals, such as AV devices associated with a room, will be automatically selected instead of laptop audio and video devices.
- If an external display is connected, shared display mode will activate and split Teams into two windows.
- Voice isolation will be disabled so in room participants can be heard clearly.
- Voice recognition will be enabled if allowed by policy.
- A room node will appear in the meeting roster to represent in room participants.
- The feature is user initiated and is not enabled by default.
[Action Required or Recommendations] No admin action is required. Recommended actions: - Inform users of the updated “optimize for room” terminology and where to find it.
- Update internal documentation that references “add shared display.”
- Communicate the change to support and helpdesk teams.
- Encourage users to adopt the feature for improved hybrid meeting experiences.
[Compliance considerations] No compliance considerations identified, review as appropriate for your organization. |
