Störungsverlauf von Lms365

1. 23. Oktober 2026 um 13:33 UTCresolved

   Veröffentlicht: 23. Oktober 2026 Status: gelöst Kundensicherheit: Learn365, Perform365 und Engage365 verwenden kein PHP und waren von diesen Sicherheitslücken nicht betroffen. Zensai hat Behebungsaktivitäten im Zusammenhang mit zwei offengelegten PHP-Schwachstellen (CVE-2026-109618 und CVE-2026-109619) abgeschlossen, die bestimmte nicht unterstützte PHP-Versionen betreffen, die in Teilen unserer öffentlichen Website-Infrastruktur verwendet werden. Die betroffenen Systeme beschränkten sich auf öffentlich zugängliche Marketing-Websites und die damit verbundene Web-Infrastruktur. Die betroffene Umgebung wurde auf unterstützte und gepatchte PHP-Releases aktualisiert und zusätzliche Validierungen durchgeführt, um Indikatoren für Kompromisse oder Sicherheitsprobleme zu identifizieren. Als Ergebnis: - Es waren keine Kundendaten betroffen. - Es kam zu keiner Unterbrechung des Kundendienstes. - Authentifizierungs- und Anwendungsdienste waren nicht betroffen. Learn365, Perform365 und Engage365 arbeiteten während des gesamten Sanierungsprozesses normal weiter. Feststellungen Unsere Untersuchung ergab: - Keine Beweise für Ausbeutung. Keine Beweise für unbefugten Zugriff. - Keine Hinweise auf bösartige Codeausführung. - Keine Beweise für Website-Manipulation. Keine Auswirkungen auf Kundenprodukte, Dienstleistungen oder Daten. Für alle Details wenden Sie sich bitte an das Trust Center Advisory: https://trustcenter.zensai.com/hc/en-us/articles/40117544567965-Security-advisory-PHP-vulnerabilities-affecting-public-website-infrastructure

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 29. September 2026 um 16:28 UTCidentified

   Wir haben das Problem mit dem Course Notifications Panel identifiziert. Einige Kursbenachrichtigungen können nicht auf Kursebene verwaltet werden.

2. 1. Oktober 2026 um 15:27 UTCmonitoring

   Ein Fix wurde bereitgestellt, um das Problem zu beheben, bei dem Kursbenachrichtigungsoptionen auf Kursebene fehlten. Wir überwachen die Ergebnisse, um sicherzustellen, dass das Problem vollständig gelöst ist.

3. 1. Oktober 2026 um 16:26 UTCresolved

   Der Fix wurde bereitgestellt und das Problem, bei dem Kursbenachrichtigungsoptionen auf Kursebene fehlten, ist nun behoben. Wenn Sie weitere Probleme bemerken, kontaktieren Sie bitte das Zensai Support-Team.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 4. September 2026 um 15:49 UTCidentified

   Wir haben derzeit ein Problem mit Kursabschlüssen, hauptsächlich in Bezug auf Kurse mit SCORM-Paketen, in denen das Paket / der Kurs abgeschlossen wird, aber der Kurs wird als In-Progress mit einem 100% Abschlussprozentsatz bleiben. Das Problem wurde identifiziert und ein Hotfix wird veröffentlicht.

2. 14. September 2026 um 21:46 UTCresolved

   Ein Fix wurde erfolgreich eingesetzt, um das Problem der SCORM-Kursabschlüsse zu beheben. Nach der Bereitstellung wurde das SCORM-Abschlussverhalten in seinen erwarteten Zustand wiederhergestellt, und die Kurse sollten nun den Abschlussstatus des Lernenden korrekt widerspiegeln, anstatt nach erfolgreichem Abschluss in Arbeit zu bleiben. Das Problem gilt als gelöst, und der Abschluss des SCORM-Kurses sollte nun in den betroffenen Umgebungen wie erwartet funktionieren.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 10. August 2026 um 11:23 UTCidentified

   Wir haben ein Problem identifiziert, das sich auf E-Mail-Benachrichtigungen für Kunden auswirkt, die die ältere Benachrichtigungskonfiguration Perform & Engage (Weekly10) verwenden. Unsere Untersuchung ergab, dass Amazon Web Services (AWS), die diese alte E-Mail-Infrastruktur unterstützen, ein Problem mit dem zugehörigen Konto gekennzeichnet und das Senden von E-Mails von diesem Dienst vorübergehend angehalten haben. Infolgedessen werden einige Benachrichtigungs-E-Mails, die über die Legacy-Konfiguration gesendet werden, möglicherweise nicht zugestellt. Kunden, die den Standard-Benachrichtigungssender ([email protected]) verwenden, sind nicht betroffen. Als Milderung migrieren wir proaktiv betroffene Organisationen von der Legacy-Konfiguration zum Standard-Benachrichtigungssender und benachrichtigen die betroffenen Administratoren über die Änderung der Absenderadresse. Unsere Teams arbeiten aktiv daran, diese Migrationen abzuschließen und weitere Auswirkungen zu minimieren. Wir werden bei Bedarf weitere Updates bereitstellen.

