Outlook 365 auto-configuration / discover works for one device, but not the other using the same user account

Question

Quick version:

What registry entries (making an assumption here) do I need for Outlook 365 on Windows 10 to auto-configure when everything is set up correctly on the back-end?

Long version for clarity:

On one device when I execute Outlook 365, the input field already has the currently logged in user's e-mail address populated (i.e. ******@thecompanydomain.com) and then there is the "Advanced options" drop-down where you can select the tickbox for "Let me set up my account manually".

I leave the "Let me set up my account manually" tickbox unchecked and then click on the "Connect" button and then shortly after that, I get the password prompt and after entering the password, I get the "Stay signed in to all of your apps" dialog box with the "Allow my organization to manage my device" tickbox, which is checked by default and I leave it that way and click on the "OK" button and then it proceeds to register the device successfully and says "You're all set" and then the "Account succesfully added" and I then click on "Done" and it proceeds to Outlook 365.

On another device using the exact same user account, when I execute Outlook 365, it goes to the dialog box where the e-mail address input field is NOT populated so I have to enter the e0mail address and then click on the "Connect" button and then that proceeds to the Outlook "Advanced setup" wher I have to select between Office 365, Outlook.com, Exchange, Google, POP, IMAP or Exchange 2013 or earlier. I select Office 365 and then it proceeds to the "Account successfully added" and then I click on the "Done" button and then Outlook 365 proceeds to load the profile and all is well.

Answer 1

If the workstation is joined to a domain or already has the account added to "Email & Accounts" of the workstation, the behavior works as described in the first example.
If the workstation is not domain-joined or does not have an 365 account added, then you see what you describe in the second example

Answer 2

Both devices are joined to the domain already, so that's why I was wondering if there needed to be specific entries added into the registry that forces that behavior. I looked at the user and machine registry hives related to Outlook, but didn't find anything that stood out. Thanks.

Answer 3

Hi @Clint ,
What’s the version of your Outlook(File>Office account>About Outlook)? It’s also suggested to check if there are any differences between your two devices(such as Windows version or others).

Could this issue be reproduced if you re-add your account via creating new profile in your two device? To further analyze your issue, please try to create a new profile and re-add your account (control panel>Mail>show profiles>Prompt for a profile to be used, then open your Outlook365>Options>New>type profile name>Add account) to check if the issue has any difference.

On another device using the exact same user account, when I execute Outlook 365, it goes to the dialog box where the e-mail address input field is NOT populated

Did you log in your company domain account to the Windows? In order to conduct your issue, please provide me with more information and test results mentioned above.

According to my test, I have tried to log in my domain account to other device but the address input field is null when I open my Outlook365(Version 2008 Build 13127 .20296 Click-to-Run), and when I create a new profile to add account in my own device, these addresses that I have already added on my Outlook sometimes could be displayed in that field but sometimes couldn't even I haven't changed any settings. I also did lots of research about this issue, but still haven't found any useful information. If I find any effective information about it later, I would post back.

---

If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 4

Sorry, I've been busy on other matters. I am using Office 365 semi-annual channel from September, 2020 (16.0.12527.21104). It would be best to forget the scenario where one machine works and one machine doesn't. I feel that just convolutes the conversation.

I start with a fresh Win10 1909 image with the September, 2020 updates and it is on-prem domain joined. I log in with my domain account and execute Office 365 and I get the UPN login prompt that is NOT automatically populated with the currently logged in domain user's UPN and after that, I then get the "Advanced setup" where I select between Office 365 and the other options. If everything is auto-discovering correctly, the UPN login prompt should already be populated with the UPN of the currently logged in domain user and then after OK'ing that dialog box, it should then automatically select Office 365 and complete the setup automatically.

Ultimately, I would just like to know "what" dictates the the UPN field automatically getting populated with the currently logged in domain user and "what" dictates "Office 365" being automatically selected for the Outlook "Advanced setup". Is that completely dictated server side (i.e. the Office 365 DNS records for AutoDiscover) or is it a combination of that and specific registry settings that has to be implemented on the Windows 10 device?

If I populate the tenant ID and UPN below, it will then populate the input field the very first time executing Office 365, but I believe that should not be necessary if everything is working correctly.

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\Configuration]
"O365ProPlusRetail.TenantId"=""
"O365ProPlusRetail.EmailAddress"=""

Even if I do that though, it still does not automatically select "Office 365" on the "Advanced setup" dialog box that comes up after that input field.

Thanks.

Answer 5

I installed a fresh install of Win10 1909 with the September, 2020 updates and Office 365 September semi-annual and it still has the problem, so it doesn't appear to be negatively impacted by anything in the actual operating system deployment process through SCCM with the task sequence steps.

I guess what I am most curious about is everything dictated server side for Office 365 to automatically picked up the user name and to automatically select Office 365 (as opposed to Exchange, GMail, etc.) or is it a combination of the server side configuration AND certain registry entries needing to be present on the WIn10 device?

Thanks.