This article lists known limitations in ShareGate Protect.
Tenant configuration
Microsoft 365 Multi-Geo tenants are not supported. If your tenant uses Multi-Geo, Protect only displays data from the main geo environment. Data from satellite geo locations is not indexed or visible.
Meeting Workspace (MPS) sites are not supported. Sites built on the Meeting Workspace (MPS) template use a legacy SharePoint site type that Microsoft has deprecated. ShareGate Protect completely ignores them. They do not appear in any report, and their data is not indexed or crawled.
Data crawls
The initial crawl of the sharing links can take several weeks. When you first connect a tenant, ShareGate Protect needs to index all sharing links. In complex Microsoft 365 environments with a high volume of sharing links, this initial crawl can take several weeks to complete.
User sign-in data
Note: The following limitations apply to the Last sign-in date shown in Protect reports. See How Protect calculates the last sign-in date for full details.
No sign-in data before December 1, 2023. Microsoft only started tracking this data on that date and did not apply it retroactively. Users whose last successful sign-in was before December 1, 2023, will show a blank Last sign-in date.
The last sign-in date may appear blank or older than what Microsoft Entra shows. Protect only counts sign-ins where the user fully completed authentication. Failed attempts and background application sign-ins are excluded. Microsoft Entra includes both, which can cause the dates to differ.
Interactive and non-interactive sign-ins are not distinguished. Protect cannot determine whether the most recent successful sign-in was a user actively logging in or a background connection from an application like Outlook or Teams.
Data residency
Data processing occurs in the US East region, even for EU data residency. If you have selected the EU data residency option, data at rest is stored in Europe. However, all data processing still occurs in Microsoft Azure's East US 1 region.