# Cannot register to Microsoft Account

**URL:** <https://onlykey.discourse.group/t/cannot-register-to-microsoft-account/205>\
**Category:** Two Factor Authentication\
**Created:** [January 30, 2021, 3:04pm UTC](https://onlykey.discourse.group/t/cannot-register-to-microsoft-account/205 "2021-01-30T15:04:56Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![Extrawdw](https://yyz2.discourse-cdn.com/free1/user_avatar/onlykey.discourse.group/extrawdw/32/60_2.png) [@Extrawdw](https://onlykey.discourse.group/u/Extrawdw)\
**Post date:** [January 30, 2021, 3:04pm UTC](https://onlykey.discourse.group/t/cannot-register-to-microsoft-account/205/1 "2021-01-30T15:04:56Z")

</div>

After upgrading the firmware to the latest, I can no longer register OnlyKey to Microsoft/Office 365 Accounts, the following error message shows:

> We couldn’t verify your identity or you are using private mode. Please ensure you are not in a private browsing window and please try again.

I tried to register a YubiKey in the same environment, it could go through. I also tried to register on another computer. another browser, no luck.

---

<div class="post-metadata">

**Author:** ![Extrawdw](https://yyz2.discourse-cdn.com/free1/user_avatar/onlykey.discourse.group/extrawdw/32/60_2.png) [@Extrawdw](https://onlykey.discourse.group/u/Extrawdw)\
**Post date:** [January 30, 2021, 3:12pm UTC](https://onlykey.discourse.group/t/cannot-register-to-microsoft-account/205/2 "2021-01-30T15:12:50Z")

</div>

I get my Firefox and it worked, weird…

---

<div class="post-metadata">

**Author:** ![t11](https://avatars.discourse-cdn.com/v4/letter/t/8e7dd6/32.png) [@t11](https://onlykey.discourse.group/u/t11)\
**Post date:** [February 1, 2021, 1:17am UTC](https://onlykey.discourse.group/t/cannot-register-to-microsoft-account/205/3 "2021-02-01T01:17:44Z")

</div>

What OS/Browser did you find that did not work? We have tested in all major OS/Browser combinations but there are still some issues where FIDO2 does not always work.

---

<div class="post-metadata">

**Author:** ![Extrawdw](https://yyz2.discourse-cdn.com/free1/user_avatar/onlykey.discourse.group/extrawdw/32/60_2.png) [@Extrawdw](https://onlykey.discourse.group/u/Extrawdw)\
**Post date:** [February 1, 2021, 8:16pm UTC](https://onlykey.discourse.group/t/cannot-register-to-microsoft-account/205/4 "2021-02-01T20:16:26Z")

</div>

Chrome and Edge  
I suspect that the cause of the problem is not the browser, but OnlyKey FIDO2 seems to have some problems with the Attestation Certificate.  
When I tried WebAuthn on [Yubico demo website](https://demo.yubico.com/webauthn-technical/registration), it has Attestation Certificate related errors (in the “technical details”) of OnlyKey.

---

<div class="post-metadata">

**Author:** ![t11](https://avatars.discourse-cdn.com/v4/letter/t/8e7dd6/32.png) [@t11](https://onlykey.discourse.group/u/t11)\
**Post date:** [February 1, 2021, 10:11pm UTC](https://onlykey.discourse.group/t/cannot-register-to-microsoft-account/205/5 "2021-02-01T22:11:27Z")

</div>

Thats odd, here is a screenshot of me accessing this site in chrome, it shows no errors just comes up as unknown device since its not a Yubikey.

 ![image](https://global.discourse-cdn.com/free1/uploads/onlykey/original/1X/542e794f66120b7e715f8d15e971dc4ea39a0773.png)

Did you maybe set a custom attestation certificate? This is a feature we used to support but removed recently.

---

<div class="post-metadata">

**Author:** ![Extrawdw](https://yyz2.discourse-cdn.com/free1/user_avatar/onlykey.discourse.group/extrawdw/32/60_2.png) [@Extrawdw](https://onlykey.discourse.group/u/Extrawdw)\
**Post date:** [February 2, 2021, 8:04am UTC](https://onlykey.discourse.group/t/cannot-register-to-microsoft-account/205/6 "2021-02-02T08:04:52Z")

</div>

Scroll down to see `Attestation Certificate` part, for YubiKey I use, there is one, but for OnlyKey, it says " There was a problem parsing the attestation certificate, please check the console logs". For Azure Active Directory, the default option is “require Attestation”. In this case, OnlyKey cannot be registered. User have to contact their directory administrator to disable Attestation, which is sometimes difficult to do.

---

<div class="post-metadata">

**Author:** ![tfluthy](https://avatars.discourse-cdn.com/v4/letter/t/3da27b/32.png) [@tfluthy](https://onlykey.discourse.group/u/tfluthy)\
**Post date:** [February 19, 2021, 4:21pm UTC](https://onlykey.discourse.group/t/cannot-register-to-microsoft-account/205/7 "2021-02-19T16:21:23Z")

</div>

I’m having the same issues that you are. If it’s a chromium based browser, it doesn’t work, while Firefox it does work.

---

<div class="post-metadata">

**Author:** ![t11](https://avatars.discourse-cdn.com/v4/letter/t/8e7dd6/32.png) [@t11](https://onlykey.discourse.group/u/t11)\
**Post date:** [February 19, 2021, 5:33pm UTC](https://onlykey.discourse.group/t/cannot-register-to-microsoft-account/205/8 "2021-02-19T17:33:04Z")

</div>

@Extrawdw it always says there is a problem with all keys I have tested except Yubikeys, I think they are looking for a Yubico cert. @tfluthy Are you having issues on Linux or a different OS?

---

<div class="post-metadata">

**Author:** ![Extrawdw](https://yyz2.discourse-cdn.com/free1/user_avatar/onlykey.discourse.group/extrawdw/32/60_2.png) [@Extrawdw](https://onlykey.discourse.group/u/Extrawdw)\
**Post date:** [February 19, 2021, 5:43pm UTC](https://onlykey.discourse.group/t/cannot-register-to-microsoft-account/205/9 "2021-02-19T17:43:14Z")

</div>

I found that even successfully register on Firefox, cannot login on Chome…

---

<div class="post-metadata">

**Author:** ![Extrawdw](https://yyz2.discourse-cdn.com/free1/user_avatar/onlykey.discourse.group/extrawdw/32/60_2.png) [@Extrawdw](https://onlykey.discourse.group/u/Extrawdw)\
**Post date:** [February 19, 2021, 5:46pm UTC](https://onlykey.discourse.group/t/cannot-register-to-microsoft-account/205/10 "2021-02-19T17:46:47Z")

</div>

If the Azure AD Admin turn off the “Requite Attestation” in Azure AD login options, then OnlyKey will work fine for Office 365 accounts. However no way for personal Microsoft Account.

---

<div class="post-metadata">

**Author:** ![tfluthy](https://avatars.discourse-cdn.com/v4/letter/t/3da27b/32.png) [@tfluthy](https://onlykey.discourse.group/u/tfluthy)\
**Post date:** [February 19, 2021, 6:24pm UTC](https://onlykey.discourse.group/t/cannot-register-to-microsoft-account/205/11 "2021-02-19T18:24:34Z")

</div>

What happens with my systems, if you register on firefox, in may or may not work in chrome, but the first time it fails in chrome, the security key vanishes out of MS account security portal

---

<div class="post-metadata">

**Author:** ![tfluthy](https://avatars.discourse-cdn.com/v4/letter/t/3da27b/32.png) [@tfluthy](https://onlykey.discourse.group/u/tfluthy)\
**Post date:** [February 19, 2021, 6:29pm UTC](https://onlykey.discourse.group/t/cannot-register-to-microsoft-account/205/12 "2021-02-19T18:29:52Z")

</div>

T11,

Windows 10 enterprise, newest version. Firefox is reliable, chromium is not

---

<div class="post-metadata">

**Author:** ![t11](https://avatars.discourse-cdn.com/v4/letter/t/8e7dd6/32.png) [@t11](https://onlykey.discourse.group/u/t11)\
**Post date:** [February 19, 2021, 7:02pm UTC](https://onlykey.discourse.group/t/cannot-register-to-microsoft-account/205/13 "2021-02-19T19:02:27Z")

</div>

For Azure AD yes you can disable ‘Enforce Attestation’ more info here - [Error adding Yubikey to Security Info - Microsoft Q&A](https://docs.microsoft.com/en-us/answers/questions/3908/error-adding-yubikey-to-security-info.html)

Currently Azure AD only supports security keys from a handful of providers and even that seems to sometimes not work with ‘Enforce Attestation’ enabled.

For the 2nd issue with Chrome and Microsoft account, this is a legitimate issue caused by new version of Chrome. A fix will be included in the next OnlyKey firmware update.
