Edge Browser User Agent

-->

The WIASupportedUserAgents defines the user agents which support WIA. AD FS analyzes the user agent string when performing logins in a browser or browser control. You can view the current settings using the following PowerShell example: Get-AdfsProperties select -ExpandProperty WiaSupportedUserAgents Change WIASupportedUserAgent settings.
You can always check the User-Agent-string. Pressing F12 for the developer tools; Tabulator: Console; type: 'navigator.userAgent' + hit return; works in IE, Edge, Chrome. In IE and Edge you can simply overwrite it for the current windows on the Tabulator:Emulation, field.

A user agent (UA) string is able to be used to detect what version of a specific browser is being used on a certain operating system. Like other browsers, Microsoft Edge includes this information in the User-Agent HTTP header whenever it makes a request to a site. It may also be accessed via JavaScript by querying the value of navigator.userAgent.

Microsoft recommends that web developers make use of feature detection whenever possible to improve code maintainability, reduce code fragility, and eliminate the risk of code breakage in the event of future UA string updates.

For cases where feature detection is not applicable and UA detection must be used, the format of the Microsoft Edge UA on desktop is as follows:

The User-Agent request header is in the following format:

Description Change User-Agent Setting of Edge. Spoof it to User-Agent of Google Chrome, Mozilla Firefox, Chrome on Android, Safari on iPhone or macOS, Googlebot or your custom string. Choose from preset User-Agent strings, or Add your own custom User-Agent string.

The return value from navigator.userAgent is in the following format:

Platform identifiers change based on the operating system being used, and version numbers also increment as time passes. This format is the same as the Chromium UA with the addition of a new Edg token at the end. Microsoft selected the Edg token to avoid compatibility issues that may be caused by using the string Edge, which is used by the version of Microsoft Edge based on EdgeHTML. The Edg token is also consistent with existing tokens used on iOS and Android.

Mapping UA String to Browser Name

Mapping UA string tokens to a more human-readable browser name for use in code is a common pattern on the web today. When mapping the new Edg token to a browser name, Microsoft recommends using a different name than the one developers used for the legacy version of Microsoft Edge to avoid accidentally applying any legacy workarounds that are not applicable to Chromium-based browsers.

User Agent Overrides

Sometimes, a website does not recognize the updated version of the Microsoft Edge UA. As a result, a set of the features of that website may not work correctly. When Microsoft is notified about these types of issues, website owners are contacted and informed about the updated UA.

The sites often need some time to update and test the UA detection logic to address the issues that Microsoft reports to site owners. In these cases, Microsoft uses a list of UA overrides in our Beta and Stable channels to maximize compatibility for users who access these sites. The overrides specify new UA values that Microsoft Edge should send instead of the default UA for specific sites. You are able to view the list of UA overrides that are currently being applied by navigating to edge://compat/useragent in the Beta and Stable channels of Microsoft Edge.

Our Canary and Dev channels do not currently receive UA overrides so that web developers have an environment where they can easily reproduce issues on their sites that are caused by the default Microsoft Edge UA. If for some reason you require the ability to disable UA overrides in the Beta or Stable channels of Microsoft Edge, you may run the Microsoft Edge executable using the following command line argument:

The standard way to pass information to the server about the visiting device is to include it in the User-Agent (UA) string. This information typically passes the name and version of the browser among many other details. In order to get an understanding of which mobile browsers use your site, you need to know their User-Agent strings.

Here’s a handy list of UAs that you may want to use.

What is the User-Agent and what information does it pass?

Described in the HTTP standard, the User-Agent string contains a number of tokens that refer to various aspects of the request, including the browser’s name and version, rendering engine, device’s model number, operating system and its version, etc.

From a web developer’s perspective, User-Agent strings can be useful when it comes to testing how online content is rendered on various hardware and software combinations. What works well on Chrome Mobile and the latest Android may not work the same on an older device and browser.

Most common mobile browsers

The landscape of mobile browsers is quite complex, with several major players (pre-installed in most cases) and a number of locally popular contenders. While all phones come with pre-installed browsers, both Google Play and Apple App Store offer a number of alternative browsers, some focusing on speed and lightness, others on saving bandwidth and blocking ads, and an ever-increasing amount claiming to increase privacy and reduce a users' mobile digital footprint. (We discussed some of the more popular privacy-respecting browsers.)

According to our report on the most popular mobile browsers, Safari Mobile, Chrome Mobile, and Samsung Browser are the three most used mobile browsers across the globe. The report also lists a number of other locally popular apps for web browsing, such as UC Browser, Yandex Browser, IE Mobile, Opera Mobile, Opera Mini, Firefox, and MIUI Browser. Feel free to browse the stats for your local market using our Data Explorer tool.

Edge Browser Change User Agent

The Complete Guide To User Agents.

Download our free e-book on User Agents to learn:

What is a User Agent?
How do you parse them?
What can you do with them?

