| (Updated) Upcoming change: disabling Teams meeting recording expiration notification emailsCategory:Microsoft TeamsNummer:MC1245635Status:planForChange | Updated June 10, 2026: We have updated the timeline. Thank you for your patience. Introduction
We are introducing a new PowerShell control that allows administrators to manage Teams Meeting Recording (TMR) expiration and deletion notification emails across the tenant. This update is based on customer feedback indicating a strong preference to continue receiving notifications while also requesting an option to disable them. This change provides greater administrative control while maintaining the default experience that helps users stay informed
When this will happen
- Commercial clouds: Rollout began May 29, 2026; completed June 2, 2026
- Sovereign clouds (GCC, GCC High, DoD): Available now.
How this affects your organization
Who is affected:
- SharePoint Administrators and Global Administrators managing Teams Meeting Recordings
Platforms/Services: - Microsoft Teams
- SharePoint Online
- PowerShell (SharePoint Online Management Shell)
What will happen:
- A new PowerShell setting is available to control notification emails for Teams meeting recording expiration and deletion
- Notifications remain enabled by default; no action is required to maintain the current behavior.
- Admins can disable notifications tenant-wide using a PowerShell cmdlet.
- There is no impact to recording expiration or deletion behavior—only the notification emails are affected.
- This setting applies at the tenant level only; per-user configuration is not supported.
Action Required / Recommendations
- No action is required if you want to continue receiving Teams meeting recording notification emails
If you prefer to disable notifications, follow these steps: - Ensure you are using the latest version of the SharePoint Online Management Shell:
- Download from the SharePoint Online Management Shell page
- Note that:
- The installer is Windows-only
- For non-Windows environments, use a Windows VM or Azure Virtual Desktop
- Verify you have required permissions:
- SharePoint Administrator or Global Administrator
- Review and update internal documentation if you reference recording notifications
- Inform helpdesk/support teams about this new control option
To disable notifications: Connect-SPOService -Url https://<your-tenant>-admin.sharepoint.com</your-tenant> Set-SPOTenant -DisableTeamsMeetingRecordingDeletedNotification $true To verify the setting: Get-SPOTenant | Format-List *Recording* (Get-SPOTenant).DisableTeamsMeetingRecordingDeletedNotification To re-enable notifications: Set-SPOTenant -DisableTeamsMeetingRecordingDeletedNotification $false
|
| (Updated) Extending AI in SharePoint using custom skillsCategory:SharePoint OnlineNummer:MC1269209Status:planForChange | Updated June 1, 2026: We have updated the timeline. Thank you for your patience. [Introduction]
We’re introducing custom skills for AI in SharePoint, which let users teach AI in SharePoint how to perform common business tasks in a consistent, repeatable way. With skills, organizations can tailor AI behavior to their own documents, standards, and processes—such as reviewing compliance documents or offer letters—without writing code or using external tools. This update helps reduce manual effort and makes AI results more reliable for everyday SharePoint work. This message is associated with Roadmap ID 559800. [When this will happen:]
- Public Preview (Worldwide): We will begin rolling out in mid-April 2026 and expect to complete by early May 2026.
- General Availability (Worldwide): We will begin rolling out in mid-June 2026 (previously late May) and expect to complete byearly July 2026 .
[How this affects your organization:]
Who is affected:
- Users of AI in SharePoint
- SharePoint site owners and admins
- Users with edit permissions on SharePoint sites
What will happen:
- Users with edit permissions can create custom skills using natural language within AI in SharePoint.
- Skills allow users to define reusable, multi‑step AI instructions for common business tasks (for example, reviewing compliance documents or offer letters).
- AI in SharePoint can automatically select relevant skills from the current site based on a user’s query, or users can invoke a skill by name.
- Skills are saved as Markdown (.md) files in the site’s Agent Assets library (/Agent Assets/Skills/<skill-name>/SKILLmd) and are governed by existing SharePoint permissions and compliance policies.
- Skills reuse native AI in SharePoint capabilities (content understanding, list manipulation, folder organization, and other supported SharePoint actions).
- Skills cannot connect to external systems or execute custom code.
- The feature is enabled by default and has no separate tenant‑level on/off toggle.
- Existing SharePoint permissions are respected; users cannot perform actions they do not already have permission to do.
[What you can do to prepare:] No action is required to enable this feature. Recommended actions for admins:
- Review how SharePoint site permissions are managed, as any user with edit permissions can create skills.
- If needed, customize who can create or use skills by breaking permission inheritance on the Agent Assets library.
- Update internal governance or usage guidance to include skills as part of AI in SharePoint.
- Inform helpdesk or power users that skills are stored as files and governed by existing SharePoint controls.
We will update this post with new documentation soon. [Compliance considerations:]
| Compliance area |
Explanation |
| Does the change store new customer data? |
Skill definitions are stored as Markdown (.md) files in the SharePoint “Agent Assets” library and are governed by existing SharePoint storage, retention, and compliance policies. |
| Does the change alter how existing customer data is processed or accessed? |
AI in SharePoint can apply skills to site content, enabling more structured and repeatable AI processing of documents, lists, and folders within the site. |
| Does the change introduce or significantly modify AI/ML or agent capabilities? |
This change introduces reusable, multi-step AI skills that extend how AI in SharePoint performs tasks using native SharePoint capabilities. |
| Does the change provide users a new way of interacting with generative AI? |
Users can create, invoke, and reuse custom AI skills directly within SharePoint using natural language. |
| Does the change include an admin control? |
Admins can control who can create or use skills by managing permissions on the Agent Assets library, including breaking permission inheritance if needed. |
| Does the change allow a user to enable or disable the feature themselves? |
The capability is enabled by default and cannot be turned off globally, but usage is constrained by SharePoint permissions and access to AI in SharePoint. |
|
| (Updated) Unlocking deeper Copilot insights with enhanced Power BI filteringCategory:Microsoft Viva
Microsoft Copilot (Microsoft 365)Nummer:MC1302902Status:stayInformed | Updated June 4, 2026: We have updated the timeline. Thank you for your patience. [Introduction]
We are enhancing Power BI reporting capabilities in Viva Insights by allowing administrators to enable additional attributes—including reserved attributes and organization-specific custom attributes—as report filters. This update enables organizations to derive deeper insights aligned to their business structure and needs. This message is associated with Microsoft 365 Roadmap ID 559995.
[When this will happen:]
General Availability (Worldwide): Rollout will begin in late June 2026 (previously late May) and is expected to complete by early July 2026 (previously early June).
[How this affects your organization:]
Who is affected:
- Viva Insights Global administrators and Insights administrators
- Users with access to Viva Insights Power BI reports
- A Microsoft 365 Copilot (Premium) license is required to use this feature
What will happen:
- The configuration experience is available to admins by default in the Viva Insights web app.
- Admins can enable additional attributes as filters in Power BI reports via the Viva Insights web app.
Screenshot 1: Example of the Attribute filter settings page in Viva Insights where admins can enable filters for Power BI reports: 
- Supported filters include reserved attributes (provided by Microsoft) and custom attributes configured by your organization.
Screenshot 2: Example of Viva Insights reports displaying newly enabled filters available to users after admin configuration: 
- Once enabled:
- These filters become available to report viewers in Power BI
- Users can personalize reports based on business-specific dimensions
[What you can do to prepare:]
- No immediate action is required.
- Review your current Viva Insights attribute configuration.
- Identify which custom or reserved attributes would add value as report filters.
- Plan internal governance for filter usage.
- Communicate this capability to report users once enabled.
- Update internal documentation or reporting guidance.
Before rollout, we will update this post with new documentation. [Compliance considerations:]
| Compliance area |
Impact |
| Does the change alter how admins can monitor, report on, or demonstrate compliance activities? |
Adds additional filtering capabilities in Power BI reports, enabling more granular reporting and analysis. |
| Does the change include an admin control and can it be controlled through Entra ID group membership? |
Admins must enable additional attributes, indicating administrative control of the feature. |
|
| (Updated) Microsoft Purview compliance portal: Role groups user interface (UI) enhancementsCategory:Microsoft PurviewNummer:MC1311975Status:stayInformed | Updated June 25, 2026: We have updated the content. Thank you for your patience. [Introduction]
We are enhancing the Role groups experience in the Microsoft Purview compliance portal and Microsoft Defender portal to make it easier for admins to understand and validate permissions. Based on customer feedback, the updated user interface (UI) introduces new views that allow admins to quickly look up role group assignments by roles, members, or their own permissions, reducing time spent troubleshooting access and improving administrative clarity. This message is associated with Roadmap ID 562033.
[When this will happen:]
- Public Preview (Worldwide): We will begin rolling out in mid-June 2026 and expect to complete by mid-July 2026.
- General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out in mid-July 2026 and expect to complete by mid-August 2026.
[How this affects your organization:]
Who is affected:
- Admins who manage role groups in the Microsoft Purview compliance portal and Microsoft Defender portal.
What will happen:
- Admins will see additional views on the Role groups page in the Microsoft Purview Compliance portal and the Settings page in the Microsoft Defender portal.
Screenshot: Role groups page in the Microsoft Purview compliance portal showing new views for Roles, Members, and My permissions: 
- Admins can look up role group assignments by:
- Role
- Member
- My permissions (to understand their own assigned roles)
- Existing role group assignments and permissions remain unchanged.
- The enhancement is enabled by default once deployed.
- There is no impact to user workflows.
[What you can do to prepare:]
- No action is required.
- Consider informing compliance and security admins about the new lookup views.
- Update internal documentation if it references the Role groups UI.
Learn more: Permissions in the Microsoft Purview portal | Microsoft Learn (will be updated before rollout)
[Compliance considerations:]
- This change enhances admins’ ability to review and validate role group assignments, improving visibility during compliance reviews and audits.
|
| (Updated) Learning Agent in Microsoft 365 Copilot to become generally availableCategory:Microsoft Viva
Microsoft Copilot (Microsoft 365)Nummer:MC1319212Status:stayInformed | Updated June 26, 2026: If your organization is in a DoD environment you are not impacted by this change and can safely disregard this message. We apologize for any inconvenience. [What and Why:]
Learning Agent in Microsoft 365 Copilot is becoming generally available to help organizations accelerate AI upskilling and reskilling directly in the flow of work. Based on feedback from the Frontier release, this update expands availability, integrates learning more deeply across Microsoft 365 experiences, and adds admin controls and reporting to support enterprise-ready deployment. This message is associated with Microsoft 365 Roadmap ID 490154.
[Rollout Schedule:]
General Availability (Worldwide): We will begin rolling out in early June 2026 and expect to complete by early June 2026.
[Impact on Your Organization:]
Who is affected:
- Microsoft 365 Copilot licensed users
- Admins managing Copilot and learning experiences
Platforms/Services:
- Microsoft 365 Copilot (web and desktop)
- Teams, Word, Excel, PowerPoint
- Viva Learning, SharePoint
Licensing requirements:
- Users must have an active Microsoft 365 Copilot (Premium) license to access Learning Agent capabilities that rely on enterprise grounding, including skills assessments, role- and task-based learning scenarios, and daily AI tips.
- A Viva Learning license (seeded or premium) is required to create and access learning plans created through the Learning Agent.
- LinkedIn Learning role play scenarios require a LinkedIn Learning Premium license.
- Skillsoft role play scenarios require a Skillsoft license for the CAISY Conversational Simulator.
What will happen:
[Action Required / Recommendations:]
- Review Learning Agent deployment settings in Microsoft 365 admin center > Copilot > Settings.
- Decide whether to deploy the Learning Agent broadly, restrict access to specific users, or block it.
- Ensure People Skills is enabled to support optimal Learning Agent functionality.
- Confirm licensing for:
- Microsoft 365 Copilot (required for enterprise‑grounded features)
- Viva Learning (required for Learning Plans)
- LinkedIn Learning Premium or Skillsoft CAISY (if using role play scenarios)
- Communicate availability and new capabilities to helpdesk and L&D teams.
Learn more: [Compliance considerations:]
| Area |
Explanation |
| AI/ML interaction with customer data |
The Learning Agent introduces generally available AI capabilities that are grounded in enterprise data to deliver skills assessments, role- and task-based learning scenarios, and personalized learning recommendations. |
| User interaction with generative AI |
Users can directly interact with the Learning Agent to receive personalized learning guidance, skill assessments, learning plans, role plays, and AI skilling recommendations. |
| Admin monitoring and reporting |
New Learning Agent usage reports provide admins and L&D leaders visibility into adoption, engagement, and feature-level usage. |
| Third-party integrations |
The Learning Agent integrates with LinkedIn Learning and Skillsoft to surface role play scenarios and learning content, which require separate third-party licenses. |
| Admin controls |
Admins can deploy, restrict, or block the Learning Agent and control task assignment behavior through the Task Inferencing API at the tenant level. |
|
| (Updated) Microsoft Entra ID SSPR will require registered authentication methods starting September 7, 2026Category:Microsoft EntraNummer:MC1325414Status:planForChange | Updated June 26, 2026: We have updated the timeline. Thank you for your patience. [What and Why] You’re receiving this message because your organization uses Microsoft Entra ID Self-Service Password Reset (SSPR). Currently, SSPR may allow users to verify their identity using contact information stored in directory attributes such as mobile phone, business phone, and alternate email, even if those values were never explicitly registered as authentication methods. To strengthen identity security, SSPR will require explicitly registered authentication methods for verification. This change is part of Microsoft’s Secure Future Initiative and ensures password reset verification is based on trusted, user-validated methods rather than directory-sourced attributes. [Rollout Schedule] - August 6, 2026: SSPR registration campaign begins prompting users and administrators to register authentication methods if SSPR setting requires registration and users do not have enough methods.
- September 7, 2026: Enforcement begins. SSPR will no longer accept directory-sourced contact information for verification.
- General Availability (Worldwide, GCC, GCC High): Early September 2026 through mid-September 2026
[Impact on Your Organization] Who is affected - All users (including administrators) in tenants with SSPR enabled
- Applies to Public cloud and US Government clouds (GCC, GCC High, DoD)
Platforms/Services - Microsoft Entra ID
- Self-Service Password Reset (SSPR)
- Web and admin portal experiences
What will happen - Only explicitly registered authentication methods will be accepted for SSPR verification.
- Directory attributes (such as mobilePhone, businessPhone, otherMails) will no longer be valid unless registered.
- Approximately 86% of SSPR verifications already use registered methods today.
- Users without registered methods at enforcement will be:
- Unable to complete password resets
- Prompted to register methods or contact an administrator
- The registration campaign will proactively prompt affected users starting July 6, 2026.
[Action Required / Recommendations] Action is required before September 7, 2026. - Review authentication method registration coverage:
- Go to Microsoft Entra admin center → Authentication methods → User registration details
- Ensure all users (including admins) have at least one registered authentication method that satisfies your SSPR policy.
- Allow or enable the SSPR registration campaign to prompt users automatically.
- Plan fallback processes:
- Helpdesk-assisted registration
- Alternative onboarding scenarios for users unable to self-register
- Communicate this change to:
- IT admins and helpdesk teams
- Users (encourage registration via My Security Info)
Learn more: [Compliance Considerations] | Question | Answer | | Does the change alter how existing customer data is processed, stored, or accessed? | Yes. Directory attributes (such as phone/email) will no longer be used for SSPR unless explicitly registered as authentication methods. | | Does the change alter admin monitoring/reporting? | Yes. Admins can monitor registration coverage via updated reporting in the Entra admin center. | | Does the change include admin controls? | Yes. Admins control SSPR policies and registration requirements. |
|
| (Updated) Action required: Update Teams Rooms app to maintain PowerPoint Live functionalityCategory:Microsoft TeamsNummer:MC1332812Status:preventOrFixIssue | Updated June 26, 2026: We have updated the content. Thank you for your patience. [What and Why] We are performing planned maintenance to support upcoming updates to PowerPoint Live in Microsoft Teams, which will begin rolling out on August 3, 2026. To keep Teams Rooms aligned with these updates, ensure devices are running the latest supported app versions. [Rollout Schedule] Teams Rooms on Windows General Availability - Worldwide and GCC: Already available now.
- GCC High: We will begin rolling out in early June 2026 and expect to complete by mid-June 2026.
- DoD: We will begin rolling out in early June 2026 and expect to complete by mid-June 2026.
Teams Rooms on Android General Availability - Worldwide and GCC: We will begin rolling out in late June 2026 (previously mid-June) and expect to complete by early July 2026 (previously late June).
- GCC High: We will begin rolling out in early July 2026 and expect to complete by mid-July 2026.
- DoD: We will begin rolling out in early July 2026 and expect to complete by mid-July 2026.
[Impact on Your Organization] Who is affected - Organizations using Microsoft Teams Rooms devices
Platforms/Services Microsoft Teams - Teams Rooms on Windows
- Teams Rooms on Android
What will happen - Teams Rooms devices running outdated app versions may not fully support PowerPoint Live experience, including:
- Synchronized media playback
- Viewing real-time inking and annotation
- There is no change to existing admin policies.
- Functionality remains consistent once devices are updated.
[Action Required/Recommendations] To maintain PowerPoint Live functionality, complete the following: - Update Teams Rooms devices to supported versions:
- Windows: Version 5.6.135 (available now) or greater
- Android: Version 1449/1.0.96.2026129709 (available now) or greater
- Complete updates before August 3, 2026.
- Review device update processes to ensure compliance across all meeting rooms.
- Notify IT support/helpdesk teams of potential functionality impact if devices are not updated.
[Compliance Considerations] | Question | Answer | | Does the change alter how existing customer data is processed, stored, or accessed (such as documents, emails, chats, etc.)? | Yes. The update to PowerPoint Live functionality may affect how presentation content is synchronized and rendered across Teams clients, but it does not introduce new data storage or retention changes. |
|
| Data Privacy: Microsoft Online Services Subprocessor DisclosureCategory:Microsoft 365 suiteNummer:MC1403210Status:stayInformed | A Data Privacy message regarding your organization is available within Message Center. The contents of this message can be accessed within Message Center by a Global Administrator or someone designated as a Message Center Privacy Reader.
Please sign in to Admin Center to view the details of this message in the M365 Message center. |
| Power Platform admin center – Advanced connector policiesCategory:Power PlatformNummer:MC1403390Status:stayInformed | Update: This feature has been disabled; we will announce a new date in the future.
We are announcing the ability to use advanced connector policies (ACP) to govern which connectors, connector actions, and Model Context Protocol (MCP) servers are permitted across your environments in Power Platform admin center. This feature reached general availability on June 4, 2026.
How does this affect me?
ACP replaces the Business/Non-Business/Blocked classification model of classic data loss prevention (DLP) policies with a single default-deny allowlist, and is off by default until explicitly activated by an administrator. ACP currently applies to certified connectors only (including MCP connectors); continue using DLP policies for custom connectors. This feature includes the following capabilities:- Default-deny allowlist: All certified connectors and actions are blocked unless explicitly added. New connectors are blocked by default until an administrator reviews and allows them. Business and non-business classifications have been removed for connectors and actions to improve clarity.
- Design-time and runtime enforcement: Makers now get immediate feedback while authoring an app, flow, or agent, not only at runtime when data is changing. Makers are blocked from adding restricted connectors or actions while authoring, and the platform performs a last-mile check at runtime.
- Govern AI tools: Admins can block an MCP server just like any other connector or action.
- Action-level control: Allow a connector while disabling specific risky, deprecated, or internal actions. Triggers, internal, and deprecated actions are clearly tagged.
- Automatic scaling: Because ACP is native to environment groups, the right policy follows each environment created through personal developer environments and routing, no environment-by-environment overhead is required.
- ACP-only mode: Optionally skip classic data policy evaluation entirely for a clean governance posture.
Admins can enable ACP directly on a single environment, which does not require Managed Environments, for high-risk, pilot, or regulated environments. Admin can also enable it once applied to an environment group to govern a fleet at scale, which does require Managed Environments.
What action do I need to take?
This message is for awareness, and no action is required.
To enable ACP in your environment, navigate to the Power Platform admin center and complete the following steps.- Review inventory. Use Power Platform inventory (preview) under Manage > Inventory to see connector and operation usage across apps, flows, and agents so you can anticipate impact before activating ACP.
- Test on a single environment. Apply ACP under Security > Data and privacy in the Power Platform admin center. No Managed Environments are required for a single environment. The policy remains off until you activate it.
- Build your allowlist. Starting from default-deny, add the certified connectors and actions your teams require. New connectors are blocked by default, so plan for ongoing allowlist reviews.
- Scale with environment group. Applying ACP across an environment group requires Managed Environments. Configure on the group’s Rules tab.
- Run hybrid with DLP. Keep existing DLP policies in place for custom connectors, HTTP connectors, and scenarios not yet at parity while you migrate to ACP.
- Evaluate ACP-only mode. Test it in public preview to prepare for migration off of DLP policies.
If you would like more information on this feature, please visit the Advanced connector policies documentation and the announcement blog post. |
| Updates available for Microsoft 365 Apps for Current ChannelCategory:Microsoft 365 appsNummer:MC1404361Status:stayInformed | We've released updates to the following update channel for Microsoft 365 Apps:
[When this will happen:]
We'll be gradually rolling out this update of Microsoft 365 Apps to users on that update channel starting June 25th, 2026 (PST).
[How this will affect your organization:]
If your Microsoft 365 Apps clients are configured to automatically update from the Office Content Delivery Network (CDN), then no action is required.
If you manage updates directly you can now download this latest update and begin deployment.
[What you need to do to prepare:]
To get more details about this update view the following release notes:
|
| Microsoft Dataverse – Service Update 9.2.26064.00000 for EURCategory:Microsoft DataverseNummer:MC1405050Status:stayInformed | We have a minor service update planned for your Microsoft Dataverse environment hosted in EUR.
This service update will occur within your region’s scheduled maintenance timeline, on the scheduled date listed for Microsoft Dataverse.
How does this affect me?
The version number for your Microsoft Dataverse environment will update to version 9.2.26064.00000 or higher.
There is no expected degradation to service performance or availability, however, during this maintenance window users may see short, intermittent impact such as transient SQL errors or a redirect to the login screen.
What action do I need to take?
This message is for awareness and no action is required. |
| Microsoft 365 Copilot: Updated service plan behavior for Copilot experiencesCategory:Microsoft Copilot (Microsoft 365)Nummer:MC1405498Status:planForChange | [What and Why:] We are simplifying how the Microsoft 365 Copilot service plan controls Copilot experiences to provide a more predictable and manageable admin experience. With this change, the Microsoft Copilot with Graph-grounded chat service plan serves as the primary control determining whether licensed users receive Microsoft 365 Copilot (Premium), Copilot Chat (Basic) or Microsoft 365 Copilot (Basic) experiences so that it is easier to stage deployments and align with enterprise expectations for manageability and consistency. [Rollout Schedule:] General Availability (Worldwide): We will begin rolling out on late July 2026 and expect to complete by early August 2026. [Impact on Your Organization:] Who is affected: - Admins managing Microsoft 365 Copilot service plans
- Users assigned a Microsoft 365 Copilot commercial license
What will happen: - The Copilot service plan will act as a control for Copilot experiences where:
- Enabled: Licensed users are expected to receive the Microsoft 365 Copilot (Premium) experience.
- Disabled: Unlicensed users are not expected to receive Microsoft 365 Copilot (Premium) experiences and will have access to Copilot Chat (Basic) or Microsoft 365 Copilot (Basic) experiences.
- Important to note that Personal Content Mode as described in Microsoft 365 Copilot Personal Content Mode | Microsoft Learn will no longer be activated when the service plan is disabled.
- Users with the service plan disabled will have access to a primarily web-grounded Copilot Chat, with reduced organizational data (Microsoft Graph) grounding in select apps.
- This change improves predictability and consistency of Copilot experiences by reducing scenarios where users may access partial Copilot functionality when the service plan is disabled. There is no change to licensing or SKU configuration; however, the Copilot features available to users may vary based on service plan configuration. The service plan becomes the control for managing Copilot experience access.
[Action Required/Recommendations:] No immediate action is required, but we recommend that you: - Review your current Copilot service plan assignments to understand which users may be impacted.
- Reach out to your account team or support if you have questions about this or would prefer to stay on the existing experience until we provide another solution to manage Personal Content Mode.
- Identify users or groups currently relying on Personal Content Mode and plan communications about the upcoming change.
- Update any internal documentation and guidance to reflect the simplified on/off behavior.
- Use your existing service plan management approach to control Copilot access.
Learn more: |
| Microsoft Teams: Assistant information now available in Organization viewCategory:Microsoft TeamsNummer:MC1405501Status:stayInformed | [What and Why:] Microsoft Teams will now display Assistant information in the Organization section of a user’s profile card, in addition to the existing Contacts tab experience. Users can view Assistant information directly from the Organization section when it is populated on a profile, improving the discoverability of Assistant information within Teams. This message is associated with Microsoft 365 Roadmap ID 565221.
[Rollout Schedule:] -
Targeted Release (Worldwide): Beginning early July 2026; expected to complete by mid-July 2026
-
General Availability (Worldwide): Beginning mid-July 2026; expected to complete by mid-August 2026
[Impact on Your Organization:]
Who is affected: Organizations that populate the Assistant field in Microsoft 365 user profiles and users who view profile cards in Teams.
Platforms/Services: -
Microsoft Teams (desktop, web)
- Microsoft 365 user profiles
What will happen:
- The Assistant field will be displayed in the Organization section of Teams profile cards.
- This information will appear automatically if populated in user profiles.
- The feature will be enabled by default.
- The Assistant designation is informational only and does not grant permissions, change reporting structures, or modify user roles.
[Action Required / Recommendations:]
No action is required if your organization already populates Assistant information. If you want to review or configure this property:
- Review Assistant property settings in SharePoint Admin Center → More Features → User Profiles → Manage User Properties → Assistant.
- Notify executive assistants and support staff of this change.
- Update internal documentation if applicable.
[Compliance considerations:]
No compliance considerations identified, review as appropriate for your organization. |
| Access your brand assets in PowerPointCategory:Microsoft 365 apps
Microsoft Copilot (Microsoft 365)Nummer:MC1405505Status:stayInformed | [What and Why:]
Microsoft is introducing native access to brand assets (colors, logos, images, icons, and more) directly within PowerPoint through Microsoft 365 Copilot. This improves productivity by helping users quickly create presentations that stay on-brand while enabling admins to standardize branding through official brand kits. This message is associated with Roadmap Id 566351.
[Rollout Schedule:]
- Targeted Release (Worldwide): Beginning in mid-July 2026 and expect to complete by late July 2026
- General Availability (Worldwide): Beginning in mid-July 2026 and expect to complete by early August 2026
[Impact on Your Organization:]
Who is affected: All Microsoft 365 Copilot (Premium) licensed PowerPoint users and admins managing branding Platforms/Services: - PowerPoint (Windows, Mac, Web)
What will happen:
- Users can access brand assets (colors, logos, icons, images) directly within PowerPoint.
Screenshot 1: Locate the Brand option on the PowerPoint ribbon: 
- Brand assets are surfaced through a dedicated brand pane to enable quick, on-brand edits.
Screenshot 2: Brand pane in PowerPoint showing brand assets and colors: 
- Official brand kits (if configured) will be available tenant-wide.
- Users without official kits can create personal brand kits.
- The feature is available to Copilot licensed users and does not require additional configuration for basic usage.
[Action Required/Recommendations:]
No action is required to enable the default experience for licensed users. For organizations that want centralized brand governance:
- Enable and assign Microsoft 365 Copilot licenses.
- Configure brand manager policy to designate brand managers.
- Create and publish official brand kits for tenant-wide use.
- Validate existing templates for optimal Copilot output.
- Communicate this feature to users and helpdesk teams.
Learn more: [Compliance considerations:]
| Area |
Explanation |
| Stores new customer data |
Brand kits store organizational assets such as logos, templates, color palettes, and guidelines within Microsoft 365 Copilot. |
| Alters processing of existing customer data |
Copilot uses existing templates and brand kit assets to generate presentations, influencing how organizational content is processed and applied. |
| Introduces AI/ML capabilities interacting with data |
Copilot uses AI to analyze templates, brand kits, and prompts to generate on-brand presentations. |
| New generative AI interaction for users |
Users can create presentations using Copilot prompts that automatically incorporate brand assets and styles. |
| Includes admin controls |
Admins can configure brand manager policies and assign designated users to manage official brand kits. |
| User enable/disable capability |
Users can create and manage personal brand kits when official kits are not centrally configured. |
|
| Microsoft OneNote: Multimodal recording in Copilot Notebooks on WindowsCategory:Microsoft 365 apps
Microsoft Copilot (Microsoft 365)Nummer:MC1405506Status:planForChange | [What and why] We are introducing multimodal capture in Copilot Notebooks on Windows. This feature enables users to capture audio, images, and notes in a single experience and use Microsoft 365 Copilot to generate structured insights such as summaries, decisions, and action items. This helps users turn meetings, conversations, and offline work into actionable outputs within Copilot Notebooks. This message is associated with Microsoft 365 Roadmap ID 566322. [Rollout schedule] - General Availability (Worldwide): Beginning late July 2026 and expected to complete by mid-September 2026
[Impact on Your Organization] Who is affected - Users with access to Copilot Notebooks in OneNote
- Requires a Microsoft 365 Copilot license
- Available to commercial Microsoft 365 users with work or school (Entra ID) accounts
- Users must have the Microsoft 365 desktop apps installed on Windows (including OneNote)
Platforms/Services - OneNote (desktop app on Windows)
- Copilot Notebooks
- Microsoft 365 Copilot
What will happen - Users can capture audio, images, and notes directly into Copilot Notebooks.
- Capture can be suggested or initiated when supported browser-based meetings are detected (Zoom, Webex, Google Meet).
- Users can also manually start capture from the OneNote system tray icon.
- Copilot generates a structured Copilot Page with insights, decisions, and action items based on captured content.
- Captured content is saved to the selected Copilot Notebook and is available across endpoints.
- The feature is available by default for eligible users.
[Action Required or Recommendations] No action is required. Admins can disable this feature using a policy setting. - Review available policy settings if you want to disable the feature.
- Inform users about organizational policies related to transcription and consent.
- Organizations should ensure users follow applicable consent and recording policies before capturing or transcribing conversations.
Learn more: [Compliance considerations] | Question | Answer | | Does the change store new customer data? | Yes. Captured audio, images, and notes are stored in the user’s selected Copilot Notebook (SharePoint or OneDrive). | | Does the change alter how customer data is processed? | Yes. Content is transcribed and processed by Microsoft 365 Copilot to generate structured insights. | | Does the change introduce AI capabilities interacting with data? | Yes. Copilot analyzes captured content to generate summaries, decisions, and action items. | | Does the change provide new interaction with generative AI? | Yes. Users interact with Copilot-generated outputs based on captured multimodal data. | | Does the change add a third party integration? | Yes. Supports capture from browser-based meetings including Zoom, Webex, and Google Meet. | | Does the change include admin control? | Yes. Admins can disable the feature using a policy setting. |
|
| Windows Server 2022 hotpatch update support extended through October 2027Category:WindowsNummer:MC1405556Status:stayInformed | What and why
Hotpatching is designed to deliver protections against security threats without requiring a device restart. By applying updates directly to running processes, hotpatching helps maintain uptime, reduces servicing disruptions, and shortens the time it takes to respond to vulnerabilities. This extension allows organizations to continue benefiting from these capabilities for an additional year while maintaining the same update experience.
Rollout schedule This change is effective immediately. Hotpatch update support, previously scheduled to end in October 2026, will now continue through October 2027. The existing monthly hotpatch update cadence remains unchanged.
Impact on your organization This change applies to devices running Windows Server 2022 Datacenter: Azure Edition that are enrolled in hotpatch updates.
Devices receiving hotpatch updates continue to get monthly security updates without requiring a restart between baseline months, helping maintain availability for critical workloads. There are no changes to how hotpatch updates are delivered or applied.
Action required/recommendations No action is required.
Compliance considerations No compliance considerations are identified. Review as appropriate for your organization. |
