Not quite - it's used on (some) Chromebooks, as in the HTML5 version of Netflix only runs on locked down hardware from Google partners. Unlock the hardware so you can run your own software on the Chromebook and the media decryption module refuses to decrypt anything.
The various content providers seem to have used the advent of HTML5 to insist on stricter DRM requirements, ones that can only be met through control over the entire hardware and software stack. I presume Microsoft's version uses the long-standing GPU support for hardware decryption and acceleration of DRMed video instead of whatever ChromeOS does. Apparently unlike the Google version it's possible for other browsers to freely support HTML5 EME that's compatible with Microsoft's DRM, but naturally only on Windows: http://msdn.microsoft.com/en-us/library/windows/apps/dn46673...
It surprises me a bit to hear that the same doesn't happen with desktop Chrome.