54 Bittitan incidents · 2020年10月 — official updates, affected components, duration and resolution details.
2026年10月21日,国安局和联邦调查局发布了关于PHP(CVE-2026-109618和CVE-2026-109619)中两个关键弱点的可允许远程代码执行的指南. 我们检视了我们的暴露系统。 移民Wiz平台不使用PHP,也不受影响. 我们的营销网站使用PHP,我们应用了必要的补丁. 我们已经证实,脆弱性问题已经得到解决。 我们最终确定,对客户数据或服务供应没有影响。 无需客户采取行动。 移民、邮箱和账户访问不受影响.
自动翻译自官方事件更新。
我们目前正在调查一个影响私人查特移民小组的问题。 在认证核实期间,客户可能看到一个错误,表明在源租户上没有发现用户. 这个问题仅限于Teams Private Chat迁移. 其他移徙类型不受影响。 我们的小组意识到这个问题,正在积极调查。 一旦掌握更多信息,我们将提供最新情况.
这一事件已经得到解决.
自动翻译自官方事件更新。
我们正在调查一个影响我们基础设施工作分配的问题,导致在提交国等待工作的时间延长。 我们的工程团队正在积极开展工作,以查明并解决根源。 需要采取的行动:如果您的工作在提交国等待时间超过1小时,请停止受影响的项目线并重新提交。 我们将随着调查的进展提供最新资料,并对中断事件道歉.
影响我们基础设施工作分配的问题已经解决。 工作处理正常,在提交国等待的时间已恢复到预期水平。 如果您已停止并重新按我们先前的指引提交项目线, 并且仍然出现延迟, 请联系支援 .
自动翻译自官方事件更新。
迁移Wiz 文档迁移出错 2026年8月19日的系统升级提高了总的文件迁移速度和吞吐量之后,我们发现一个影响到一小部分客户的问题。 一些用户在文件迁移时可能遇到以下错误之一: "收集被修改; 计数操作不能执行". "时间和长度都超出了" "没有从文件中读出所有字节". 这些错误并不表明数据丢失。 它们是8月19日发布中包含的DLL升级的结果,这使得更新后代码无法读取升级前生成的日志. 我们意识到这个问题,并正在积极制定更广泛的决议。 建议采取的步骤 如果您遇到上述错误之一, 请执行重设项目并重新提交迁移通行证 。 这在大多数情况下解决了这个问题。 有关说明,请参见MigrationWiz中如何重置项目. https://help.bittitan.com/hc/en-us/articles/360042167494-MigrationWiz-Statistics-Statistics-Lookup#01H8HMGW00PCG8XHWPM7QHWJD 如果执行重置项目后该错误持续存在, 请打开一个支持大小写, 这样我们的团队就可以直接协助您, 而我们的工作是更广泛的修正 。 我们将在这里提供最新情况 随着我们的调查继续进行.
这一事件已经得到解决.
自动翻译自官方事件更新。
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.
The root cause has been determined, and we are working to release a change to address this error shortly.
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.
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.
This incident is resolved.
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.
This incident has been resolved.
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.
This incident is now resolved.
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.
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.
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]
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.
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.
We are continuing to work on a fix for this issue
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.
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.
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
This incident has been resolved.
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
Some customers may experience migrations stuck in the submitted state. We are aware of this issue and are working to resolve it.
We have implemented a change and are seeing previously stalled migrations being processed. We are continuing to monitor the situation.
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.
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.
This incident has been resolved.
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.
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.
We are continuing to work on a fix for this issue.
All previously identified issues have been resolved.
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.
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.
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.
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.
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.
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
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)
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.
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.
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
We are aware that some customers are receiving a credential verification error for OneDrive migrations. The team is working to resolve this issue.
This incident has been resolved.
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.
This incident has been resolved.