List of mobile browsers User-Agent strings

The following table contains User-Agent strings for all the most used mobile browsers today. Note that UAs used by mobile browsers vary depending on the browser version, device model, OS, and many other factors.

Safari for iOS
Mozilla/5.0 (iPhone; CPU iPhone OS 10_3_1 like Mac OS X) AppleWebKit/603.1.30 (KHTML, like Gecko) Version/10.0 Mobile/14E304 Safari/602.1

Android Browser
Mozilla/5.0 (Linux; U; Android 4.4.2; en-us; SCH-I535 Build/KOT49H) AppleWebKit/534.30 (KHTML, like Gecko) Version/4.0 Mobile Safari/534.30

Chrome Mobile
Mozilla/5.0 (Linux; Android 7.0; SM-G930V Build/NRD90M) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.125 Mobile Safari/537.36

Opera Mobile (Blink rendering engine)
Mozilla/5.0 (Linux; Android 7.0; SM-A310F Build/NRD90M) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.91 Mobile Safari/537.36 OPR/42.7.2246.114996

Opera Mobile (Presto rendering engine)
Opera/9.80 (Android 4.1.2; Linux; Opera Mobi/ADR-1305251841) Presto/2.11.355 Version/12.10

Opera Mini
Opera/9.80 (J2ME/MIDP; Opera Mini/5.1.21214/28.2725; U; ru) Presto/2.8.119 Version/11.10

Opera Mini (iOS WebKit)
Mozilla/5.0 (iPhone; CPU iPhone OS 7_1_2 like Mac OS X) AppleWebKit/537.51.2 (KHTML, like Gecko) OPiOS/10.2.0.93022 Mobile/11D257 Safari/9537.53

Firefox for Android
Mozilla/5.0 (Android 7.0; Mobile; rv:54.0) Gecko/54.0 Firefox/54.0

Firefox for iOS
Mozilla/5.0 (iPhone; CPU iPhone OS 10_3_2 like Mac OS X) AppleWebKit/603.2.4 (KHTML, like Gecko) FxiOS/7.5b3349 Mobile/14F89 Safari/603.2.4

UC Browser
Mozilla/5.0 (Linux; U; Android 7.0; en-US; SM-G935F Build/NRD90M) AppleWebKit/534.30 (KHTML, like Gecko) Version/4.0 UCBrowser/11.3.8.976 U3/0.8.0 Mobile Safari/534.30'

Dolphin
Mozilla/5.0 (Linux; Android 6.0.1; SM-G920V Build/MMB29K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.98 Mobile Safari/537.36

Puffin for Android
Mozilla/5.0 (Linux; Android 5.1.1; SM-N750K Build/LMY47X; ko-kr) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.135 Mobile Safari/537.36 Puffin/6.0.8.15804AP

Puffin for iOS
Mozilla/5.0 (Linux; Android 5.1.1; SM-N750K Build/LMY47X; ko-kr) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.135 Mobile Safari/537.36 Puffin/6.0.8.15804AP

Samsung Browser
Mozilla/5.0 (Linux; Android 7.0; SAMSUNG SM-G955U Build/NRD90M) AppleWebKit/537.36 (KHTML, like Gecko) SamsungBrowser/5.4 Chrome/51.0.2704.106 Mobile Safari/537.36

Yandex Browser
Mozilla/5.0 (Linux; Android 6.0; Lenovo K50a40 Build/MRA58K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.137 YaBrowser/17.4.1.352.00 Mobile Safari/537.36

MIUI Browser
Mozilla/5.0 (Linux; U; Android 7.0; en-us; MI 5 Build/NRD90M) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/53.0.2785.146 Mobile Safari/537.36 XiaoMi/MiuiBrowser/9.0.3

IE Mobile
Mozilla/5.0 (compatible; MSIE 10.0; Windows Phone 8.0; Trident/6.0; IEMobile/10.0; ARM; Touch; Microsoft; Lumia 950)

Edge Mobile
Mozilla/5.0 (Windows Phone 10.0; Android 6.0.1; Microsoft; Lumia 950) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Mobile Safari/537.36 Edge/15.14977

BlackBerry Browser
Mozilla/5.0 (BB10; Kbd) AppleWebKit/537.35+ (KHTML, like Gecko) Version/10.3.3.2205 Mobile Safari/537.35+

Get access to a free, fully-working local version trial of DeviceAtlas.

Our high performance flagship product - the most complete data set.

How to parse User-Agent strings

As you can easily notice from the list above, each User-Agent string contains a number of keywords that may obfuscate the device behind the request. For example, most UAs listed here include 'Mozilla' and 'Mobile Safari.'

The result is that UA parsing solutions must be sophisticated enough to understand which elements of a UA are meaningful. A simple regex solution searching for keywords will struggle in terms of accuracy and detection speed. To make things worse, the number of UA combinations grows every time a new device, browser, browser's version, or OS version are released.