| Update Principal owner of a SharePoint Embedded user-owned container through SPAC and PowerShellCategory:SharePoint OnlineNummer:MC1152315Status:stayInformed | [Introduction]
To improve administrative control and support organizational transitions, SharePoint Embedded now allows administrators to update the principal owner of user-owned containers directly through the SharePoint Admin Center (SPAC) or via SharePoint PowerShell cmdlets. This update addresses common scenarios such as user departures or team restructuring.
[When this will happen:]
General Availability (Worldwide): Rollout will begin in late September 2025 and is expected to complete by late October 2025.
[How this affects your organization:]
- Who is affected: SharePoint administrators managing user-owned containers in SharePoint Embedded.
- What will happen:
- Admins will be able to update the principal owner of user-owned containers via SPAC or PowerShell.
- This capability is limited to user-owned containers only.
- The update helps maintain continuity and access control when users leave or teams change.
- No changes will be made to existing containers unless action is taken by an admin.
- The feature will be available by default on SPAC; no opt-in required.
- The feature will not be readily available by default on PowerShell. The admin has to update it to the latest version.
[What you can do to prepare:]
- Review user-owned containers that may need ownership updates.
- Use SPAC to select a container and update the principal owner via the General tab.
- Alternatively, use the updated SharePoint PowerShell cmdlets to perform the same action. Ensure your SharePoint PowerShell module is updated to the latest version.
- Communicate this change to helpdesk or support teams.
- Update internal documentation if ownership management is referenced.
[Compliance considerations:] No compliance considerations identified, review as appropriate for your organization. |
| Membership management of SharePoint Embedded containers through PowerShellCategory:SharePoint OnlineNummer:MC1152317Status:stayInformed | [Introduction]
We’re introducing new PowerShell cmdlets that allow SharePoint Embedded administrators to manage container membership directly through PowerShell. This update provides greater flexibility and automation capabilities, reducing reliance on the SharePoint Admin Center for user role management.
[When this will happen:]
General Availability (Worldwide): Rollout will begin in late September 2025 and is expected to complete by late October 2025.
[How this affects your organization:]
- Who is affected: SharePoint Embedded administrators using PowerShell to manage container roles.
- What will happen:
- New PowerShell cmdlets will be available:
- Admins can add, update, or remove users from container roles without using the SharePoint Admin Center.
- No changes will be made automatically; admins must use the cmdlets to manage roles.
[What you can do to prepare:]
- Ensure your SharePoint PowerShell module is updated to the latest version.
- Review internal documentation or automation scripts that manage container membership.
- Communicate this change to your SharePoint administration team.
- Learn more: Get started with SharePoint Online Management Shell
[Compliance considerations:]
No compliance considerations identified, review as appropriate for your organization. |
| New filtering capability for SharePoint Embedded containers using sensitivity labelsCategory:SharePoint OnlineNummer:MC1152318Status:planForChange | [Introduction]
To enhance compliance management, SharePoint Embedded now supports filtering containers by sensitivity label. This update enables administrators to more effectively organize and manage containers based on their sensitivity classification, aligning with organizational data governance needs.
[When this will happen:]
General Availability (Worldwide): Rollout will begin in late October 2025 and is expected to complete by late November 2025.
[How this affects your organization:]
Who is affected:
Admins managing SharePoint Embedded containers.
What will happen:
- A new filter option will be available to sort containers by sensitivity label.
- This feature will be ON by default for all tenants.
- Existing sensitivity label configurations will be respected.
- No impact to user workflows unless admins take action to apply filters.
[What you can do to prepare:]
- Review your current sensitivity label taxonomy to ensure it aligns with container management goals.
- Communicate this update to SharePoint Embedded admins and helpdesk staff.
- Update internal documentation if you reference container filtering capabilities.
- Learn more about sensitivity labels in SharePoint Embedded
[Compliance considerations:]
No compliance considerations identified, review as appropriate for your organization. |
| eSignature: Free text field support in WordCategory:Microsoft 365 suite
Microsoft 365 appsNummer:MC1152319Status:stayInformed | [Introduction:] We’re adding support for free text fields in eSignature requests within Word. This enhancement allows users to collect custom information—such as job title, phone number, address, or full name—from signers, improving flexibility and alignment with real-world document workflows. This update is associated with Microsoft 365 Roadmap ID 499024. [When this will happen:] General availability (Worldwide): We will begin rolling out in early October 2025 and expect to complete by early January 2026. [How this affects your organization:] Who is affected: Users and admins in tenants with eSignature enabled in Microsoft Word. What will happen: - Users will be able to insert free text fields into eSignature requests in Word documents.
- These fields can be used to collect custom information from signers.
- The feature will be ON by default for tenants with eSignature enabled.
- No changes to existing admin policies are required.
- There is no impact to end-user workflow unless eSignature is enabled.
Screenshot 1 – Create a signature request: 
Screenshot 2 – View of document with signature: 
[What you can do to prepare:] - If eSignature is already enabled in your tenant, no action is required.
- If not enabled, you can turn it on in the Microsoft 365 admin center.
- To enable eSignature, follow the instructions at Overview of eSignature | Microsoft 365 | Microsoft Learn.
- Consider notifying helpdesk staff and updating internal documentation to reflect this new capability.
[Compliance considerations:]No compliance considerations identified, review as appropriate for your organization. |
| Microsoft Defender for Office 365: Enhanced email entity page experienceCategory:Microsoft Defender XDRNummer:MC1152320Status:stayInformed | [Introduction:] We’re introducing a streamlined experience for the email entity page in Microsoft Defender for Office 365. This update improves how users navigate between email records, reducing friction and enhancing productivity. The changes are based on customer feedback to simplify workflows and reduce time spent switching between tabs. [When this will happen:] - Public Preview: We will begin rolling out late September 2025 and expect to complete by late October 2025.
- General Availability (Worldwide): We will begin rolling out early November 2025 and expect to complete by late November 2025.
[How this affects your organization:] Who is affected: - Security analysts and administrators using Microsoft Defender for Office 365.
- Users accessing email entities via security.microsoft.com (Explorer, Advanced Hunting, Quarantine, etc.).
- This feature is available to tenants licensed with Microsoft Defender for Office 365 Plan 2 or with Microsoft security licenses such as E5 and above.
What will happen: - Email entity pages will open in a shared browser tab instead of launching a new tab for each record.
- A parent-child relationship is established between the main security.microsoft.com tab and the shared email entity tab. If the same or new email is opened again from the parent tab, it switches to the already-open shared tab.
- If the parent tab is closed or refreshed, this relationship is reset. A new shared email entity tab will be opened the next time an email entity is accessed from the refreshed or newly opened parent tab.
- Navigation positions within each email entity are retained during the session (e.g., Analysis tab vs. Timeline tab).
- A new “Email preview” tab is added alongside “Similar emails,” allowing persistent preview even when switching tabs.
- Each email entity now has a unique URL, enabling direct sharing via Teams or opening in a new browser tab.
[What you can do to prepare:] - No action is required from end users or administrators.
- You may wish to inform helpdesk staff of the new navigation behavior for email entities.
Learn more: [to be updated] The Email entity page in Microsoft Defender for Office 365 – Microsoft Defender for Office | Microsoft Learn [Compliance considerations:] No compliance considerations identified, review as appropriate for your organization. |
| (Teams Premium) Customize the screen in Teams Town hall through “Manage what attendees see”Category:Microsoft TeamsNummer:MC1152321Status:planForChange | [Introduction]
Coming soon to Microsoft Teams: the new Manage what attendees see feature will empower organizers and presenters to deliver more engaging and professional town hall events. With enhanced customization options—including layouts, backgrounds, theme colors, and name tags—this update supports a visually rich experience. This feature is available exclusively to organizers with a Teams Premium license.
This update applies to Teams for Windows desktop, Mac desktop, web, and Teams Rooms.
This message is associated with Microsoft 365 Roadmap ID 491633
[When this will happen:]
- Targeted Release: early October 2025 – mid-October 2025
- General Availability (Worldwide): late October 2025 – early November 2025
[How this affects your organization:]
Who is affected:
- Organizers and presenters of town hall events using Microsoft Teams with a Teams Premium license.
What will happen:
- Organizers and presenters will be able to customize the screen with new layouts, backgrounds, theme colors, and name tags.
- The updated Manage what attendees see feature will support both On and On with preview options.
- The new experience will be automatically enabled when either option is selected.
- Feature is only available for Town hall events.
- New meetings or events created after late October 2025 will include the updated experience by default.
[What you can do to prepare:]
- No admin action is required before rollout.
- Notify users who organize or present town halls about this change.
- Update internal documentation where applicable.
- Review the updated Manage what attendees see in Teams meetings documentation (link will be provided before rollout).
- Conduct a test session with the feature enabled to become familiar with the new controls.
[Compliance considerations:]
No compliance considerations identified, review as appropriate for your organization. |
| Expanding Microsoft 365 Copilot Search admin experience to AI admin roleCategory:Microsoft 365 appsNummer:MC1152322Status:stayInformed | We’re introducing a new AI Admin Role for Microsoft 365 Copilot Search to provide organizations with enhanced control and flexibility in managing AI-powered search experiences. This role enables designated admins to configure, monitor, and govern Copilot Search capabilities across their tenant.
When this will happen:
General Availability (Worldwide): Rollout begins mid-September 2025 and is expected to complete by September 22, 2025.
How this affects your organization:
- Admins assigned the new AI Admin Role will be able to manage Copilot Search settings and capabilities for their organization.
- This feature is on by default for tenants with eligible licenses and assigned roles.
- No changes will be made to existing admin roles unless explicitly assigned.
What you can do to prepare:
- Ensure that designated admins are assigned the AI Admin Role.
- Confirm that your organization has the Microsoft 365 Copilot license.
- Review role assignment practices in Microsoft Entra ID to manage access.
Learn more: About admin roles in the Microsoft 365 admin center – Microsoft 365 admin | Microsoft Learn Compliance considerations: | Does the change introduce or significantly modify AI/ML or agent capabilities that interact with or provide access to customer data? | Yes. This update introduces the AI Admin Role, which enables designated administrators to manage AI-powered Copilot Search experiences that interact with customer data across Microsoft 365 services. | | Does the change alter how existing customer data is processed, stored, or accessed (e.g., documents, emails, chats, etc.)? | Yes. AI-powered search may surface data across services based on user permissions, potentially altering how data is accessed and presented.
| | =Does the change provide end users any new way of interacting with generative AI? | Yes. Copilot Search enhances the user experience by enabling generative AI-powered search capabilities across Microsoft 365. | | Does the change alter how admins can monitor, report on, or demonstrate compliance activities (e.g., Purview or admin reporting)? | Yes. The AI Admin Role includes new governance and monitoring capabilities for Copilot Search, allowing admins to oversee AI interactions and usage. | | Does the change include an admin control and can it be controlled through Entra ID group membership? | Yes. Admin access to Copilot Search capabilities is managed via the AI Admin Role, which can be assigned and controlled through Microsoft Entra ID group membership. |
|
| Microsoft 365 Copilot Apps installation on devices with Microsoft 365 AppsCategory:Microsoft 365 apps
Microsoft Copilot (Microsoft 365)
Microsoft 365 Copilot ChatNummer:MC1152323Status:planForChange | Introduction Starting in October 2025, Microsoft will begin automatically installing the Microsoft 365 Copilot app on Windows devices that have Microsoft 365 desktop client apps. This app provides a centralized entry point for accessing Copilot experiences and AI-powered capabilities across Microsoft 365. This change simplifies access to Copilot and ensures users can easily discover and engage with productivity-enhancing features. When this will happen Rollout begins in early October 2025 and completes mid-November 2025 How this affects your organization Who is affected: - Organizations with Windows devices running Microsoft 365 desktop client apps
- Customers outside the European Economic Area (EEA) (EEA customers are excluded)
- Admins responsible for managing Microsoft 365 Apps deployments
- Users on eligible devices who will see the Microsoft 365 Copilot app appear in their Start menu
What will happen: - The Microsoft 365 Copilot app will be automatically installed on Windows devices that have Microsoft 365 desktop apps, unless administrators opt out.
- The app will appear in the Start menu as a new entry point for accessing Copilot experiences across Microsoft 365.
- On devices where the app is already installed, no visible change will occur.
- The app installation is enabled by default and does not require user interaction.
- This change does not apply to customers in the European Economic Area (EEA).
What you can do to prepare Admin Actions - Review the documentation for more details and instructions on how to manage this.
- You can opt out of the installation in the Microsoft 365 Apps Admin Center.
- Consider notifying helpdesk and users to reduce confusion and support requests.
- Update internal documentation if you reference installed apps or Copilot access points.
User Impact - Users may see a new app icon for Microsoft 365 Copilot in the Start menu.
- On many devices, the app may already be installed, resulting in no visible change
Compliance considerations
No compliance considerations identified, review as appropriate for your organization.
|
