MS O365 Autodiscovery: Failing
-
First troubleshooting step for autodiscovery is make 100% sure DNS records are correct.
-
Don't disagree. However, I deleted my Outlook profile to allow Outlook to auto-create.
Same network, different accounts, but my account auto configured in mere seconds over the completely failing the user is getting.
-
@gjacobse said in MS O365 Autodiscovery: Failing:
Has anyone encountered this issue today when trying to create the Outlook User profile on initial signon.
Yes. Had to use the troubleshooting tool to get it to work (locally installed Outlook sucks, I stick with the PWA version whenever possible now). Tool can be found here: https://support.microsoft.com/en-us/office/resolve-outlook-for-windows-issues-with-automated-troubleshooting-tools-38e2342d-3527-4190-8754-a82d8b970fe2
-
Did you copy the profile over from another PC? I have had this happen when the profile is copied using a transfer tool.
-
@wls-itguy said in MS O365 Autodiscovery: Failing:
Did you copy the profile over from another PC? I have had this happen when the profile is copied using a transfer tool.
No - New User / New Profile.
-
@gjacobse Change DNS to 1.1.1.1 and try, then change it back to internal DNS...
-
@gjacobse said in MS O365 Autodiscovery: Failing:
ounts, but my account auto configured in mere seconds over the completely failing the user is getting.
I get this with the wrong account in Credential Manger or on the Windows Accounts
-
Sidetracked, late update.
Signed the user out of all MS products, One sign in received a message that the user didn’t have an account.ADUC / AAD both showed the user as valid and licensed
-
@gjacobse is auto discover disabled for this user?
-
@dustinb3403 What do you mean disabling autodiscover for a user? Are you talking about a registry key?
-
@dbeato said in MS O365 Autodiscovery: Failing:
@dustinb3403 What do you mean disabling autodiscover for a user? Are you talking about a registry key?
No, within O365 you can either selectively disable authentication protocols because you're a glutton for punishment or you can do so with conditional access policies or Security Defaults.
-
@gjacobse said in MS O365 Autodiscovery: Failing:
Sidetracked, late update.
Signed the user out of all MS products, One sign in received a message that the user didn’t have an account.ADUC / AAD both showed the user as valid and licensed
Have you tried the troubleshooting tool yet? It's worked for me a lot lately when nothing else makes any sense.
That or just break down and install the PWA version and be done with it.
-
@travisdh1 said in MS O365 Autodiscovery: Failing:
@gjacobse said in MS O365 Autodiscovery: Failing:
Sidetracked, late update.
Signed the user out of all MS products, One sign in received a message that the user didn’t have an account.ADUC / AAD both showed the user as valid and licensed
Have you tried the troubleshooting tool yet? It's worked for me a lot lately when nothing else makes any sense.
That or just break down and install the PWA version and be done with it.
MS SaRA - Yes,.. Sara was used, and useless.
-
@gjacobse said in MS O365 Autodiscovery: Failing:
@travisdh1 said in MS O365 Autodiscovery: Failing:
@gjacobse said in MS O365 Autodiscovery: Failing:
Sidetracked, late update.
Signed the user out of all MS products, One sign in received a message that the user didn’t have an account.ADUC / AAD both showed the user as valid and licensed
Have you tried the troubleshooting tool yet? It's worked for me a lot lately when nothing else makes any sense.
That or just break down and install the PWA version and be done with it.
MS SaRA - Yes,.. Sara was used, and useless.
Dang. Sorry man. Outlook errors are so unhelpful.
-
I had a similar problem several months ago with an existing O365 account. The user could no longer configure Outlook for their account and the problem happened across 3 machines. The user could access the online version of Outlook. After spending weeks with MS support with no success, I ended up disabling MFA for the user and Outlook worked again. After testing a few things, I enabled MFA again and it stayed working. No idea why that was the fix, but we've had a lot of problems enabling MFA for users.
Hope this helps.
-
@dustinb3403 said in MS O365 Autodiscovery: Failing:
@dbeato said in MS O365 Autodiscovery: Failing:
@dustinb3403 What do you mean disabling autodiscover for a user? Are you talking about a registry key?
No, within O365 you can either selectively disable authentication protocols because you're a glutton for punishment or you can do so with conditional access policies or Security Defaults.
Well you can disable Autodiscover as a whole organization through the modern authentication setting, however in order to have conditional access you have to have higher licensing than normal which is why I am confused at the disabling comment.
-
@dbeato said in MS O365 Autodiscovery: Failing:
@dustinb3403 said in MS O365 Autodiscovery: Failing:
@dbeato said in MS O365 Autodiscovery: Failing:
@dustinb3403 What do you mean disabling autodiscover for a user? Are you talking about a registry key?
No, within O365 you can either selectively disable authentication protocols because you're a glutton for punishment or you can do so with conditional access policies or Security Defaults.
Well you can disable Autodiscover as a whole organization through the modern authentication setting, however in order to have conditional access you have to have higher licensing than normal which is why I am confused at the disabling comment.
Just a P2 license to setup a conditional access license for the administrator account(s). The user accounts don't require this level of licensing.
Why is it a confusing question?
