Störungsverlauf von Bittitan

1. 21. Oktober 2026 um 21:31 UTCresolved

   Am 21. Oktober 2026 gaben die NSA und das FBI Leitlinien zu zwei kritischen Schwachstellen in PHP heraus (CVE-2026-109618 und CVE-2026-109619), die die Ausführung von Remotecode ermöglichen könnten. Wir haben unsere Systeme auf Exposition überprüft. Die MigrationWiz-Plattform verwendet kein PHP und ist nicht betroffen. Unsere Marketing-Website verwendet PHP und wir haben die notwendigen Patches angewendet. Wir haben bestätigt, dass die Verwundbarkeit behoben wurde. Wir haben abschließend festgestellt, dass es keine Auswirkungen auf Kundendaten oder Serviceverfügbarkeit gab. Von den Kunden sind keine Maßnahmen erforderlich. Migrationen, Postfächer und Kontozugriff sind nicht betroffen.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 14. Oktober 2026 um 14:04 UTCinvestigating

   Wir untersuchen derzeit ein problem, das teams private chat-migrationen betrifft. Bei der Überprüfung der Anmeldeinformationen wird möglicherweise ein Fehler angezeigt, der darauf hinweist, dass der Benutzer auf dem Source-Mandanten nicht gefunden wurde. Dieses problem ist auf teams private chat-migrationen beschränkt. Andere Migrationsarten sind nicht betroffen. Unser Team ist sich des Problems bewusst und untersucht aktiv. Wir werden ein Update bereitstellen, sobald wir weitere Informationen haben.

2. 14. Oktober 2026 um 15:19 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 23. September 2026 um 16:01 UTCinvestigating

   Wir untersuchen ein Problem, das sich auf Stellenzuweisungen an unsere Infrastruktur auswirkt, was zu verlängerten Wartezeiten für Jobs im eingereichten Zustand führt. Unser Engineering-Team arbeitet aktiv daran, die Ursache zu identifizieren und zu beheben. Erforderliche Aktion: Wenn Ihre Jobs länger als 1 Stunde im Status Eingereicht gewartet haben, stoppen Sie bitte die betroffenen Projektlinien und reichen Sie sie erneut ein. Wir werden Updates bereitstellen, während unsere Untersuchung fortschreitet, und uns für die Störung entschuldigen.

2. 24. September 2026 um 02:48 UTCresolved

   Das Problem, das sich auf die Stellenbesetzung unserer Infrastruktur auswirkt, wurde gelöst. Jobs werden normal verarbeitet, und die Wartezeiten im Zustand Eingereicht sind auf das erwartete Niveau zurückgekehrt. Wenn Sie Projektlinien gemäß unserer früheren Anleitung gestoppt und erneut eingereicht haben und immer noch Verzögerungen feststellen, wenden Sie sich bitte an den Support.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 3. September 2026 um 13:58 UTCinvestigating

   MigrationWiz Dokument Migrationsfehler Nach einem Systemupgrade am 19. August 2026, das die Migrationsgeschwindigkeit und den Durchsatz von Dokumenten insgesamt verbesserte, haben wir ein Problem identifiziert, das eine kleine Teilmenge von Kunden betrifft. Einige Benutzer können bei der Migration von Dokumenten auf einen der folgenden Fehler stoßen: "Sammlung wurde geändert; Aufzählungsoperation kann nicht ausgeführt werden." "Offset und Länge waren außerhalb der Grenzen" "Haben Sie nicht alle Bytes aus der Datei gelesen." Diese Fehler sind kein Hinweis auf Datenverlust. Sie sind das Ergebnis eines DLL-Upgrades, das in der Version vom 19. August enthalten ist, wodurch Logs, die vor dem Upgrade generiert wurden, durch den aktualisierten Code nicht lesbar sind. Wir sind uns des Problems bewusst und arbeiten aktiv an einer umfassenderen Lösung. Empfohlene Schritte Wenn einer der oben genannten Fehler auftritt, führen Sie bitte ein Reset-Element durch und reichen Sie den Migrationspass erneut ein. Dies löst das Problem in den meisten Fällen. Anweisungen finden Sie unter Zurücksetzen von Elementen in MigrationWiz. https://help.bittitan.com/hc/en-us/articles/360042167494-MigrationWiz-Statistics-Statistics-Lookup#01H8HEMGW00PCG8XHWPM7QHWJD Wenn der Fehler nach der Durchführung eines Reset-Elements weiterhin besteht, öffnen Sie bitte einen Supportfall, damit unser Team Sie direkt unterstützen kann, während wir an einem breiteren Fix arbeiten. Wir werden hier Updates zur Verfügung stellen, wenn unsere Untersuchung fortgesetzt wird.