2. 11. August 2026 um 13:43 UTCresolved

   All affected customers have now been successfully migrated to Azure Communication Services and have been informed of the change. Email notification delivery has been restored for the impacted organizations, and no further action is required from customers. If you have any questions or experience any further issues, you can always create a support ticket through our Help Center.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 5. Juni 2026 um 14:19 UTCidentified

   We are currently experiencing an issue affecting learner progress management actions in Learn365. Some customers may be unable to clear learner progress, edit learner progress, or force a retake. These actions may keep loading without completing or return an error. Our engineering team has identified the issue as related to a recent migration and is actively working on a fix. We expect the fix to be available soon. We will provide further updates as soon as more information is available.

2. 5. Juni 2026 um 15:11 UTCresolved

   The fix has been deployed, and the affected functionality should now be working as expected. If you experience any unexpected behavior, please reach out to our Support team by submitting a ticket: https://helpcenter.zensai.com/hc/en-us/articles/14197648878237-How-to-contact-Zensai-Product-Support

3. 9. Juni 2026 um 16:13 UTCpostmortem

   ### **Root Cause and Analysis** During the Learn Service deployment, a database migration introduced a schema change that removed a database column still required by another platform component. As a result, the affected component was no longer fully compatible with the updated database schema, which caused learner progress management actions to fail or remain loading without completing. The issue was related to a deployment sequencing dependency between platform components. This dependency was not identified early enough during the release validation process. ### **Resolution** Once the root cause was identified, we applied a hotfix to restore the required database column. This restored compatibility between the affected platform components and resolved the issue affecting learner progress management actions. ### **Remediation Items** To reduce the risk of similar incidents in the future, we are implementing the following improvements: **Improved release dependency checks** We are strengthening release validation to ensure dependencies between platform components are identified and confirmed before deployment. **Updated database migration guidelines** We are formalizing additional safeguards for database schema changes, especially when removing database fields that may be used by multiple platform components. **Additional deployment review automation** We are introducing automated checks to help identify potentially risky database migration patterns before release. **Stronger release readiness validation** We are improving release readiness checks to ensure critical validation steps are completed before production deployment. We apologize for the disruption this caused and appreciate your patience while our teams investigated and resolved the issue.

1. 13. Mai 2026 um 11:02 UTCidentified

   We have identified the cause of an issue where course pages and course flyouts may fail to load in the new UI for customers whose subscription plan does not include the Skills service. Our team is currently working on a fix. In the meantime, the old UI is not affected and can be used as a temporary workaround. We will provide an update as soon as the fix is available.

2. 13. Mai 2026 um 11:04 UTCidentified

   We are continuing to work on a fix for this issue.

3. 13. Mai 2026 um 13:21 UTCidentified

   The fix has been deployed to production, and the issue should now be resolved. If you still experience any problems, please try clearing your browser cache and cookies or opening the page in an incognito/private browser window. If you have any further questions or continue to experience issues, please contact our Support team.

4. 13. Mai 2026 um 13:23 UTCresolved

   This incident has been resolved.

1. 1. April 2026 um 08:26 UTCresolved

   Between 05:30 and 07:30 CET, we experienced an issue in the Central US region affecting the Audit service. During this period, certain user profile synchronization events resulted in unexpected audit behavior. The issue has been identified and addressed, and the service is operating normally. We are reviewing additional safeguards to prevent similar occurrences in the future.

