ShareGate Migrate uses user agent strings to identify itself when communicating with Microsoft services such as SharePoint and Microsoft 365.
These strings are sent with each request to ensure compatibility with the APIs and servers that ShareGate connects to.
In some cases, ShareGate uses user agent strings that reference older browser identifiers, such as MSIE 10.0, to maintain reliable communication with services that were initially built to recognize those identifiers.
Understanding which user agents ShareGate Migrate supports can be helpful when troubleshooting connectivity issues or configuring network and firewall rules that filter traffic based on user-agent strings.
ShareGate user agents explained
Mozilla/5.0
What it is
A legacy compatibility token.
Why ShareGate Migrate uses it
Historically, many websites were coded to recognize “Mozilla” as a valid browser. Nearly all modern browsers still include this token for backward compatibility.
Important
It does not mean the application is Mozilla Firefox.
Compatible
What it is
A legacy Internet Explorer compatibility flag.
Why ShareGate Migrate uses it
Indicates the client is operating in compatibility mode with legacy browser standards.
MSIE 10.0
What it is
A historical Internet Explorer version identifier.
Why ShareGate Migrate uses it
ShareGate Migrate uses Microsoft’s Trident rendering engine (the legacy Internet Explorer engine) internally for authentication workflows.
The Trident engine automatically identifies itself using the Internet Explorer format.
It is the embedded engine’s legacy identifier.
Important
The app or user is not running Internet Explorer 10.
The Operating System(OS) is not outdated.
Internet Explorer is not used as a browser.
Windows NT 6.2
What it represents
The Windows operating system version.
Mapping
NT 6.2 maps to Windows 8 / Windows Server 2012
Important
Many frameworks preserve this string for compatibility even on newer Windows versions. It does not necessarily reflect the actual OS version.
Trident/6.0
What it is
The version of Microsoft’s Trident rendering engine.
Why ShareGate Migrate uses it
Trident 6.0 corresponds to the Internet Explorer 10 engine.
This confirms the request is coming from a Microsoft WebView/embedded browser component.
Important
Internet Explorer is not used as a browser.
MS FrontPage
What it is
A legacy Microsoft token related to SharePoint and older Microsoft web technologies.
Why ShareGate Migrate uses it
SharePoint historically used FrontPage Server Extensions.
Some SharePoint SOAP endpoints still reference this legacy identifier.
Important
This is common in SharePoint traffic and does not indicate actual use of FrontPage.
Sharegate
What it is
The primary product identifier.
Why ShareGate Migrate uses it
This clearly indicates the traffic originates from ShareGate Migrate. This is the most relevant and unique identifier in the string.