Windows Accounts Windows Accounts

Productivity
Version: 1.0.7
Last Update: 2022-06-13

Overview

Windows Accounts is a Chrome extension developed by Microsoft. According to the data from Chrome web store, current version of Windows Accounts is 1.0.7, updated on 2022-06-13.
10,000,000+ users have installed this extension. 490 users have rated this extension with an average rating of .

Sign in to supported websites with accounts on Windows 10 and later versions

Use this extension to sign in to supported websites with accounts on Windows 10 and later versions. If you have a Microsoft supported identity on Windows 10 or later, you won’t be required to enter your credentials to sign in to supported websites. You’ll need to use this extension if your organization has implemented conditional access policy. Currently, this extension supports Azure Active Directory identities.

Rating

490 ratings

Total Installs

10,000,000+

Information

Last Update

2022-06-13

Current Version

1.0.7

Size

6.87KiB

Author

Microsoft

Website

None

Category

Productivity

Latest Reviews

See More

avatar Gagan Soni
2022-05-06

Hi All, Have you seen issue where ServiceWorker for Windows account extension has been unregistered automatically and causing on Azure wesbite (Portal.office.com) to stop working. Error "You can't get there from here). Windows account extension is still enabled and active.

There only option to register serviceworker back is to go into the Windows Account extension details and turn ON /OFF allow incognito mode option.

avatar Justin C
2022-05-02

In my opinion its a good extension, a useful one even. But it has its faults.

avatar Shovan Swain
2022-04-29

Doesn't work

avatar Peter Turek
2022-04-22

Doesn't seem to work with Windows Information Protection

avatar Mike Fink
2022-04-13

It works most of the time. Except for the occasions where it stops working inexplicably, and the Outlook webapp claims this extension isn't installed. Clearing cookies solves this for me, but it's stupid that such a workaround is needed, especially when the error message is completely wrong. I went several weeks reverting to running Outlook in Edge, assuming that some corporate security policy had gotten more restrictive before figuring this out the first time.