1. 16. März 2026 um 11:53 UTCidentified

   We have identified an issue where courses fail to load in the mobile application. This issue impacts all users attempting to access course content via the Learn365 Mobile application. Our engineering team is actively working on resolving issue. We will provide an update as soon as further progress is available.

2. 16. März 2026 um 11:53 UTCidentified

   We are continuing to work on a fix for this issue.

3. 16. März 2026 um 18:00 UTCmonitoring

   A fix has been successfully deployed to the production environment to address the issue causing courses not to load in the mobile application. We are currently monitoring the situation closely to ensure system stability and confirm that courses are loading as expected. Further updates will be shared if necessary.

4. 23. März 2026 um 10:55 UTCresolved

   This incident has been resolved.

1. 13. März 2026 um 14:03 UTCresolved

   Customers experienced a short‑term (12:37 - 13:46 UTC) service disruption in the US region, during which some Learn365 applications and admin pages were temporarily unavailable. The issue has been fully resolved, all services are now operating normally, and our team continues to closely monitor the system to ensure stability.

1. 23. Februar 2026 um 11:26 UTCinvestigating

   We are investigating an issue where some users see a "Your session has expired" message immediately after opening the Course Catalog webpart, even on first load or after refreshing the page. We will provide an update as soon as we have more information.

2. 26. Februar 2026 um 14:17 UTCmonitoring

   We’ve deployed a fix after identifying the root cause. We are monitoring results closely to ensure the service remains stable and the issue is fully resolved. If you continue to experience the problem, please contact our Support team by submitting a ticket: https://helpcenter.zensai.com/hc/en-us/articles/14197648878237-How-to-contact-Zensai-Product-Support

3. 9. März 2026 um 13:18 UTCresolved

   The issue has been addressed and the service is operating normally. Following the deployment of the fix, we have verified that the platform is functioning as expected. If you experience any unexpected behavior, please reach out to our Support team by submitting a ticket: https://helpcenter.zensai.com/hc/en-us/articles/14197648878237-How-to-contact-Zensai-Product-Support Thank you for your patience while we worked to resolve this matter.

1. 13. Februar 2026 um 12:21 UTCinvestigating

   We are currently investigating an issue affecting access to the Microsoft Teams apps for Learn365 and Perform & Engage. Some users may experience blank pages or apps not loading within Teams, including errors such as “There was a problem reaching this app”. Possible workaround: Users may be able to access the apps via Microsoft Teams in a web browser while the investigation is ongoing. Our findings indicate this issue is related to the Microsoft Teams platform. We have engaged Microsoft and are working with them separately to identify and resolve the root cause. We will provide further updates as soon as more information becomes available.

2. 16. Februar 2026 um 11:47 UTCinvestigating

   We have received an update from Microsoft Support. They have confirmed that this issue is part of a recent service spike impacting multiple users across the platform. Their Engineering team is actively investigating the root cause and working on implementing a fix. This spike is causing intermittent disruptions similar to those reported. Microsoft is currently reviewing telemetry and service activity to isolate the source of the issue and mitigate the impact. We will provide the next update once we receive further information from Microsoft.

3. 19. Februar 2026 um 16:27 UTCresolved

   Microsoft has confirmed that the issue was caused by a service degradation on their side. Their engineering team investigated the incident and implemented the necessary fixes to restore service stability. The service is now fully operational, and we are not observing any further impact. We sincerely apologize for any inconvenience this may have caused and appreciate your patience while the issue was being resolved. If you experience any related concerns, please don’t hesitate to contact our Support team: https://helpcenter.zensai.com/hc/en-us/articles/14197648878237-How-to-contact-Zensai-Product-Support

1. 19. Dezember 2025 um 19:02 UTCinvestigating

   We are currently investigating an issue with users not populating within Entra ID groups that have been added to Learn365.

2. 23. Dezember 2025 um 15:22 UTCmonitoring

   A fix has been implemented and we are monitoring the results

3. 23. Dezember 2025 um 17:10 UTCresolved

   After monitoring the effectiveness of the fix that was released we have seen a full recovery of functionality to users populating within Entra ID Groups.

