Istoricul incidentelor Bittitan

1. 21 octombrie 2026 la 21:31 UTCresolved

   Pe 21 octombrie 2026, NSA și FBI au emis orientări privind două vulnerabilități critice în PHP (CVE-2026-109618 și CVE-2026-109619) care ar putea permite executarea la distanță a codului. Ne-am revizuit sistemele de expunere. Platforma MigrationWiz nu utilizează PHP și nu este afectată. Site-ul nostru de marketing utilizează PHP și am aplicat patch-urile necesare. Am confirmat că vulnerabilitatea a fost abordată. Am stabilit în mod concludent că nu a existat niciun impact asupra datelor clienților sau a disponibilității serviciilor. Nu este necesară nicio acțiune din partea clienților. Migraţiile, cutiile poştale şi accesul la conturi nu sunt afectate.

Traducere automată din actualizarea oficială a incidentului.

1. 14 octombrie 2026 la 14:04 UTCinvestigating

   Investigăm în prezent o problemă care afectează migraţiile Echipelor Private Chat. În timpul verificării credibile, clienții pot vedea o eroare care indică faptul că utilizatorul nu a fost găsit pe chiriaș Sursa. Această problemă este limitată la echipele private chat migrații. Alte tipuri de migrație nu sunt afectate. Echipa noastra este constienta de problema si investigheaza activ. Vom oferi o actualizare de îndată ce vom avea mai multe informații.

2. 14 octombrie 2026 la 15:19 UTCresolved

   Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 23 septembrie 2026 la 16:01 UTCinvestigating

   Investigăm o problemă care afectează sarcinile de angajare pentru infrastructura noastră, ceea ce duce la prelungirea timpului de așteptare pentru locurile de muncă din statul solicitat. Echipa noastră de ingineri lucrează activ pentru a identifica şi rezolva cauza principală. Acţiune necesară: Dacă locurile dvs. de muncă aşteaptă de mai mult de 1 oră, vă rugăm să opriţi liniile de proiect afectate şi să le resuscitaţi. Vom oferi actualizări pe măsură ce investigaţia noastră progresează şi ne cerem scuze pentru întrerupere.

2. 24 septembrie 2026 la 02:48 UTCresolved

   Problema care afectează sarcinile de locuri de muncă pentru infrastructura noastră a fost rezolvată. Locurile de muncă sunt de prelucrare în mod normal, și timpii de așteptare în statul trimis au revenit la nivelurile preconizate. Dacă v-ați oprit și ați reluat liniile de proiect pe orientările noastre anterioare și sunt încă văd întârzieri, vă rugăm să contactați sprijinul.

Traducere automată din actualizarea oficială a incidentului.

1. 3 septembrie 2026 la 13:58 UTCinvestigating

   MigrationWiz Document Erori de migrare Ca urmare a unei actualizări a sistemului la 19 august 2026 care a îmbunătăţit viteza globală de migrare a documentelor şi de trecere, am identificat o problemă care afectează un subset mic de clienţi. Unii utilizatori pot întâmpina una dintre următoarele erori în timpul migrării documentelor: "Colecția a fost modificată; operațiunea de enumerare nu poate fi executată." "Offset and long were out of limits" "Nu a citit toate octeți din fișier." Aceste erori nu indică pierderea datelor. Acestea sunt rezultatul unei actualizări DLL incluse în lansarea din 19 august, ceea ce determină ca jurnalele generate înainte de actualizare să nu poată fi citite prin codul actualizat. Suntem conștienți de această problemă și lucrăm activ la o rezoluție mai largă. Etape recomandate Dacă vă confruntați cu una dintre erorile de mai sus, vă rugăm să efectuați un Reset items și resuscitați permisul de migrare. Aceasta rezolvă problema în majoritatea cazurilor. Pentru instrucțiuni, consultați Cum se resetează elementele din MigrationWiz. A se vedea Decizia nr. În cazul în care eroarea persistă după efectuarea unui Reset items, vă rugăm să deschideți un caz de sprijin, astfel încât echipa noastră vă poate ajuta direct în timp ce lucrăm la un fix mai larg. Vom furniza actualizări aici pe măsură ce ancheta noastră continuă.

2. 8 septembrie 2026 la 15:01 UTCresolved

   Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 8 iulie 2026 la 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 iulie 2026 la 15:42 UTCinvestigating

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

3. 8 iulie 2026 la 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 februarie 2026 la 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 februarie 2026 la 21:31 UTCresolved

   This incident is resolved.

1. 23 februarie 2026 la 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 februarie 2026 la 13:40 UTCresolved

   This incident has been resolved.

1. 13 februarie 2026 la 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 aprilie 2026 la 13:27 UTCresolved

   This incident is now resolved.

1. 8 ianuarie 2026 la 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 ianuarie 2026 la 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 ianuarie 2026 la 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 ianuarie 2026 la 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 ianuarie 2026 la 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 ianuarie 2026 la 19:29 UTCidentified

   We are continuing to work on a fix for this issue

7. 30 ianuarie 2026 la 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 februarie 2026 la 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 decembrie 2025 la 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 decembrie 2025 la 22:03 UTCresolved

   This incident has been resolved.

1. 8 decembrie 2025 la 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 decembrie 2025 la 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 decembrie 2025 la 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 decembrie 2025 la 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 decembrie 2025 la 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 decembrie 2025 la 17:42 UTCresolved

   This incident has been resolved.

1. 5 decembrie 2025 la 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 decembrie 2025 la 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 decembrie 2025 la 15:30 UTCidentified

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

4. 5 decembrie 2025 la 16:33 UTCresolved

   All previously identified issues have been resolved.

1. 28 mai 2025 la 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 iulie 2025 la 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 iulie 2025 la 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 aprilie 2025 la 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 aprilie 2025 la 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 aprilie 2025 la 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 aprilie 2025 la 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 iulie 2025 la 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 martie 2025 la 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 iulie 2025 la 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 februarie 2025 la 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 februarie 2025 la 15:11 UTCresolved

   This incident has been resolved.

1. 3 februarie 2025 la 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 februarie 2025 la 16:39 UTCresolved

   This incident has been resolved.