| (Updated) Transitioning Teams Android Device Management from Teams admin Center to the Teams Rooms Pro Management portalCategory:Microsoft Teams
Microsoft 365 for the webNummer:MC1227622Status:planForChange | Updated July 2, 2026: We have updated the timeline. Thank you for your patience. [Introduction]
As part of our ongoing mission to deliver a modern, secure, and scalable one-stop management portal for admins, we are transitioning Teams Android device management from the Teams admin center (TAC) to the Teams Rooms Pro Management portal (PMP).
This move consolidates management of all Teams devices, including Teams Rooms on Windows, Teams Rooms on Android, Teams phones, and Teams panels, into a single unified portal, providing IT admins a consistent and seamless experience for managing devices at scale. This message is associated with Roadmap ID 555235.
[When this will happen:] - General Availability (Worldwide): Effective July 2, 2026, the rollout is 100% complete across all regions in the Public cloud.
- General Availability (GCC High and DoD): We expect to complete the rollout by late-July 2026.
- General Availability (GCC): We expect to complete the rollout by late-August 2026.
- Device management deprecation in TAC: We will start the deprecation for Public cloud customers in August and expect to complete by end of September 2026 in all the clouds.
[How this affects your organization:] Who is affected: Admins who manage Teams Rooms on Android, Teams phones, Teams panels, and SIP Phones. What will happen:
- By end of June 2026, Android device management capabilities, including inventory, updates, health monitoring, and settings will transition from TAC to PMP for the device types, Teams Rooms on Android, Teams phones, Teams panels and SIP Phones.
- The following capabilities will be available and enhanced in PMP:
- Device inventories for Android-based Teams Rooms, phones, and panels, including metadata and app information
- Remote device actions (restart, log collection, sign-in/out, provisioning, and more)
- Update management
- Device settings management
- Device health monitoring
- SIP device management
- PMP will become the primary portal for all Teams device management. By September 2026, overlapping TAC capabilities (updates, settings, restart, sign-in/out, log collection, provisioning) will be deprecated in TAC.
- The article below serves as the main information source for this transition. It has been updated with the latest timelines, milestones, migration guidance, and readiness steps. We will keep updating it as the rollout progresses.
[What you need to do to prepare:]
- Monitor the below article for any feature specific updates and timelines. This article also provides migration guidance and pre-requisites for successful transition to PMP.
- Learn more about Pro Management portal features with these Teams Rooms Pro Management short YouTube videos.
- Update internal helpdesk and IT documentation to reference PMP as the new management portal.
[Compliance considerations] No compliance considerations identified, review as appropriate for your organization. |
| (Updated) SharePoint Designer 2013 reaches end of support on July 14, 2026Category:SharePoint OnlineNummer:MC1230891Status:planForChange | Updated July 2, 2026: We are updating this post as a reminder. Thank you for your patience. [Introduction] Microsoft is retiring SharePoint Designer 2013, which follows the Microsoft Fixed Lifecycle Policy and will reach end of support on July 14, 2026. This retirement aligns with our commitment to modernize workflow automation and customization experiences using supported tools such as Power Automate. [When this will happen] End of support begins in mid-July 2026, with retirement enforcement occurring between mid-July and late July 2026 across all Microsoft 365 environments (Worldwide, GCC, GCC High, and DoD). [How this affects your organization] Who is affected: Organizations that use SharePoint Designer 2013 for SharePoint workflows or site customizations. What will happen: - Microsoft will no longer provide support, security updates, or fixes for SharePoint Designer 2013.
- No extensions or exceptions will be offered beyond the retirement date.
- Workflows built with SharePoint Designer 2013 will require migration to supported alternatives such as Power Automate.
- The SharePoint Migration Tool (SPMT) can migrate supported workflow actions to Power Automate.
[What you can do to prepare] We recommend the following actions before July 14, 2026: - Review existing SharePoint Designer 2013 workflows and customizations.
- Plan and complete migration to supported technologies.
- Update internal documentation, helpdesk knowledge bases, and user communications.
- Use the SharePoint Migration Tool (SPMT) 4.1 to assess and migrate supported workflow actions to Power Automate.
- Note: The SharePoint Migration Tool lets you migrate SharePoint Designer 2013 workflows to Power Automate.
- Review SharePoint Designer 2013 lifecycle details and workflow migration guidance as part of your planning.
No extension options will be available after the retirement date. Learn more: [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization.
|
| (Updated) Microsoft 365 Copilot app: Branded footer customizationCategory:Microsoft Copilot (Microsoft 365)
Microsoft 365 Copilot ChatNummer:MC1238432Status:stayInformed | Updated July 2, 2026: We have updated the timeline. Thank you for your patience. [Introduction] We’re introducing a new co-branding capability that will allow organizations to display a branded footer at the bottom of the Chat screen in the Microsoft 365 Copilot app. This update will enable admins to add their organization’s logo to their users’ Microsoft 365 Copilot app, helping users confirm they are using their trusted, work-managed Copilot experience. This feature began rolling out end of June 2026 (previously early May) and is expected to complete by early July 2026 (previously mid-June). This message is associated with Microsoft 365 Roadmap ID 555852. [When this will happen] - General Availability (Worldwide): Began rolling out end of June 2026 (previously early May) and is expected to complete by early July 2026 (previously mid-June).
[How this will affect your organization] Who is affected - All Microsoft 365 tenants using the Microsoft 365 Copilot app.
What will happen - Admins will be able to upload a logo in the Microsoft 365 admin center to customize the footer in the Microsoft 365 Copilot app.
- The footer will display an “Approved by [Logo]” indicator to help users confirm they are in an organization-approved Copilot environment:
- Only the logo from your organization’s theme configuration will be used; other theme elements will not be applied in this release.
- This feature will be off by default and will require admin configuration.
- There will be no user impact unless an admin enables the footer.
[What you can do to prepare] No action will be required unless you want to enable the branded footer. Admins who want to configure this feature should: - Review and verify your organization’s theme configuration in the Microsoft 365 admin center.
- Upload the logo you want to display in the Microsoft 365 Copilot app footer once rollout begins.
- Use the existing theme management flow to apply co-branding once the feature is available.
For configuration guidance: Customize the theme for your organization | Microsoft 365 | Microsoft Learn [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. |
| (Updated) Publishing InfoPath Forms in SharePoint Online will not be allowed for all tenantsCategory:SharePoint OnlineNummer:MC1255407Status:planForChange | Updated July 2, 2026: We are updating this post as a reminder. Thank you for your patience. Introduction
As announced earlier in MC616550 (June 2023), InfoPath Forms Service in SharePoint Online is being retired and will be removed from existing tenants after July 14, 2026. To support this transition and reduce future migration effort, Microsoft will prevent the publication of InfoPath forms in SharePoint Online for all tenants ahead of the service’s retirement.
When this will happen:
- After May 18, 2026: Publishing new InfoPath forms or publishing updates to existing forms will be blocked
- July 14, 2026: InfoPath Forms Service will be fully retired
How this affects your organization:
Who is affected:
- All SharePoint Online tenants
- InfoPath designers, publishers, and site owners
- IT administrators managing SharePoint Online
What will happen:
- After May 18, 2026, new InfoPath forms cannot be published
- Modifications to existing InfoPath forms cannot be published
- Existing published forms will remain available and usable
- There is no option to extend InfoPath Forms Service beyond retirement
What you can do to prepare:
To understand how InfoPath is used in your organization, you can run the Microsoft 365 Assessment tool to scan the tenant for InfoPath usage. Using the Power BI InfoPath Report generated by the scanner tool, you can:
- Identify all InfoPath Forms usage in the tenant, per site collection and site.
- Evaluate the recency and volume of usage of InfoPath Forms.
- Understand lists, libraries, and content types that use InfoPath.
We recommend communicating to the impacted site owners and teams inside your organization now, so they are aware of the coming change.
For scenarios where InfoPath or InfoPath Forms Services are currently being used, we recommend migrating to Power Apps, Power Automate, or Microsoft Forms. Please ensure that you allow adequate time for migration of any use of InfoPath or InfoPath Forms Services in your organization ahead of this date, as there is no migration tool provided. Additional instructions on how to migrate can be found in this blog.
Note: Please plan the migration appropriately as there will not be an option to extend InfoPath Forms Services beyond the InfoPath retirement date of July 14, 2026.
Compliance considerations:
This update disables the ability to publish or republish InfoPath forms in SharePoint Online as part of a planned service retirement; it does not change how existing customer data is stored, processed, or governed. |
| (Updated) General Availability: Microsoft Entra passkeys on WindowsCategory:Microsoft EntraNummer:MC1282568Status:stayInformed | Updated July 1, 2026: We have updated the timeline. Thank you for your patience. [Introduction]
Microsoft Entra passkeys on Windows will soon be Generally Available, enabling phishing‑resistant, passwordless sign‑in to Microsoft Entra‑protected resources from Windows devices. The Public Preview of this capability was previously announced in MC1247893. Users can create device‑bound passkeys stored in the Windows Hello container and authenticate using Windows Hello methods (face, fingerprint, or PIN). This expands passwordless authentication support to Windows devices that aren’t Microsoft Entra‑joined or registered, helping organizations strengthen security and reduce reliance on passwords across corporate‑managed, personal, and shared device scenarios.
[When this will happen:]
- General Availability (Worldwide): We will begin rolling out in late April 2026 and expect to complete by mid‑June 2026.
- General Availability (GCC, GCC High, DoD): We will begin rolling out in early September 2026 (previously early July) and expect to complete by late September 2026 (previously late July).
How this affects your organization:
Who is affected:
Organizations using Microsoft Entra ID with passkeys enabled in the Authentication Methods policy whose users sign in from Windows devices, including: - Corporate‑managed PCs
- Personal devices
- Shared devices
What will happen: With this General Availability release:
- Microsoft Entra passkeys on Windows will no longer require explicit opt‑in through Windows Hello AAGUID allow‑listing in a passkey (FIDO2) profile.
- This represents a change from Public Preview behavior, where administrators were required to explicitly allow Windows Hello AAGUIDs in a passkey profile for Microsoft Entra passkeys on Windows to function.
- If your passkey profile allows device‑bound, non‑attested passkeys:
- Users scoped to that profile will now be able to register and use Microsoft Entra passkeys on Windows by default without additional administrator configuration.
- As a result:
- Users in scope of passkey profiles that allow device‑bound, non‑attested passkeys may begin registering and using passkeys on Windows devices.
- If Conditional Access policies allow:
- Passkeys can be created and used on Windows devices that are not Microsoft Entra‑joined or registered, including personal or shared PCs.
- Each Windows device requires separate passkey registration per Entra account.
- Windows Hello for Business remains recommended for managed, Microsoft Entra‑joined or registered devices.
- Passkeys on Windows supplement unmanaged or shared device scenarios and do not support device sign‑in.
- Attestation is not currently supported for Microsoft Entra passkeys on Windows but is planned for a future update.
What you can do to prepare:
No action is required for most organizations. If you do not want users to register or use Microsoft Entra passkeys on Windows:
- Update the relevant passkey (FIDO2) profile to block Windows Hello AAGUIDs.
- Review existing passkey profiles that allow device‑bound, non‑attested passkeys.
- Add Windows Hello AAGUIDs to the block list in passkey profiles where passkey usage on Windows devices should not be permitted.
Learn more: Enable Microsoft Entra passkey on Windows | Microsoft Learn (will be updated before GA rollout) [Compliance considerations:] | Compliance area | Explanation | | Does the change modify, interrupt, or disable Conditional Access policies? | Existing Conditional Access policies continue to govern whether passkeys can be created or used on unmanaged Windows devices. | | Does the change include an admin control and can it be controlled through Entra ID group membership? | Admins can control passkey availability through Authentication Methods policies and FIDO2 passkey profiles scoped to Microsoft Entra ID groups. | | Does the change allow a user to enable and disable the feature themselves? | Users may register Microsoft Entra passkeys on Windows devices if permitted by administrator policy configuration. |
|
| (Updated) Microsoft 365 Copilot: Copilot chat pane and Summary feature in OneNote Mobile (Android)Category:Microsoft 365 apps
Microsoft Copilot (Microsoft 365)Nummer:MC1309746Status:stayInformed | Updated July 2, 2026: We have updated the timeline. Thank you for your patience. [Introduction] Microsoft is introducing a new Copilot chat pane in OneNote Mobile (Android) for users licensed with Microsoft 365 Copilot (Premium). This update adds a new Summary feature that allows users to generate concise summaries of longer OneNote pages, as well as ask questions about their notes, directly within the OneNote mobile app. This helps users review and interact with note content more efficiently while on the go. This message is associated with Microsoft 365 Roadmap ID 422323. [When this will happen] General Availability (Worldwide): We will begin rolling out end of July 2026 (previously end of June) and expect to complete by early August 2026 (previously mid-July). [How this affects your organization] Who is affected - Users with Microsoft 365 Copilot (Premium) licenses
- Users accessing OneNote on Android
- All Microsoft 365 tenants
What will happen - Users with a Microsoft 365 Copilot (Premium) license will see a Copilot chat pane in the OneNote mobile app on Android:
- The Copilot chat pane allows users to generate concise summaries of longer OneNote pages and ask questions about their notes:
- Existing Microsoft 365 Copilot controls, permissions, and policies continue to apply.
- Users without a Microsoft 365 Copilot (Premium) license are not impacted.
[What you can do to prepare] - No admin action is required before rollout.
- Ensure that users who should access this feature are assigned a Microsoft 365 Copilot (Premium) license.
- Consider informing helpdesk staff and users about the availability of Copilot chat and the Summary feature in OneNote mobile.
- Review existing Microsoft 365 Copilot governance, compliance, and usage policies to ensure they align with your organization’s requirements.
[Compliance considerations] | Question | Answer | | Does the change alter how existing customer data is processed, stored, or accessed? | Yes. Copilot chat processes OneNote content that users already have access to in order to generate summaries and answer questions, in accordance with existing Microsoft 365 Copilot data handling, permissions, and security controls. | | Does the change introduce or significantly modify AI or ML capabilities that interact with customer data? | Yes. This update introduces Copilot chat capabilities within OneNote Mobile, allowing generative AI to analyze note content that the user has permission to access. | | Does the change provide end users a new way of interacting with generative AI? | Yes. Users can interact with generative AI through the Copilot chat pane in OneNote Mobile to summarize content and ask questions about their notes. |
|
| (Updated) Microsoft Teams: A refreshed in-meeting experience with simpler controls and a smarter share panelCategory:Microsoft TeamsNummer:MC1317197Status:planForChange | Updated July 1, 2026: We have updated the content. Thank you for your patience. [What and Why]
As Microsoft Teams has added meeting capabilities over time, the meeting controls and share panel have grown crowded, contributing to mis-clicks between high‑impact actions like Share, Leave, and Raise hand, and to accidental shares of unintended content. Drawing on extensive customer feedback and telemetry, we’re introducing two coordinated updates: redesigned meeting and sharing controls. Together, they make core actions easier to find, reduce accidental clicks, and give users more confidence when sharing content. This update supports personal and team productivity by reducing friction in everyday meetings and improving confidence when presenting or sharing content. This message is associated with Microsoft 365 Roadmap ID 560321 and 502520. It applies to Teams for Windows desktop, Teams for Mac desktop, and Teams for the web. [Rollout Schedule]
- Targeted Release: We will begin rolling out redesigned meeting controls in early July 2026 and expect to complete by late July 2026. Redesigned Sharing controls will begin rolling out in Aug 2026.
- General Availability (Worldwide): We will begin rolling out in early September 2026 (previously early August) and expect to complete by late September 2026 (previously late August).
- General Availability (GCC, GCC High): We will begin rolling out in early October 2026 (previously early September) and expect to complete by late November 2026 (previously late October).
- General Availability (DoD): We will begin rolling out in early November 2026 (previously early October) and expect to complete by late December 2026 (previously late November).
[Impact on Your Organization]
Who is affected: - All Teams work and school users joining meetings
Platforms: - Teams for Windows desktop
- Teams for Mac desktop
- Teams for the web
- Not in scope: Teams (consumer), iOS, Android, Teams Rooms, Linux
What will happen:
- Meeting controls will be center‑aligned, with microphone, camera, and share grouped together.
- The Leave button will be separated to reduce accidental exits.
- Less‑used actions will move into a reorganized More menu.
- Users can personalize meeting controls by pinning, unpinning, and rearranging controls using drag and drop.
Screenshot: New More options menu 
- Users can personalize meeting controls by pinning, unpinning, and rearranging controls using drag and drop.
- The redesigned share panel may include:
- Live previews of screens and windows.
- A tabbed layout
- A two‑step share confirmation to reduce accidental sharing.
Screenshot: Reorganized share panel – not final UI 
- The new experience is enabled by default and cannot be disabled at the tenant level.
- During rollout, users may opt in early and can temporarily return to the previous experience from Teams settings.
- Existing meeting app pinning policies will continue to be honored.
- New meeting app pinning policies will support up to two apps pinned to the main meeting controls, with additional apps available in the More menu.
Known limitations: - Meeting controls customization preferences (such as pinned controls) do not sync across devices at launch. Preferences persist across meetings on the same client. Cross‑device sync is planned for a future release.
- The opt‑out toggle for the new meeting experience is controlled by individual users and cannot be managed at the tenant level. This opt‑out is a temporary adoption aid and will be retired in a future release. Microsoft will provide advance notice via a separate Message Center post before removal.
[Action Required / Recommendations]
No immediate action is required. We recommend that you: - Review existing Teams meeting app pinning policies and plan future policies around the two‑app limit.
- Communicate the redesiged meeting control changes to users, helpdesk, and internal support teams ahead of the July 2026 rollout. Detailed change management guidance for IT Pros/admins, along with an end user visual guide will be published on July 9th 2026: https://adoption.microsoft.com/microsoft-teams/new-meeting-controls-experience.
- Update internal documentation and training materials to reflect:
- The new meeting controls layout.
- User customization options.
- The updated share panel experience.
[Compliance Considerations]
No compliance considerations identified, review as appropriate for your organization. |
| (Updated) Microsoft 365 Copilot: Get suggested edits from Copilot in your Copilot PagesCategory:Microsoft 365 apps
Microsoft Copilot (Microsoft 365)Nummer:MC1330886Status:stayInformed | Updated July 2, 2026: We have updated the timeline. Thank you for your patience. [What and Why] We are introducing Copilot‑generated suggested edits in Copilot Pages to help users improve the clarity and quality of their content without leaving their workflow. This enhancement brings AI‑powered writing feedback directly into the page experience, enabling users to review and apply actionable suggestions in context. This aligns with our goal to improve personal and team productivity by helping users create higher‑quality content more efficiently. This message is associated with Microsoft 365 Roadmap ID 562351. [Rollout Schedule] - Frontier: We will begin rolling out to Frontier Private and Public in early June 2026.
- General Availability (Worldwide): We will begin rolling out in late July 2026 (previously late June) and expect to complete by early August 2026 (previously mid-July).
[Impact on Your Organization] Who is affected Users with access to Microsoft 365 Copilot and Copilot Pages Platforms/Services - Copilot Pages (web)
- Microsoft 365 Copilot
What will happen - Users can request writing feedback directly within Copilot Pages using Copilot Shortcuts or Copilot Chat.
- A new Suggest edits option will be available:
- Copilot analyzes page content and generates suggestions to improve clarity and writing quality.
- Suggestions appear as comment-like cards in a right-hand sidebar aligned to relevant content.
- Each suggestion can be applied with a single click using an Apply button.
- The feature is available by default to eligible users; no additional configuration is required.
- Existing Copilot policies and permissions are respected.
[Action Required / Recommendations] No action is required. Admins may consider the following: - Inform users about the availability of suggested edits in Copilot Pages.
- Share guidance on accessing suggestions via Copilot Shortcuts or Copilot Chat.
- Set expectations that Frontier releases are early experiences intended for feedback and validation.
- Monitor usage and feedback as users adopt this capability.
- Review Copilot access and ensure Copilot Pages and OneDrive for Business remain enabled.
Learn more: [Compliance considerations] | Question | Answer | | Does the change introduce or significantly modify AI/ML capabilities that interact with customer data? | Yes. Copilot analyzes page content and generates suggestions based on user-authored content within Copilot Pages. | | Does the change provide end users a new way to interact with generative AI? | Yes. Users can directly request and apply AI-generated writing suggestions within Copilot Pages. | | Does the change allow a user to enable/disable the feature themselves? | Yes. Users can choose when to invoke suggested edits via Copilot Shortcuts or Chat. |
|
| (Updated) Copilot Notebooks available in Microsoft 365 Copilot Chat for Basic usersCategory:Microsoft 365 apps
Microsoft 365 Copilot ChatNummer:MC1384425Status:stayInformed | Updated July 2, 2026: We have updated the timeline. Thank you for your patience. [What and Why] Copilot Notebooks will be available in Microsoft 365 Copilot Chat for users with Copilot Chat (Basic) and M365 Copilot (Basic) experiences. This update expands Copilot Notebooks beyond users with a Microsoft 365 Copilot add-on license to include additional Copilot Chat users. Copilot Notebooks provides a persistent, AI-powered workspace where users can organize content, add references, and interact with Copilot to reason over their materials in one place. [Rollout Schedule] - General Availability (Worldwide): Rollout will begin in mid-June 2026.
[Impact on Your Organization] Who is affected - Users with access to Copilot Chat (Basic) and M365 Copilot (Basic) experiences
- Copilot Notebooks availability varies by endpoint.
- Admins managing Copilot, Loop, and SharePoint storage
Platforms/Services - Microsoft 365 Copilot Chat (web)
- Microsoft Loop / SharePoint Embedded
- SharePoint Embedded (Loop-backed storage)
- Web, desktop, and mobile
- Only Copilot Notebooks in OneNote on web will be available to Copilot Chat (Basic) commercial customers at this time.
What will happen - Copilot Notebooks will be available to eligible users in Microsoft 365 Copilot Chat. This includes users with:
- Copilot Chat (Basic)
- M365 Copilot (Basic)
- Copilot Notebooks in OneNote will not be available to Copilot Chat (Basic) users at this time.
- Users can create persistent notebooks to organize content with Copilot.
- Notebook content is stored in user-owned SharePoint Embedded containers shared with Microsoft Loop.
- These containers appear as “Loop” in the SharePoint admin center, PowerShell, and Microsoft Purview.
- Notebook content counts toward your organization’s SharePoint storage quota.
- Existing admin configurations and policies for Copilot Notebooks and Loop (including Cloud Policy) are respected.
- The feature is enabled by default where Copilot Notebooks is allowed.
- Documentation describing Copilot Notebooks availability will be updated to reflect this change.
[Action Required / Recommendations] No immediate action is required. You may want to: - Review your Copilot Notebooks and Loop configuration to ensure alignment with your organization’s policies.
- Review SharePoint storage usage, as Copilot Notebooks content contributes to tenant storage.
- Inform helpdesk and end users about this new capability.
Learn more: [Compliance considerations] | Question | Answer | | Does the change store new customer data, if so, where, and is the data cached or permanently stored? | Yes. Notebook content is stored in user-owned SharePoint Embedded (Loop-backed) containers and persists as part of SharePoint storage. | | Does the change introduce or significantly modify AI/ML or agent capabilities that interact with or provide access to customer data, if so summarize changes? | Yes. Copilot Notebooks introduce a persistent workspace where Copilot operates over user content. | | Does the change provide users any new way of interacting with generative AI, if so how? | Yes. Users interact with Copilot within notebooks to work across content. |
|
| (Updated) Microsoft Purview compliance portal: Admin assignment time limitCategory:Microsoft PurviewNummer:MC1411431Status:stayInformed | Updated July 2, 2026: We have updated the content and timeline. Thank you for your patience. [What and Why:]
Microsoft Purview is introducing the ability to assign a time limit when adding users or security groups to role groups. Administrators can specify an expiration date from 1 day up to 2 years, enabling temporary administrative access and supporting least-privilege security practices. This enhancement helps organizations improve governance and compliance while reducing the risk of unnecessary long-term privileged access.
[Rollout Schedule:]
- General Availability (Worldwide): Beginning late July 2026; expected to complete by late August 2026
- General Availability (GCC, GCC High, DoD): Beginning late August 2026; expected to complete by late September 2026
[Impact on Your Organization:]
Who is affected:
- Microsoft Purview administrators
- Security and compliance administrators
- Organizations using Purview role groups in Worldwide, GCC, GCC High, and DoD environments
Platforms/Services:
- Microsoft Purview compliance portal
- Microsoft Defender portal
- Microsoft Purview RBAC
What will happen:
- Administrators can assign users or security groups to role groups with a defined expiration period.
- Assignment durations can range from 1 day to 2 years.
- The capability applies to existing and new assignments.
- Existing assignments are not modified automatically.
- No impact to user workflows.
- The feature is available by default after rollout.
- No policy or configuration changes are required.
[Action Required/Recommendations:]
No action is required. We recommend that you:
- Review privileged access management processes.
- Consider using assignment expiration periods for temporary access scenarios.
- Update internal documentation where appropriate.
- Inform Purview administrators of the new capability.
[Compliance Considerations:]
| Compliance Consideration |
Assessment |
| Does the change alter how admins can monitor, report on, or demonstrate compliance activities? |
Temporary role group assignment limits may support governance and audit reviews of administrative access, but the announcement does not describe new reporting, monitoring, or compliance reporting capabilities. |
| Does the change include an admin control and can it be controlled through Entra ID group membership? |
Admins can configure a time limit (1 day to 2 years) for new or existing role group assignments. The feature applies to both users and security groups assigned to role groups assigned in Microsoft Purview portal. |
|
| Remote Event Receivers in SharePoint Online will be retiredCategory:SharePoint OnlineNummer:MC1411726Status:planForChange | [What and Why:]
Microsoft is retiring Remote Event Receivers (RERs) in SharePoint Online as part of the Azure ACS retirement and ongoing modernization of the SharePoint extensibility platform. Remote Event Receivers registered using Azure ACS stopped functioning correctly on April 2, 2026. Remote Event Receivers registered using Microsoft Entra applications will continue to function until July 1, 2027, after which all Remote Event Receivers will stop working. Microsoft recommends migrating affected solutions to SharePoint webhooks or Microsoft Graph change notifications.
[Rollout Schedule:]
- April 2, 2026: Azure ACS-registered Remote Event Receivers stopped functioning correctly.
- July 1, 2027: All remote event receivers, including those registered using a Microsoft Entra application, will stop working. No RER will fire events after this date.
[Impact on Your Organization:]
Who is affected:
- Organizations using SharePoint Online Remote Event Receivers.
- Developers, solution owners, and third-party vendors supporting SharePoint customizations.
Platforms/Services:
- SharePoint Online
- Microsoft Entra ID applications
- SharePoint Add-ins
- SharePoint webhooks
- Microsoft Graph change notifications
What will happen:
- Azure ACS-based Remote Event Receivers have already stopped functioning correctly.
- All remaining Remote Event Receivers will stop firing events after July 1, 2027.
- Applications and workflows that depend on Remote Event Receivers will no longer receive SharePoint event notifications.
- Business processes that rely on those events may stop working unless migrated.
- SharePoint webhooks and Microsoft Graph change notifications are the recommended replacement technologies.
- SharePoint webhooks are asynchronous. Solutions that depend on synchronously blocking or cancelling actions will need to be redesigned.
- There will not be an option to extend Remote Event Receivers beyond July 1, 2027.
- Microsoft currently does not provide a tenant-wide method for administrators to discover Remote Event Receiver usage. We will update this Message Center post, and the associated developer blog post, as soon as a discovery capability is available.
[Action Required / Recommendations:]
- Identify any in-house applications or solutions that use Remote Event Receivers.
- Work with developers to determine whether Remote Event Receivers are in use.
- Contact third-party vendors to determine whether their solutions rely on Remote Event Receivers.
- Request updated webhook-based versions of affected third-party solutions.
- Plan migration to SharePoint webhooks or Microsoft Graph change notifications before July 1, 2027.
- Review internal documentation and operational procedures that reference Remote Event Receivers.
- Communicate this retirement to application owners, developers, support teams, and help desk personnel.
- Monitor future Message Center updates for Microsoft’s planned Remote Event Receiver discovery capability.
- Review Overview of SharePoint webhooks.
- Review Microsoft Graph change notifications guidance.
- Review the Azure ACS retirement FAQ.
- Review guidance for using Remote Event Receivers without an Azure ACS dependency.
- Review the SharePoint team retirement update blog.
Learn more:
[Compliance Considerations:]
| Area |
Explanation |
| Does the change alter how existing customer data is processed, stored, or accessed? |
Organizations migrating from Remote Event Receivers to SharePoint webhooks or Microsoft Graph change notifications may need to redesign how SharePoint event data is retrieved and processed. |
| Does the change modify, interrupt, or disable capabilities? |
Remote Event Receivers are being retired. Applications, workflows, and integrations that depend on them will stop receiving SharePoint events after July 1, 2027 unless migrated. |
| Does the change alter how admins can monitor, report on, or demonstrate compliance activities? |
Microsoft currently does not provide a tenant-wide discovery capability for identifying Remote Event Receiver usage. Administrators must work with developers and solution vendors to assess exposure until a discovery capability becomes available. |
| Does the change add any integration to 3rd party software products? |
Organizations using third-party solutions built on Remote Event Receivers may require updated vendor versions that use supported technologies such as SharePoint webhooks or Microsoft Graph change notifications. |
|
| Copilot Notebooks: Suggested artifacts for faster content creationCategory:Microsoft 365 appsNummer:MC1411727Status:planForChange | [What and Why:]
Copilot Notebooks will intelligently recommend relevant artifacts based on your Microsoft 365 knowledge and the content in your notebook, helping you move work forward faster without leaving the notebook experience. By automatically leveraging existing context and background information, Copilot reduces the need to repeatedly write prompts containing the same details when creating new content from notebook materials. Supported artifact types include Word documents, Excel workbooks, and PowerPoint presentations. Support for additional artifact types, including PDFs and Pages, will be introduced in a future release. This message is associated with Roadmap ID 566870. [Rollout Schedule:]
- Public Preview (Worldwide): Beginning in early July 2026; expected to complete by late August 2026.
- General Availability (Worldwide): Beginning in late July 2026; expected to complete by late September 2026.
[Impact on Your Organization:]
Who is affected:
- Users who can currently create artifacts within Copilot Notebooks.
- Organizations licensed for Microsoft 365 Copilot (Premium) with access to Copilot Notebooks.
Platforms/Services:
- Microsoft 365 Copilot
- Copilot Notebooks
- Word
- Excel
- PowerPoint
What will happen:
- Users will see proactive artifact recommendations within Copilot Notebooks.
- Suggestions are generated using notebook references, pages, and Microsoft 365 context.
- Supported artifact types include Word, Excel, and PowerPoint.
- Future releases are expected to add support for PDFs and Pages.
- The feature is available by default for eligible users.
- No admin configuration is required.
[Action Required/Recommendations:]
No action is required. We recommend that you:
- Review user-facing communications regarding Copilot Notebooks.
- Inform help desk teams about the new recommendation experience.
- Update internal training and adoption materials as appropriate.
- Monitor roadmap communications for future artifact type support.
[Compliance Considerations:]
| Compliance consideration | Explanation |
|---|
| Does the change alter how existing customer data is processed, stored, or accessed? | Artifact suggestions are generated using content already available in Copilot Notebooks, including notebook references, pages, and the user’s Microsoft 365 context. This introduces additional AI-driven processing of existing customer data to determine relevant artifact recommendations. | | Does the change introduce or significantly modify AI/ML or agent capabilities that interact with or provide access to customer data? | The feature adds proactive AI-generated artifact recommendations that analyze notebook content and Microsoft 365 context to suggest next-step deliverables such as Word documents, Excel workbooks, and PowerPoint presentations. | | Does the change provide end users any new way of interacting with generative AI? | Users can receive contextual artifact recommendations directly within Copilot Notebooks and generate content from pre-populated prompts that incorporate relevant notebook information. | | Does the change alter how admins can monitor, report on, or demonstrate compliance activities? | The announcement does not specify whether recommendation activity will be surfaced in existing audit, reporting, or compliance experiences. Organizations may wish to review future documentation for additional compliance-related details. | | Does the change include an admin control and can it be controlled through Entra ID group membership? | No new administrative controls are described. The feature appears to be available to users who already have permission to create artifacts in Copilot Notebooks, but Microsoft has not explicitly documented control mechanisms. | | Does the change allow a user to enable and disable the feature themselves? | The announcement states that users remain in control of whether they use suggested artifacts, but it does not specify whether the recommendation experience itself can be enabled or disabled by individual users. |
|
| Sales in Microsoft 365 Copilot – Engage customers across multiple channels (web, voice, SMS & email)Category:Microsoft Copilot (Power Platform)Nummer:MC1412480Status:stayInformed | We are announcing the ability to engage customers across multiple channels (web, voice, SMS & email) in Sales in Microsoft 365 Copilot. This feature will reach general availability on August 3, 2026.
How does this affect me?
This feature provides a multi-channel outreach capability, spanning web chat, voice, SMS, and email, to meet customers in the channel they naturally prefer.
Key functionality of this feature includes:
- Configuration of multi-channel playbooks to reach customers across different channels to optimize response rates.
- Channel specific guidelines that can be established to ensure channel specific tone, brevity and best practices are adhered to.
- Channel level consent management.
- Automatic logging of channel interactions to CRM.
- Cross channel engagement context to ensure consistent customer experience across customer touchpoints.
What action do I need to take?
This message is for awareness, and no action is required. |
| Microsoft Dataverse – Service Update 9.2.26065.00000 for EURCategory:Microsoft DataverseNummer:MC1412483Status: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.26065.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. |
| Customize the Start menu with updated policiesCategory:WindowsNummer:MC1412655Status:stayInformed | What and why The updated Start menu is now rolling out to organizations using Windows 11. It brings the “All \[apps\]” section to the top level of the Start menu with new views (category and grid). The size of the Start menu is dynamic to the user’s device. Additionally, updated policies now make it easier for you to configure Start. Rollout schedule - Start menu began gradual rollout in October 2025 to general audiences.
- The rollout to organizations began in June 2026.
Impact on your organization Windows 11 devices began updating to show the new Start menu. In addition to the existing policies, the following policies give you more control: - HideCategoryView: This is a net new policy that you can apply to the updated Start menu design. Turn off the new category view in the “All \[apps\]” section, so devices show the grid view by default. Note: If you already have HideAppList enabled, you don’t need to enable HideCategoryView since devices won’t have the “All \[apps\]” section.
- ConfigureStartPins: You can apply this policy to all versions of Start. It only includes an update. When the optional applyOnce flag is set, the pinned layout is applied only during initial provisioning. After that, users can customize their Start menu without losing those changes during routine policy refreshes. This addresses a previous issue where users’ pinned sections could be unexpectedly refreshed.
Action required/recommendations Review the new policies and make changes accordingly:
Compliance considerations No compliance considerations are identified. Review as appropriate for your organization. |
| (Updated) InfoPath 2013 client and InfoPath Forms Services in SharePoint Online will reach end of support in July 2026Category:SharePoint OnlineNummer:MC616550Status:planForChange | Updated July 2, 2026: We are updating this post as a reminder. Thank you for your patience. Industry trends and feedback from our customers and partners make it clear that today’s businesses demand an intelligent, integrated forms experience that spans devices which InfoPath does not provide. As announced earlier, InfoPath Client 2013 will reach the end of its extended support period on July 14, 2026 (link), and to keep an aligned experience across Microsoft products, InfoPath Forms Service will be retired from SharePoint Online. We’re sending this message to bring it to your early attention to minimize the potential impact on your organization. [Key Points:] - Major: Retirement
- Timeline: After May 18, 2026: Publishing new InfoPath forms or publishing updates to existing forms will be blocked and from July 14, 2026, Microsoft will remove InfoPath Forms Services for existing tenants.
- Action: Review and assess impact
[How this will affect your organization:]
- After May 18, 2026, publishing new InfoPath forms or publishing updates to existing forms will be blocked. Existing published forms will remain available and usable till July 14, 2026
- After July 14, 2026, users will no longer be able to use InfoPath forms in SharePoint Online.
[What you need to do to prepare:]
To understand how InfoPath is used in your organization, you can run the Microsoft 365 Assessment tool to scan the tenant for InfoPath usage. Using the Power BI InfoPath Report generated by the scanner tool, you can: - Identify all InfoPath Forms usage in the tenant, per site collection and site.
- Evaluate the recency and volume of usage of InfoPath Forms.
- Understand lists, libraries and content types that use InfoPath.
We recommend communicating to the impacted site owners/teams inside your organization now, so they are aware of the coming change.
For scenarios where InfoPath or InfoPath Forms services are currently being used, we recommend migrating to Power Apps, Power Automate or Forms. Please ensure that you allow adequate time for migration of any use of InfoPath/InfoPath Forms Services in your organization ahead of this date, as there is no migration tool provided. Additional instructions on how to migrate can be found in this blog. Please plan appropriately as there will not be an option to extend InfoPath Form Services beyond the InfoPath retirement date of July 14, 2026. |