1. 12. Dezember 2025 um 13:02 UTCresolved

   A customer recently reported two security-related issues affecting access controls and administrative permissions. Upon receiving the report, our team immediately investigated, validated the findings, and deployed fixes for both items. While there is no evidence of misuse, we have taken additional steps to strengthen our security posture, including initiating a new, independent penetration test to ensure comprehensive coverage. Details of Resolved Issues 1. Access control for storage links Certain file links were accessible without the expected security measures. This has now been addressed at the resource level, and an update is being deployed to ensure proper access requirements are enforced. 2. Permissions on admin functionality There was a scenario where users could elevate their permissions if they navigated to a specific page. This has been corrected to prevent unauthorised changes. If you have further questions or would like more details about the issue, please contact Zensai Support Team.

2. 23. Januar 2026 um 13:15 UTCpostmortem

   This report outlines two security-related issues that were identified, their root causes, and the actions taken to fully resolve them. We are sharing this transparently to maintain trust and ensure clarity on the steps taken to strengthen platform security. ## Issue 1: Unauthorized Access via Legacy APIs ### Summary Certain legacy API endpoints allowed unauthorized actions, including privilege escalation and access to restricted data. ### Root Cause Some older API endpoints were not aligned with current authentication and authorization standards. These endpoints were not included in recent security audits, automated scans, or penetration testing due to assumptions about their risk level and limited test scope coverage. This resulted in incomplete security validation across the full API surface. ### Actions Taken * Immediate remediation of all exposed endpoints * Full security scan of **1,700\+ API endpoints** using automated scripts and AI-based validation * Introduction of centralized endpoint security validation processes * Expansion of dynamic security scanning to include role-based scenarios * Scheduling of a new penetration test with expanded scope and guidance * Integration of security validation into development and QA workflows ## Issue 2: BLOB Storage URL Exposure ### Summary Storage URLs were publicly accessible and did not include expiration \(TTL\), creating potential unauthorized access risk. ### Root Cause During infrastructure migration from AWS to Azure, storage URL handling was reimplemented. The new implementation did not enforce TTL or access restrictions, and security validation for storage access was not formally reviewed as part of the migration process. ### Actions Taken * Immediate implementation of **TTL \(time-to-live\)** on all storage URLs * Full obfuscation of backend storage URLs * Enforcement of authenticated access for file retrieval * Updates to QA and development review processes * Formalization of security validation for infrastructure and storage changes ## Lessons Learned * Legacy systems must be continuously audited and cannot be excluded from security reviews * Security testing must cover the **entire platform surface**, not only core or new components * Infrastructure and architectural changes must trigger mandatory security validation * Penetration testing must be supported by internal processes, automation, and continuous scanning ## Commitment We have strengthened our internal security processes, expanded automated and manual validation coverage, and embedded security checks directly into development and QA workflows. These changes ensure higher resilience, stronger prevention, and earlier detection of potential risks going forward. Security and trust remain core priorities, and we are committed to continuous improvement and transparency.

1. 8. Dezember 2025 um 22:26 UTCinvestigating

   We are currently investigating an issue with User being enrolled to courses. At this time, individual Users and User Groups are having difficulty being enrolled to courses.

2. 9. Dezember 2025 um 00:38 UTCmonitoring

   Our development team has implemented a fix to address the enrollment issues, and we're now monitoring the system closely to ensure stability and full recovery. We appreciate your patience and will provide further updates as needed.

3. 9. Dezember 2025 um 21:09 UTCresolved

   The hotfix that was released has resolved the issue and we have observed enrollments completing. If you are observing lingering issues with enrollments after 630am UTC please reach out to our Support Team for additional assistance.

1. 12. November 2025 um 18:02 UTCinvestigating

   We are currently investigating an issue with Instructor Led Training sessions having difficulty loading in the Learn365 Admin Center.

2. 12. November 2025 um 18:17 UTCidentified

   The issue has been identified, and a fix is being created.

3. 14. November 2025 um 09:49 UTCresolved

   Our team has resolved the issue that was causing difficulty loading Instructor Led Training sessions in the Learn365 Admin Center. If you continue to experience issues, please reach out to the Zensai Support Team.

1. 29. Oktober 2025 um 16:11 UTCinvestigating

   We are currently aware of an issue with an Azure service outage. We are actively investigating the issue.

