Several issues reguarding your 2FA activation pipeline in MS Accounts

there are 3 problems, specifically, allrelating to the 2FA setup process.

1. In the setup process, specifically when using an authenticator different to MS Authenticator, when you are presented with the QR code used to add your account to an authenticator app, you are asked to enter the current code generated by the authenticator app. Even if the key is correct and completely unmodified, it never thinks the code is correct, making finisshing the setup process impossible.
2. (connected to 1) Even more serious of a problem is the fact that, if you click Cancel at any point during the setup process, 2FA is left on despite cancel meaning that you want to end setup and not enable 2FA. This is a problem of a medium-high risk (it would be high if 2FA usage was common) further escalated in risk by bug 1. If you are a new user wanting to enable 2FA (which I assume MS should promote due to lower account theft rate): Due to bug 1, you believe 2FA setup is somehow hard and give up by clicking cancel, and due to bug 2, when you click cancel, 2FA remains on, potentially locking you out of your account because when you login next time, you need to present a code you possibly do not have (because you deleted it because you thought you would never need it anymore).
3. If you DO use MS authenticator, after you link your MS account and go and check your security settings, the settings due show the Authenticator notification as a verification method (which I assume is the 2FA verification), but under additional methods, 2FA is NOT shown as on, although you just setup Authenticator. This ONLY happens if you setup authenticator outside the 2FA setup in the account page.

I contacted MS support on the 2 first problems, and they told me I would recieve a response within 72h. Every troubleshooting step was followed and failed. After 72h, I did not recieve any response whatsoever from MS, so I contacted support again, seeking a response and they told me to come here to post my issue.

The third one I have just discovered out of curiosity with how MSes own solution would perform, which, I must admit, is better (though it seems to setup another system, not a standard OTP code), so I think it was just a cosmetic bug.

For anyone who has aceess to support requests, my support code(s) is

2FA protection is left on even if you click cancel at setup step (#7103281635)

and 7103476327 (for the one directing me here)