Outage in BitTitan

Impact to O365 migrations when using Impersonation permissions

Resolved Minor
May 21, 2021 - Started about 4 years ago - Lasted 10 months
Official incident page

Need to monitor BitTitan outages?
Stay on top of outages with IsDown. Monitor the official status pages of all your vendors, SaaS, and tools, including BitTitan, and never miss an outage again.
Start Free Trial

Outage Details

We are aware that some customers are experiencing the following error when migrating mailboxes to an O365 destination. "An internal server error occurred. The operation failed., Object reference not set to an instance of an object." Microsoft is aware of this issue and is working towards a fix. We are working urgently with Microsoft to seek guidance and an ETA on a permanent resolution and to ascertain any workaround available for customers. We will be providing further updates as soon as possible. We sincerely apologize for any inconvenience caused. Some affected customer admins may be able to see Microsoft's advisory in the MS Office Portal with incident number EX257082. This affects all of our MigrationWiz portals.
Latest Updates ( sorted recent to last )
RESOLVED about 4 years ago - at 06/02/2021 06:33AM

All indications show that the deployment of the fix has been completed by Microsoft and that this issue has been resolved for our customers.

MONITORING about 4 years ago - at 06/01/2021 07:12AM

Microsoft are continuing to deploy the fix for this issue to affected tenants. This could take 1 more day from now for this to be 100% deployed to all tenants. We have had reports where this has been deployed to tenants already and has resolved the issue. If you have been affected by this problem please continue to retry the migration to verify that the fix has been deployed. We will provide any further information as soon as we receive it from Microsoft. Thank you for your understanding.

IDENTIFIED about 4 years ago - at 05/30/2021 08:03AM

Microsoft are continuing to deploy the fix for this issue to affected tenants. This could take a further 3 days from now for this to be 100% deployed to all tenants. We have had some reports where this has been deployed to tenants already and has resolved the issue. If you have been affected by this problem please continue to retry the migration to verify that the fix has been deployed. In the meantime we will continue to provide any further information as soon as we receive it from Microsoft. Thank you for your understanding.

IDENTIFIED about 4 years ago - at 05/29/2021 08:08AM

Microsoft are continuing to deploy the fix for this issue to affected tenants. This could take a further 4 days from now for this to be 100% deployed to all tenants. We have had some reports where this has been deployed to tenants already and has resolved the issue. If you have been affected by this problem please continue to retry the migration to verify that the fix has been deployed. In the meantime we will continue to provide any further information as soon as we receive it from Microsoft. Thank you for your understanding.

IDENTIFIED about 4 years ago - at 05/28/2021 02:20PM

Microsoft are continuing to deploy the fix for this issue to affected tenants. This could take a further 5 days from now for this to be 100% deployed to all tenants. Although we have had some reports where this has been deployed to tenants earlier and has resolved the issue. If you have been affected by this problem please continue to retry the migration to verify that the fix has been deployed. In the meantime we will continue to provide any further information as soon as we receive it from Microsoft. Thank you for your understanding.

IDENTIFIED about 4 years ago - at 05/28/2021 03:54AM

Microsoft have provided an update that the fix for this issue is in the process of being deployed to affected tenants at this time. Note that it is expected to take up to 6 days from now for this to be 100% deployed to all tenants. Although we have had some reports where this has been deployed to tenants earlier and resolved the issue. If you have been affected by this problem please continue to retry the migration to verify that the fix has been deployed. In the meantime we will continue to provide any further information as soon as we receive it from Microsoft. Thank you for your understanding.

IDENTIFIED about 4 years ago - at 05/27/2021 06:35PM

The cause of the issue has been identified by Microsoft and we are working with them to develop a deployment plan for resolution as soon as possible and will provide further updates as information becomes available. We appreciate this is impacting our customers and apologize for any inconvenience caused

IDENTIFIED about 4 years ago - at 05/27/2021 11:23AM

Microsoft have provided an update that the fix for this issue is in the process of being deployed to affected tenants at this time. Note that it is expected to take up to 6 days from now for this to be 100% deployed to all tenants. Although we have had some reports where this has been deployed to tenants earlier and resolved the issue. If you have been affected by this problem please continue to retry the migration to verify that the fix has been deployed. In the meantime we will continue to provide any further information as soon as we receive it from Microsoft. Thank you for your understanding.

IDENTIFIED about 4 years ago - at 05/27/2021 02:50AM

Microsoft have provided an update that the fix for this issue is in the process of being deployed to affected tenants at this time. Note that it is expected to take up to 7 days from now for this to be 100% deployed to all tenants. If you have been affected by this problem please continue to retry the migration to verify that the fix has been deployed. In the meantime we will continue to provide any further information as soon as we receive it from Microsoft. Thank you for your understanding.

IDENTIFIED about 4 years ago - at 05/26/2021 04:31PM

Microsoft have provided an update that the fix for this issue is in the process of being deployed to affected tenants at this time. Note that it is expected to take up to 7 days from now for this to be 100% deployed to all tenants. If you have been affected by this problem please continue to retry the migration to verify that the fix has been deployed. In the meantime we will continue to provide any further information as soon as we receive it from Microsoft. Thank you for your understanding.

IDENTIFIED about 4 years ago - at 05/26/2021 04:29PM

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

IDENTIFIED about 4 years ago - at 05/26/2021 10:25AM