2. 29. Oktober 2025 um 16:26 UTCinvestigating

   We are continuing to investigate this issue.

3. 29. Oktober 2025 um 16:42 UTCidentified

   Starting at approximately 16:00 UTC, Microsoft reported DNS issues that are affecting access to the Azure Portal and potentially other services. Microsoft has initiated mitigation steps expected to restore portal access shortly and is actively investigating the root cause.

4. 29. Oktober 2025 um 17:17 UTCidentified

   Microsoft has reported the following: "We began experiencing Azure Front Door issues resulting in a loss of availability of some services. In addition, customers may experience issues accessing the Azure Portal." We are continuing to assess the situation.

5. 29. Oktober 2025 um 18:25 UTCidentified

   Current status from Microsoft: We have confirmed that an inadvertent configuration change as the trigger event for this issue. We have initiated the deployment of our 'last known good' configuration. This is expected to be fully deployed in about 30 minutes from which point customers will start to see initial signs of recovery. Once this is completed, the next stage is to start to recover nodes while we route traffic through these healthy nodes. Customer configuration changes will remain blocked during this time as we work towards mitigation. We will communicate to customers when this block is reverted.

6. 29. Oktober 2025 um 21:05 UTCmonitoring

   Current status from Microsoft: We initiated the deployment of our ‘last known good’ configuration, which has now successfully been completed. Customers may have begun to see initial signs of recovery. We are currently recovering nodes and routing traffic through healthy nodes, and as we make progress in this workstream, customers will continue to see improvement.

7. 29. Oktober 2025 um 21:26 UTCmonitoring

   Microsoft has identified the services affected by the outage: Affected Azure services include, but are not limited to: App Service, Azure Active Directory B2C, Azure Communication Services, Azure Databricks, Azure Healthcare APIs, Azure Maps, Azure Portal, Azure SQL Database, Container Registry, Media Services, Microsoft Defender External Attack Surface Management, Microsoft Entra ID, Microsoft Purview, Microsoft Sentinel, Video Indexer, and Virtual Desktop. Per Microsoft: As recovery progresses, some requests may still land on unhealthy nodes, resulting in intermittent failures or reduced availability until more nodes are fully restored. This recovery effort involves reloading configurations and rebalancing traffic across a large volume of nodes to restore full operational scale. The process is gradual by design, ensuring stability and preventing overload as dependent services recover. We expect continued improvement across affected regions. This means we expect recovery to happen by 23:20 UTC on 29 October 2025

8. 29. Oktober 2025 um 21:48 UTCmonitoring

   We are pleased to report that functionality is beginning to return across all regions. Access to all aspects of Learn365 and Perform & Engage 365 should now start to be restored for users. Please be aware that Microsoft is continuing efforts to fully resolve the issue, so you may still experience intermittent access or degraded performance during this time. We appreciate your patience and will provide further updates as the situation evolves.

9. 30. Oktober 2025 um 10:25 UTCresolved

   From Microsoft updates: An unintended configuration change in Azure Front Door (AFD) caused a global service disruption by introducing an invalid state that prevented numerous nodes from loading properly. This resulted in latency, timeouts, and uneven traffic distribution. The root cause was a deployment process flaw combined with a software defect that allowed the invalid configuration to bypass validation. Microsoft restored stability by rolling back to the last known good configuration and has since implemented additional safeguards to prevent recurrence. For more details, please refer to the Microsoft status page: https://azure.status.microsoft/en-us/status/history/ If you experience any other issues, please don’t hesitate to contact our technical support by submitting a ticket: https://helpcenter.zensai.com/hc/en-us/articles/360019112178-Get-help-from-the-Zensai-Product-Support-team

