Forum Discussion
Apr 19, 2017
Can't connect Outlook 2016 to my O365 Mailbox
Scenario: I have an Office 365 account with the email foo@contoso.com I have an old MSA account with the email foo@contoso.com Windows 10 - Creators Update (but tried this with a fully patched ve...
Salvatore Biscari
Apr 30, 2017Silver Contributor
Andrew, I think instead that it is very well worth.
Here is why:
- Where the MSA account ID is involved (as in the Windows login and everything about the MSA itself) all continues to work as usual: you don't need to change anything.
- Ditto for every other place where you could have used the emai as signinl, because you still have the email address itself (in O365) and therefore all continues to work as usual.
Try it.
Just my two cents...
Apr 30, 2017
I think you missed my point... I get what you're saying & completely agree.
But for the sites that use signin email for the identifier and not (like they should), the MSA account ID, changing your email screws you over as suddenly your account is orphaned on that site.
I've done this before with other MSA's and I've seen that happen. I've used this MSA for 10yrs+, and I'm not sure where it would be an issue... so I'm not about to be the one to test it until MSFT forces this change.
But for the sites that use signin email for the identifier and not (like they should), the MSA account ID, changing your email screws you over as suddenly your account is orphaned on that site.
I've done this before with other MSA's and I've seen that happen. I've used this MSA for 10yrs+, and I'm not sure where it would be an issue... so I'm not about to be the one to test it until MSFT forces this change.
- Simon MilborrowOct 20, 2017Copper Contributor
I will confirm that it was 2fa that was blocking my sign in also, once I disabled it, it went through first time although still took about 3 minutes to set up the account.
- DeletedSep 22, 2017
As far as I remember disabling/enabling was effective immediately.
- Philip McDanielSep 22, 2017Copper Contributor
How long did you have to wait for the disable of MFA to take place?
- DeletedJul 19, 2017
I had the same problem.
I my case it seemed to be related to two-factor auth being enabled in O365.Fixed it by temporarily (only while setting up the account in OL2016) disabling 2FA.