2. 8. September 2026 um 15:01 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 8. Juli 2026 um 14:43 UTCinvestigating

   We are currently investigating an issue affecting OneDrive to OneDrive migrations that use Delegate Application authentication. Customers may encounter the error message "Your migration failed while checking destination credentials" when attempting to run migrations under this configuration. Our engineering team is actively investigating the root cause. No action is required on your part at this time. We will provide updates as our investigation progresses. We apologize for any inconvenience this may cause.

2. 8. Juli 2026 um 15:42 UTCinvestigating

   The root cause has been determined, and we are working to release a change to address this error shortly.

3. 8. Juli 2026 um 18:04 UTCresolved

   We have resolved the issue affecting OneDrive to OneDrive migrations using Delegate Application authentication. Customers who previously encountered the error message "Your migration failed while checking destination credentials" should now be able to run migrations successfully. If you continue to experience issues, please resubmit your migration. If problems persist, contact our support team. We apologize for any inconvenience this may have caused.

1. 25. Februar 2026 um 17:10 UTCinvestigating

   We are currently experiencing an issue with our online cart system for US Address Customers that may cause online orders to fail at checkout. Our team is actively investigating and working to resolve the problem as quickly as possible.

2. 25. Februar 2026 um 21:31 UTCresolved

   This incident is resolved.

1. 23. Februar 2026 um 22:11 UTCinvestigating

   We are currently experiencing an issue with our online cart system that may cause online orders to fail at checkout. Our team is actively investigating and working to resolve the problem as quickly as possible.

2. 24. Februar 2026 um 13:40 UTCresolved

   This incident has been resolved.

1. 13. Februar 2026 um 21:09 UTCidentified

   We have upgraded our Microsoft 365 authentication to Microsoft’s modern identity platform (v2) to improve security, reliability, and configuration experience. Known Issues: OneDrive Migrations (Delegate App) Customers using the Advanced Option ForceOneDriveNonGlobalAdminAuthExport=1 may experience credential failures. This option remains functional for SharePoint-to-SharePoint migrations. Recommendation: Remove this advanced option if possible and assign the SharePoint Administrator role to the Delegate account. This issue is under investigation. Tenant-to-Tenant Coexistence (Free/Busy Setup) Organizational relationship creation is currently failing for coexistence projects. Workaround: If free/busy is not required, create a standard mailbox project without coexistence. We are actively investigating and will provide updates as available.

2. 29. April 2026 um 13:27 UTCresolved

   This incident is now resolved.