10. 30. Oktober 2025 um 19:59 UTCpostmortem

    On October 29, 2025, our platform experienced intermittent latencies, timeouts, and errors due to a widespread disruption in Azure Front Door \(AFD\), a critical component of Azure-based infrastructure. This affected our services reliant on AFD for global content delivery, impacting customer access and performance. As a consumer of Azure services, we were directly affected by this Microsoft-managed incident. Below is a summary of the root cause, resolution efforts, and planned remediation based on Microsoft's preliminary incident report \(PIR\). Root Cause Identification and Analysis The outage was triggered by an inadvertent tenant configuration change by Microsoft within Azure Front Door, which introduced an invalid or inconsistent configuration state. This caused a significant number of AFD nodes to fail to load properly, resulting in increased latencies, timeouts, and connection errors across dependent services, including our platform.  As unhealthy nodes were removed from the global pool, traffic became imbalanced, exacerbating the issue and leading to intermittent availability even in partially healthy regions. The root trigger was a faulty tenant configuration deployment process, where Microsoft's protection mechanisms—designed to validate and block erroneous deployments—failed due to a software defect. This allowed the invalid configuration to bypass safety checks and propagate globally. Our internal monitoring confirmed the impact aligned with Microsoft's timeline, starting around 15:45 UTC on October 29, with services like Azure App Service and Azure SQL Database \(which underpin our SaaS offerings\) experiencing degraded performance. Resolution Microsoft's response began shortly after the incident onset. Key steps included:  * At 16:04 UTC on October 29, investigation commenced following monitoring alerts. * By 16:15 UTC, teams examined recent configuration changes in AFD. * Initial communications were posted to the public status page at 16:18 UTC, with targeted notifications to impacted customers \(including us\) via Azure Service Health at 16:20 UTC. * To contain the issue, all new customer configuration changes to AFD were blocked at 17:30 UTC. * A "last known good" configuration was deployed starting at 17:40 UTC, with global pushes beginning at 18:30 UTC. * Manual node recovery and gradual traffic rebalancing to healthy nodes started at 18:45 UTC. * By 00:05 UTC on October 30, the impact was fully mitigated for most customers, though a small subset \(not affecting our platform\) experienced lingering issues. From our side, we monitored the situation via Azure Service Health alerts. Our platform returned to normal operation in line with Microsoft's recovery, with no residual issues reported by our users. Remediation Items As this incident originated from Microsoft's internal processes, there are limited direct actions we can take to prevent similar Azure-managed outages in the future. However, Microsoft has already implemented immediate safeguards, including a review of their protection mechanisms and the addition of enhanced validation and rollback controls to block faulty deployments.

1. 27. Oktober 2025 um 20:51 UTCinvestigating

   We are currently investigating an issue impacting access to Perform365 and Engage365. When attempting to load the applications, users are encountering a "504 The service behind this page isn't responding to Azure Front Door" gateway timeout error. Our engineering team is actively working to identify the root cause. We apologize for any inconvenience and will provide updates as more information becomes available.

2. 28. Oktober 2025 um 10:39 UTCresolved

   We would let you know that Perform & Engage 365 is now running smoothly. We’ve applied a fix to prevent the server from crashing, and the application is fully functional. The root cause was an inefficient query that failed to complete. To prevent similar issues, we’ve implemented a monitoring script that automatically terminates long-running queries, ensuring the database server remains stable. If you experience any issues, please don’t hesitate to contact our technical support by submitting a ticket: https://weekly10.zendesk.com/hc/en-us/articles/14012220303133-Submit-a-request-to-Zensai-Product-Su…

1. 14. Oktober 2025 um 09:13 UTCinvestigating

   We are currently investigating reports of a disruption affecting the loading of the Learn365 Webparts. Our engineering team is actively working to identify the root cause and restore full functionality as quickly as possible. We will provide updates as soon as more information becomes available.

2. 14. Oktober 2025 um 09:25 UTCinvestigating

   We are continuing to investigate this issue.

3. 14. Oktober 2025 um 12:20 UTCmonitoring

   A fix has been successfully deployed to address the issue affecting the loading of the Learn365 Webparts. We are continuing to monitor system performance closely to ensure stability. We’ll provide a final update once we confirm the issue is fully resolved. Thank you for your patience during this time.

4. 15. Oktober 2025 um 13:17 UTCresolved

   The issue has been resolved. The incident was linked to a recent SharePoint Online update, changes in MSAL (Microsoft Authentication Library), and a few unexpected edge cases that impacted service stability. Our engineering team has deployed a fix and confirmed that all affected services are now operating normally. We will continue to monitor for any residual impact, but no further disruptions are expected at this time. Thank you for your patience and understanding throughout the investigation.

