11-04-2019
2:00pm
Incident Update - Creation and Deletion of Site Collections in Microsoft 365 environments
Our latest tests seem to confirm that the issue is now resolved.
______________________________________________
11-04-2019
10:00am
Incident Update - Creation and Deletion of Site Collections in Microsoft 365 environments
We have been informed Microsoft is aware of, and actively working on the issue. Updates to follow.
______________________________________________
11-04-2019
9:00am
Incident Update - Authentication loop
Patch 10.1.1 has successfully resolved the issue.
______________________________________________
10-04-2019
4:00pm
Incident - Creation and Deletion of Site Collections in Microsoft 365 environments
A situation affecting Site Collections in Microsoft 365 environments has recently been detected. This issue was flagged in our internal tests on April 9, 2019, and it seems related to SharePoint Online changes made by Microsoft. We are actively looking into this with Microsoft. Updates will be sent as we know more.
What does it affect?
Creation and Deletion of Site Collections in Microsoft 365 environments, most often when connected at the tenant level. The problems are intermittent and not systematic.
Scope
We are unable to determine the scope and impact at this moment.
Solution or workaround
It may be possible to manually create your site in SharePoint before using the ShareGate migration tool to merge your content in. Please note that unfortunately this workaround does not cover all scenarios impacted by these changes.
______________________________________________
10-04-2019
4:00pm
Incident - Authentication loop
A situation affecting authentication had been detected. This issue was flagged in our internal tests on April 8, 2019.
What does it affect?
Browser authentication. The the ShareGate migration tool app becomes stuck in an authentication loop that requires users to keep submitting their credentials.
Scope
The ShareGate migration tool version 10.0.9 and 10.1.
Solution or workaround
Install patch 10.1.1 to resolve the issue.