HANDS ON SharePoint
HANDS ON Teams
HANDS ON Lists
HANDS ON tek
M365 Admin
Issue Awareness: Temporary impact to some Microsoft Loop policy configurations
We’re notifying your organization of a recent issue that resulted in impact to Microsoft Loop functionality and may have impacted your organization. Specifically, some policy configurations were not being honored as expected for users, which allowed the below behavior to occur.
The affected features as follows:
1. Users could have created workspaces within Loop which should have otherwise been disabled.
2. Users could have accessed the “Edit in pages” function within Copilot after performing a search or other function request.
The impacted timeframe this could have occurred between was October 10, 2024, and October 14, 2024. We do not collect telemetry which would confirm if you had users who performed the noted actions as outlined above during the impact timeframe. However, we have identified that you have the associated policies disabled in your tenant and therefore may have had users perform these unexpected actions during the impact timeframe. As such, we are notifying your organization as part of our commitment to privacy and transparency and want to make you aware of the potential for impact and the actions we’ve taken to address the issue.
What actions can I take?
Loop workspaces created in this timeframe that may have otherwise not been allowed in your organization can be discovered using SharePoint Admin tools. More information on finding Loop workspaces, which are SharePoint Embedded containers, can be found here: SharePoint Admin Center, SharePoint PowerShell.
Loop Application ID: a187e399-0c36-4b98-8f04-1edc167a0996
Loop Mobile Application ID: 0922ef46-e1b9-4f7e-9134-9ad00547eb41
Why am I just receiving this message?
Why was Microsoft Loop affected?
The SharePoint Admin tools have the ability to identify creators, creation times, owners, size, as well as other properties of SharePoint Embedded containers. More information on managing Loop workspaces can be found here: Summary of governance, lifecycle, and compliance capabilities for Loop experiences | Microsoft Learn.
Loop components created in this timeframe that may have otherwise not been allowed in your organization can be discovered using SharePoint Audit Logs. More information on what to search for can be found here.
The underlying issue was communicated in the Service Health Dashboard (SHD) under MO907640 due to service impact to Exchange Online. However, it has since been determined that additional downstream services were also affected. Additional information related to Copilot can be found in the SHD under CP908784 for applicable organizations.
Many services utilize CPS for policy configuration and implementation; however, it was determined that when one of the Microsoft Loop APIs was called to retrieve policy configuration and failed due to the CPS issue, some features defaulted to ‘enabled.’ This was determined to be a design issue and has since been updated to default to ‘disabled’ for similar scenarios.
What caused the CPS issue and what actions are being taken to prevent future issues?
Please see the SHD post for MO907654. A Post Incident Report was also published that outlines multiple action items.
Message ID: MC927758