1. 10. Oktober 2025 um 11:01 UTCinvestigating

   We are aware of the issue affecting the creation of sessions ('Oops, something went wrong' error) in certain regions and are actively investigating the matter to resolve it as quickly as possible. In the meantime, if you are experiencing this problem, we recommend using the following workaround: you can create a Teams meeting and paste the meeting link into the session settings to ensure your sessions are created successfully. Thank you for your patience and understanding as we work to address this issue.

2. 30. Oktober 2025 um 08:37 UTCinvestigating

   We are continuing to investigate this issue.

3. 24. November 2025 um 19:53 UTCresolved

   This incident has been resolved.

4. 2. Dezember 2025 um 11:33 UTCpostmortem

   # **Session Creation Disruption in Select Regions** **Summary** Customers in select regions were unable to create sessions due to an unexpected issue related to Microsoft 365 licensing changes. When attempting to create a session, the system produced an error “Oops, something went wrong”, preventing the generation of a Teams meeting link. ‌ **Root Cause** Microsoft recently modified the licensing structure for certain Microsoft 365 accounts: [https://www.microsoft.com/en-us/licensing/news/Microsoft365-Teams-2025](https://www.microsoft.com/en-us/licensing/news/Microsoft365-Teams-2025) Previously, **Exchange Online Plan 1** often included **Teams** by default as part of a bundled suite. For many customers, session creation continued to work because their accounts already had an active Teams license. However, for affected customers, the Teams component was no longer included automatically. As a result, our platform was **unable to generate a Teams meeting link** during session creation. ‌ **Additional Note on Email App Settings** Microsoft confirmed that the following email app permissions are sufficient for proper access to users’ mailboxes and calendars: * Outlook on the Web * Exchange Web Services \(EWS\) * MAPI \(Outlook Desktop\) ‌ **Resolution** To restore full functionality and successfully create a session with a Teams meeting link, сustomers affected by the change need to ensure that both of the following licenses are assigned: 1. **Exchange Online Plan 1** 2. **Microsoft Teams license** In Learn365, reconnecting the account through **Notification Settings** is recommended to refresh permissions and ensure stability. Once the appropriate actions are applied, session creation and automatic Teams meeting generation resume working as expected. ‌ If you have any questions or are still experiencing issues, please reach out to us by opening a support ticket: [https://helpcenter.zensai.com/hc/en-us/articles/14197648878237-How-to-contact-Zensai-Product-Support#h\_01HBZEW0Z0FGSEJ6Z8VNKTFGK0](https://helpcenter.zensai.com/hc/en-us/articles/14197648878237-How-to-contact-Zensai-Product-Support#h_01HBZEW0Z0FGSEJ6Z8VNKTFGK0) We will be happy to assist you.

1. 9. Oktober 2025 um 10:19 UTCidentified

   We are currently experiencing issues with Perform&Engage 365 access as a result of the ongoing Azure Front Door outage reported by Microsoft (https://azure.status.microsoft/en-us/status). Some users may encounter degraded performance or difficulties loading pages. We are closely monitoring the situation and will provide updates as soon as more information becomes available. Thank you for your patience and understanding.

2. 9. Oktober 2025 um 12:38 UTCidentified

   Compliance Service is also affected by the Azure Front Door issue. Document conversion and deployment may be delayed while the Microsoft services are degraded.

3. 9. Oktober 2025 um 14:07 UTCmonitoring

   As per Microsoft, https://azure.status.microsoft/en-gb/status Current Status: Azure customers using Azure Front Door (AFD) should see consistent availability with slightly higher latencies decreasing as we continue to recover additional resources.

4. 9. Oktober 2025 um 18:03 UTCresolved

   We are pleased to inform you that the issue impacting access to Perform&Engage 365 and the Compliance Service due to the Azure Front Door outage has been fully resolved. This aligns with Microsoft's confirmation that the underlying outage has been mitigated, with all affected services recovering completely. Our monitoring confirms that Perform&Engage 365 and the Compliance Service are now operating normally, with no further disruptions observed. We sincerely apologize for any inconvenience this may have caused to your daily operations and appreciate your patience during this time. If you encounter any lingering issues, please reach out to our support team.