Is Microsoft Single Sign On safe?

Clean risk

Microsoft Single Sign On relays postMessage calls from any HTTPS page to a native Windows Web Authentication Manager (WAM) bridge via a hardcoded channel UUID.

The extension's content script registers a message listener on all HTTPS pages that forwards caller-supplied payloads to the native host com.microsoft.browsercore, which handles silent Entra ID / Azure AD authentication. The only inbound gate is a hardcoded channel UUID that is shipped in the extension bundle and readable by any page script, meaning any JavaScript on any HTTPS page can drive the native host with attacker-controlled method names and parameters. The background script injects the sender origin before forwarding, but does not otherwise restrict which pages or methods may invoke the bridge.

Microsoftv1.0.11Extension ID ppnbnpeolgkicgegkbkbjmhlideopijiChrome Web Store
1Risk
Who publishes it

Microsoft - 1 other listing from the same operator, none carrying a finding

Same store account

1 other listing published from this account, 2.0M+ users between them, none of them carrying a finding.

AI-assisted analysis.

What Microsoft Single Sign On can do

Permissions this extension asks for, as declared in version 1.0.11. Asking for a permission is not a finding on its own - it is what the extension can do if it chooses to.

  • Talk to a program installed on your computer, outside the browser's sandbox

    nativeMessaging

Where Microsoft Single Sign On sends data

  • com.microsoft.browsercore

    Found in its code · 1 other extension

Chrome Web Store listing

Versions
1.0.11 seen since March 4, 2026
Store rating
2.2 from 931 ratings
Last updated
August 1, 2024
Size
8.05 KiB
Privacy policy
privacy.microsoft.com
Updated June 21, 2026