1. 8. Januar 2026 um 20:33 UTCinvestigating

   Late next week, we will begin rolling out a security-enhancing update to our authorization flow. As part of this update, a small set of workloads require user action to continue running successfully. OneDrive, SharePoint and Teams Collaboration endpoints using delegated permissions will need the Tenant ID added in the Endpoint Settings page and PKCE consent completed. BYO app registrations will no longer function and must be switched to the BitTitan app. For full instructions and details, please refer to the guidance pages below: Required Actions & Resolution Guide [https://help.bittitan.com/hc/en-us/articles/43575952076827-Post-Deployment-Action-Items] Endpoint Settings Guide [https://help.bittitan.com/hc/en-us/articles/42628192621211-Endpoints-Setting-Guide] Consent Flow Guide [https://help.bittitan.com/hc/en-us/articles/42629928893851-Project-Summary] This notice is informational to ensure customers can complete the necessary updates.

2. 14. Januar 2026 um 16:30 UTCinvestigating

   The rollout is now expected to begin in the early part of the next week. No additional customer action is required beyond what was previously communicated. Private Chat History (PCH) will not be supported following this deployment as part of an ongoing re-implementation initiative. This work is intended to deliver an improved PCH experience, and PCH support will be reintroduced in a planned upcoming release.

3. 20. Januar 2026 um 05:35 UTCidentified

   We’ve upgraded our Microsoft 365 authentication experience to adopt Microsoft’s modern identity platform (v2), bringing stronger security, improved reliability, and a smoother configuration experience. What’s New • A modern PKCE-based authentication flow • Enhanced security with Azure Key Vault • Support for Microsoft’s latest identity platform (OAuth2) • Simple, UI-based permission selection • A guided in-UI consent experience for faster setup • Better compatibility with MFA-enabled tenants Action Required: Some customers may need to re-authenticate depending on their configuration. Required Actions & Resolution Guide [https://help.bittitan.com/hc/en-us/articles/43575952076827-Post-Deployment-Action-Items] Endpoint Settings Guide [https://help.bittitan.com/hc/en-us/articles/42628192621211-Endpoints-Setting-Guide] Project Summary - Consent Flow Guide [https://help.bittitan.com/hc/en-us/articles/42629928893851-Project-Summary]

4. 21. Januar 2026 um 01:44 UTCidentified

   Update: Resolved Issues, Known Issues & Workarounds Following the recent deployment, we have identified a small number of edge-case scenarios that may affect specific configurations. Most have simple workarounds, and our teams are actively addressing these issues. Resolved Issues : The following issues identified after deployment have been resolved: 1. SSO sign-in for SSO-enabled domains An issue that prevented users from logging in using SSO-enabled domains has been resolved. 2.SharePoint auto-discovery SharePoint site auto-discovery is now functioning as expected. We are actively working to address these scenarios and will provide updates as improvements are rolled out. If you experience issues outside of the cases described above, please contact Support for assistance. Known Issues : M365 Mailbox Issue: Scoping Some customers, who are using scoping functionality, are receiving the error: “Your migration failed while checking source credentials. Validate Token failed, please check EWS Application Permissions in Azure App.” This is currently under investigation. Recommendation: If possible, run your project without using scoping. The migration should complete successfully. Delegated Consent may return a 500 error : In some cases, attempting delegated consent may result in an internal server error. Workaround: Edit the project, save it without making changes, and then retry the consent flow. This resolves the issue in most cases. Consent may reference a previously configured tenant after changing endpoints : If a project’s source or destination endpoint is edited to point to a different tenant, the consent flow may still attempt to authorize the previously configured tenant. Workaround: If the project has not been started, create a new project using the updated tenant details. Consent banner may not appear for specific Google → Microsoft 365 (v3) document migration scenarios In certain edge cases, the consent-required banner may not display even when consent has not yet been provided. Recommendation: Review the Project Summary page and confirm that the consent status shows Authorized / Consented before starting the migration Consent banner may not refresh after editing project endpoints When editing a project and changing tenant or permission settings, the consent banner may not immediately reappear. Recommendation: Verify the consent status from the Project Summary page to ensure authorization is complete.

5. 26. Januar 2026 um 13:31 UTCidentified

   Update : Our teams continue to actively investigate and address the remaining items identified after deployment. Below are the latest updates and recommendations. M365 Mailbox Issue: Scoping Some customers using scoping functionality may encounter the error: “Your migration failed while checking source credentials. Validate Token failed, please check EWS Application Permissions in Azure App.” This remains under investigation. Recommendation: If possible, run your project without using scoping. The migration should complete successfully. If scoping is required and the above recommendation does not resolve the issue, ensure the source application includes the additional permission Exchange.ManageAsApp, and follow the steps outlined in below document. Document Link: [M365 Mailbox and Archive Migrations - Scoping Option for API Permissions](https://help.bittitan.com/hc/en-us/articles/27712633347099-M365-Mailbox-and-Archive-Migrations-Scoping-Option-for-API-Permissions#h_01J3NXCYXSE6V647FTHKRPR2KX) ----- Tenant-to-Tenant (T2T) Coexistence – Organizational Relationship Creation Tenant-to-Tenant coexistence projects are currently unable to complete the required cross-organizational free/busy setup process. Workaround: If free/busy availability between tenants is not required (typically only needed for large, long-running coexistence projects), we recommend creating a standard MigrationWiz mailbox project without coexistence while we work to resolve this issue. ----- We appreciate your patience and continued cooperation as we work to fully resolve these items. Additional updates will be shared as progress is made.

6. 26. Januar 2026 um 19:29 UTCidentified

   We are continuing to work on a fix for this issue

7. 30. Januar 2026 um 03:06 UTCidentified

   Update : We have upgraded our document migration authentication to modern authentication standards for SharePoint, Teams, and OneDrive. This enhancement strengthens security, improves reliability, and aligns our migration platform with current Microsoft 365 identity best practices. As part of this upgrade, legacy authentication mechanisms such as SharePoint IDCRL are no longer used. Customer Impact: Migration projects using delegated permissions (SharePoint, Teams, or OneDrive) will fail until permissions are re-consented. To continue, customers must re-consent the delegated permissions and then re-run the migration. For more information, please review our release note. We remain committed to continuously improving the security, reliability, and quality of our migration platform. If you have any questions, please feel free to reach out to our Support team.

8. 13. Februar 2026 um 21:08 UTCresolved

   With the release of our Microsoft modern identity platform (v2) upgrade, designed to enhance security, reliability, and the overall configuration experience, the majority of the initial issues identified following launch have now been resolved.

1. 8. Dezember 2025 um 17:49 UTCmonitoring

   Migration jobs continue to process, but stopping them from the MigrationWiz UI is working inconsistently. Please contact Support if you require any migration lines to be stopped. Monitoring We have implemented a change and are seeing previously stalled migrations being processed. We are continuing to monitor the situation. Dec 07, 2025 - 10:12 PST Investigating Some customers may experience migrations stuck in the submitted state. We are aware of this issue and are working to resolve it. Dec 07, 2025 - 06:34 PST

2. 9. Dezember 2025 um 22:03 UTCresolved

   This incident has been resolved.

1. 8. Dezember 2025 um 17:47 UTCresolved

   Migration jobs continue to process, but stopping them from the MigrationWiz UI is working inconsistently. Please contact Support if you require any migration lines to be stopped

1. 7. Dezember 2025 um 14:34 UTCinvestigating

   Some customers may experience migrations stuck in the submitted state. We are aware of this issue and are working to resolve it.

2. 7. Dezember 2025 um 18:12 UTCmonitoring

   We have implemented a change and are seeing previously stalled migrations being processed. We are continuing to monitor the situation.

3. 8. Dezember 2025 um 17:41 UTCresolved

   Migration jobs continue to process, but stopping them from the MigrationWiz UI is working inconsistently. Please contact Support if you require any migration lines to be stopped.

1. 5. Dezember 2025 um 17:53 UTCmonitoring

   While the earlier issues have been resolved, customers who reset their password today will need to reset it again. For customers who did not update their password today, their previous password should now work.

2. 8. Dezember 2025 um 17:42 UTCresolved

   This incident has been resolved.

1. 5. Dezember 2025 um 14:26 UTCidentified

   MigrationWiz is currently experiencing a login issue. This is not a security incident. Users encountering the issue and receiving an “Access Denied” error should reset their password, which will restore access. We are investigating the cause and will provide an update soon.

2. 5. Dezember 2025 um 15:23 UTCidentified

   MigrationWiz is currently experiencing a login issue. This is not a security incident. Users encountering the issue and receiving an “Access Denied” error should reset their password, which will restore access. Additionally, some users may experience issues with license application and other related functions. We are investigating the cause and will provide an update soon.

3. 5. Dezember 2025 um 15:30 UTCidentified

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

4. 5. Dezember 2025 um 16:33 UTCresolved

   All previously identified issues have been resolved.

1. 28. Mai 2025 um 00:15 UTCinvestigating

   We are currently investigating an issue affecting document migrations involving Google Drive, OneDrive, and SharePoint. Customers may experience intermittent authentication or connectivity errors when running migrations in these areas. As a temporary workaround, re-running the affected migration items typically resolves the issue. Our engineering team is actively working toward a permanent resolution. We appreciate your patience and will provide additional updates as soon as they become available.

2. 2. Juli 2025 um 12:03 UTCmonitoring

   We have implemented a series of platform enhancements to improve authentication reliability and connections for document migrations across OneDrive, SharePoint, and Google Drive. These updates have strengthened the way secure connections are established and managed, resulting in more consistent credential validation and reduced authentication-related disruptions. In addition to improved reliability, we have also made optimizations to enhance data transfer speed and throughput. These changes help migrations complete faster and more efficiently, particularly for large volumes of data or high-concurrency migration scenarios. As of our most recent deployment on June 30, we are are seeing very promising results We will continue to monitor the platform to ensure stable performance and a seamless migration experience for all users.

3. 9. Juli 2025 um 21:08 UTCresolved

   We have confirmed through comprehensive testing and positive customer feedback that our recent platform enhancements have successfully resolved the reported performance issues affecting authentication reliability and connection stability during document migrations. If you continue experiencing any challenges related to authentication or connection reliability while using MigrationWiz, please reach out directly to our Support team for assistance. Thank you for your patience as we worked to address this matter.

1. 17. April 2025 um 19:49 UTCinvestigating

   We are currently investigating migrations that are failing with the error: “The method or operation is not implemented.” in some Microsoft Teams and Sharepoint migrations. Our engineering team is actively working to identify the root cause and implement a resolution. We will update this status again no later than Tuesday, April 22.

2. 21. April 2025 um 15:14 UTCidentified

   We are aware that some migrations are failing with the error: “The method or operation is not implemented.” in some Microsoft Teams and SharePoint migrations. Our engineering team has identified a solution and is actively working on developing the fix. We are targeting deployment by Friday, May 2, and will continue to provide updates as progress is made.

3. 30. April 2025 um 18:24 UTCresolved

   We’re pleased to confirm that the issue causing migration failures with the error “The method or operation is not implemented” has been fully resolved. We apologize for any inconvenience this may have caused, and appreciate your patience as we worked to implement a fix

1. 17. April 2025 um 15:49 UTCidentified

   As of March 31, 2025, Microsoft has ended support for app-only authentication in the OneNote API. To maintain functionality, users must switch to delegated authentication. This is a Microsoft platform change, and MigrationWiz cannot mitigate this. Microsoft’s Official Announcement(https://learn.microsoft.com/en-us/graph/api/resources/onenote-api-overview?view=graph-rest-1.0) Using Delegated Permissions for OneDrive, SharePoint, and Teams migrations(https://help.bittitan.com/hc/en-us/articles/360038153373-Using-Delegated-Permissions-for-OneDrive-SharePoint-and-Teams-migrations)

2. 2. Juli 2025 um 12:05 UTCresolved

   As of March 31, 2025, Microsoft no longer supports app-only authentication for the OneNote API. If you need to migrate OneNote files, you must use delegated permissions in accordance with Microsoft’s changes. For more information, please review our Help Center article(https://help.bittitan.com/hc/en-us/articles/360038153373-Using-Delegated-Permissions-for-OneDrive-SharePoint-and-Teams-migrations). If you have any questions, feel free to contact our support team.

1. 31. März 2025 um 16:36 UTCmonitoring

   Microsoft has announced a change to Exchange Web Services (EWS) access in Exchange Online, effective at some point in April 2025 (Microsoft has not provided a specific date for this change). Once this change has been made, EWS access will only be allowed if both the organization-level and user-level EWSEnabled flags are set to True. To avoid any service disruptions, please ensure that EWS is enabled at both levels in your Microsoft 365 tenant. If either flag is set to False, EWS requests will be denied, and your migrations or services relying on EWS may fail. We strongly recommend reviewing your settings in advance. For more information, refer to Microsoft’s official announcement: 👉 [The way to control EWS usage in Exchange Online is changing.](https://techcommunity.microsoft.com/blog/exchange/the-way-to-control-ews-usage-in-exchange-online-is-changing/4383083) If you need assistance, please contact our support team.

2. 2. Juli 2025 um 12:06 UTCresolved

   This informational notice about Microsoft’s upcoming EWS access changes is now closed. No further updates are expected. Please ensure your organization has made the necessary adjustments to avoid service disruption

1. 24. Februar 2025 um 17:09 UTCinvestigating

   We are aware that some customers are receiving a credential verification error for OneDrive migrations. The team is working to resolve this issue.

2. 27. Februar 2025 um 15:11 UTCresolved

   This incident has been resolved.

1. 3. Februar 2025 um 20:52 UTCidentified

   You may see an informational message noting that your destination region is outside of Germany but this message is in error. In fact your migration will run in the correct location, based on your settings. You can safely ignore this message.

2. 10. Februar 2025 um 16:39 UTCresolved

   This incident has been resolved.