Admins can't identify who deleted a Viva Engage community or its Microsoft 365 Group in Microsoft Entra ID audit logs

Title: Admins can't identify who deleted a Viva Engage community or its Microsoft 365 Group in Microsoft Entra ID audit logs User impact: Admins can't identify who deleted a Viva Engage community or its Microsoft 365 Group in Entra ID audit logs. More info: Impact applies to deletions initiated from both the Viva Engage web experience and the Viva Engage app in Microsoft Teams. Admins needing to identify who deleted a specific community or group during the affected period should open a Microsoft support case with the deletion date and group/community details so support can trace the initiating user through service-side logs. Current status: We're deploying the first of three changes which we need to make for to ensure a comprehensive long-term solution. Due to the complexity of these changes, we currently anticipate remediation by Friday, January 30, 2027. We're continuing to monitor the progress of our deployment to identify any opportunities to expedite the process. Scope of impact: This issue is preventing all admins from identifying who deleted Viva Engage communities or their connected Microsoft 365 Group in Microsoft Entra ID audit logs. This information may be updated as our investigation continues. Start time: Friday, July 10, 2026, at 2:05 PM UTC Estimated time to resolve: We estimate that our three-phase improvement will be complete by January 30, 2027. Root cause: A recent update to improve group deletions of Viva Engage communities within Microsoft Teams is resulting in impact. Next update by: Friday, October 30, 2026, at 11:00 PM UTC

Title: Admins can't identify who deleted a Viva Engage community or its Microsoft 365 Group in Microsoft Entra ID audit logs User impact: Admins can't identify who deleted a Viva Engage community or its Microsoft 365 Group in Entra ID audit logs. More info: Impact applies to deletions initiated from both the Viva Engage web experience and the Viva Engage app in Microsoft Teams. Admins needing to identify who deleted a specific community or group during the affected period should open a Microsoft support case with the deletion date and group/community details so support can trace the initiating user through service-side logs. Current status: We're progressing with our additional levels of validations so we can ensure that our solution returns admins ability to determine who deleted Viva Engage communities or its Microsoft 365 Group in Entra ID audit logs. We'll provide an updated timeline for the deployment of our fix and the remediation of the impact once our pre-deployment tests have concluded. Scope of impact: This issue is preventing all admins from identifying who deleted Viva Engage communities or their connected Microsoft 365 Group in Microsoft Entra ID audit logs. This information may be updated as our investigation continues. Start time: Friday, July 10, 2026, at 2:05 PM UTC Root cause: A recent update to improve group deletions of Viva Engage communities within Microsoft Teams is resulting in impact. Next update by: Thursday, October 1, 2026, at 11:00 PM UTC

Title: Admins can't identify who deleted a Viva Engage community or its Microsoft 365 Group in Microsoft Entra ID audit logs User impact: Admins can't identify who deleted a Viva Engage community or its Microsoft 365 Group in Entra ID audit logs. More info: Impact applies to deletions initiated from both the Viva Engage web experience and the Viva Engage app in Microsoft Teams. Admins needing to identify who deleted a specific community or group during the affected period should open a Microsoft support case with the deletion date and group/community details so support can trace the initiating user through service-side logs. Current status: We've determined that resolving this issue requires additional validation to ensure that our fix addresses the impact without introducing unintended effects to the service. We're continuing testing and validation efforts and will provide an updated deployment timeline once those activities are completed. Scope of impact: This issue is preventing all admins from identifying who deleted Viva Engage communities or their connected Microsoft 365 Group in Microsoft Entra ID audit logs. This information may be updated as our investigation continues. Root cause: A recent update to improve group deletions of Viva Engage communities within Microsoft Teams is resulting in impact. Next update by: Wednesday, September 16, 2026, at 11:00 PM UTC

Title: Admins can't identify who deleted a Viva Engage community or its Microsoft 365 Group in Microsoft Entra ID audit logs User impact: Admins can't identify who deleted a Viva Engage community or its Microsoft 365 Group in Entra ID audit logs. More info: Impact applies to deletions initiated from both the Viva Engage web experience and the Viva Engage app in Microsoft Teams. Admins needing to identify who deleted a specific community or group during the affected period should open a Microsoft support case with the deletion date and group/community details so support can trace the initiating user through service-side logs. Current status: We've identified an update to our Viva Engage communities that’s preventing admins from identifying users who deleted a Viva Engage community or its connected Microsoft 365 Group in Microsoft Entra ID audit logs. We've developed and are internally validating a fix to remediate the impact. We'll provide an updated timeline for the deployment of our solution and the remediation of the impact once it has become available. Scope of impact: This issue is preventing all admins from identifying who deleted Viva Engage communities or their connected Microsoft 365 Group in Microsoft Entra ID audit logs. Root cause: A recent update to improve group deletions of Viva Engage communities within Microsoft Teams is resulting in impact. Next update by: Wednesday, September 2, 2026, at 11:00 PM UTC