The fix from Microsoft for this issue is still being deployed to affected tenants at this time. Note that it is expected to take up to 7 days from now for this to be 100% deployed to all tenants. If you have been affected by this problem please continue to retry the migration to verify that the fix has been deployed. In the meantime we will provide any further information as soon as we receive it from Microsoft
Microsoft released an advisory earlier with further information (EX257082) and this can be downloaded from the following: https://bittitan.sharefile.com/d-s9150a59c5da74ef5a4a9a1fb8ce9b092
We will continue to provide further updates as soon as possible.

IDENTIFIED about 4 years ago - at 05/25/2021 10:54PM

The fix from Microsoft for this issue is still being deployed to affected tenants at this time. Note that it is expected to take up to 8 days for this to be 100% deployed to all tenants. If you have been affected by this problem please continue to retry the migration to verify that the fix has been deployed. In the meantime we will provide any further information as soon as we receive it from Microsoft
Microsoft released an advisory earlier with further information (EX257082) and this can be downloaded from the following: https://bittitan.sharefile.com/d-s9150a59c5da74ef5a4a9a1fb8ce9b092
We will continue to provide further updates as soon as possible.

IDENTIFIED about 4 years ago - at 05/25/2021 04:20PM

We have had confirmation from Microsoft that a fix is in the process of being deployed to affected tenants. Note that it is expected to take up to 8 days for this to be 100% deployed to all tenants. If you have been affected by this problem please continue to retry the migration to verify that the fix has been deployed. In the meantime we will provide any further information as soon as we receive it from Microsoft
Microsoft released an advisory earlier with further information (EX257082) and this can be downloaded from the following: https://bittitan.sharefile.com/d-s9150a59c5da74ef5a4a9a1fb8ce9b092
We will continue to provide further updates as soon as possible.

IDENTIFIED about 4 years ago - at 05/25/2021 01:04PM

The cause of the issue has been identified by Microsoft and we are working with them to develop a deployment plan for resolution as soon as possible and will provide further updates as information becomes available. Microsoft have released an advisory with further information (EX257082) and this can be downloaded from the following: https://bittitan.sharefile.com/d-s9150a59c5da74ef5a4a9a1fb8ce9b092
We will be providing further updates as soon as possible

IDENTIFIED about 4 years ago - at 05/25/2021 07:24AM

The cause of the issue has been identified by Microsoft and we are working with them to develop a deployment plan for resolution as soon as possible and will provide further updates as information becomes available. We appreciate this is impacting our customers and apologize for any inconvenience caused

IDENTIFIED about 4 years ago - at 05/24/2021 10:27PM

The cause of the issue has been identified by Microsoft and we are working with them to develop a deployment plan for resolution as soon as possible and will provide further updates as information becomes available. We appreciate this is impacting our customers and apologize for any inconvenience caused

INVESTIGATING about 4 years ago - at 05/24/2021 10:05PM

We are still working urgently with Microsoft to seek guidance and an ETA on a permanent resolution and to ascertain any workaround available for customers. We will be providing further updates as soon as possible. We appreciate this is impacting our customers and apologize for any inconvenience caused

INVESTIGATING about 4 years ago - at 05/24/2021 01:58PM

We are still working urgently with Microsoft to seek guidance and an ETA on a permanent resolution and to ascertain any workaround available for customers. We will be providing further updates as soon as possible. We appreciate this is impacting our customers and apologise for any inconvenience caused

INVESTIGATING about 4 years ago - at 05/24/2021 02:18AM

We are still working urgently with Microsoft to seek guidance and an ETA on a permanent resolution and to ascertain any workaround available for customers. We will be providing further updates as soon as possible

INVESTIGATING about 4 years ago - at 05/23/2021 02:35AM

We are still working urgently with Microsoft to seek guidance and an ETA on a permanent resolution and to ascertain any workaround available for customers. We will be providing further updates as soon as possible

INVESTIGATING about 4 years ago - at 05/22/2021 02:34AM

We are still working urgently with Microsoft to seek guidance and an ETA on a permanent resolution and to ascertain any workaround available for customers. We will be providing further updates as soon as possible

INVESTIGATING about 4 years ago - at 05/21/2021 11:18PM

We are still working urgently with Microsoft to seek guidance and an ETA on a permanent resolution and to ascertain any workaround available for customers. We will be providing further updates as soon as possible

INVESTIGATING about 4 years ago - at 05/21/2021 09:01PM

We are still working urgently with Microsoft to seek guidance and an ETA on a permanent resolution and to ascertain any workaround available for customers. We will be providing further updates as soon as possible

INVESTIGATING about 4 years ago - at 05/21/2021 07:02PM

We are still working urgently with Microsoft to seek guidance and an ETA on a permanent resolution and to ascertain any workaround available for customers. We will be providing further updates as soon as possible

INVESTIGATING about 4 years ago - at 05/21/2021 05:03PM

We are aware that some customers are experiencing the following error when migrating mailboxes to an O365 destination.

"An internal server error occurred. The operation failed., Object reference not set to an instance of an object."

Microsoft is aware of this issue and is working towards a fix. We are working urgently with Microsoft to seek guidance and an ETA on a permanent resolution and to ascertain any workaround available for customers. We will be providing further updates as soon as possible. We sincerely apologize for any inconvenience caused.

Some affected customer admins may be able to see Microsoft's advisory in the MS Office Portal with incident number EX257082.

This affects all of our MigrationWiz portals.

Be the First to Know When Vendors Go Down

With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.

Start free trial

No credit card required · Cancel anytime · 4200 services available

Integrations with Slack Microsoft Teams Google Chat Datadog PagerDuty Zapier Discord Webhook