A reddit dedicated to the profession of Computer System Administration. Community members shall conduct themselves with professionalism. Do not expressly advertise your product. More details on the may be found. For IT career related questions, please visit Please check out our, which includes lists of subreddits, webpages, books, and other articles of interest that every sysadmin should read! Checkout the Users are encouraged to contribute to and grow our Wiki.
So you want to be a sysadmin? Official IRC Channel - #reddit-sysadmin on Official Discord -. TL:DR - Outlook 2016 autodiscover to O365 broken, download KB 3073666 as workaround. If you try to deploy Office 2016 (specifically Outlook 2016) and connect it to an existing Office 365 account for email, autodiscover will probably give you fits. It just does not work reliably, and in many cases will not work at all.
How to set up safe senders and blocked senders in Office 365. Content provided by Microsoft. Applies to: Exchange Online. How to set up safe senders and blocked senders in bulk. How to update an existing safe sender and blocked sender list. Apr 16, 2018 - Outlook for Mac does support iCloud Mail. For steps on how to configure your iCloud email account in Outlook for Mac, go to the 'More.
It just hangs and never completes. Because of this 'minor' oversight from our friends at Microsoft, you may find it frustrating and just about impossible to get Outlook 2016 to connect to an Office 365 email account. No problem, right? I'll just manually create a new profile.
Because of changes to Outlook 2016, it is much more difficult to create a working profile manually or edit the profile settings. After wasting a couple of hours yesterday to try to get Outlook 2016 to connect to an existing Office 365 email account, I discovered a temporary workaround that I'd like to share. Microsoft has a pre-release product called 'Microsoft Office 365 Support and Recovery Assistant'. If you download and install this package on the affected PC, it appears to run a battery of checks and tests and then will manually create an Outlook 2016 Profile for the affected Office 365 account (using the information that you provide). Once the profile is created, Outlook 2016 will then start and connect to the Office 365 account properly. Here is the link to download the Assistant: How Outlook 2016 was shipped in this state is beyond me.
After many years in the IT trenches, I am no longer surprised to see a major product update shipped with a major feature broken. While I am no longer surprised, I refuse to be accepting of this behavior. How can a company with over 115,000 employees and $$billions$$ in the bank ship a major product that can't even connect to it's own service? Outlook 2010 autodiscover seems to work just fine, same with Outlook 2013. Outlook 2016 autodiscover, not so much. Think I'm going to take a chance on a Surface Book?
I doubt I'd even use it if they gave me one. /end rant. There is a reason that E3/E4 Office365 users have to be manually added to a first release BETA group to even download the software. Anyways we have a few guys in the first release group running 2016 with no issues so far. I am running 2016 on windows 10 enterprise no issues, outlook set right up using autodiscover.
We use 365 with E3 and active directory sync (No SSO or AD FS, just account/password sync). Make sure you have the proper autodiscover AND msoid CNAMES configured. Test with testexchangeconnectivity.com.
Also try and install the Sign in assistant tool as it will manage your outlook's connection. Download here:.
Just to make sure that folks understand - this is Outlook 2016 connecting to Office 365 using autodiscover. Outlook 2016 connecting to non Office 365 Exchange seems to be fine using autodiscover. Too little detail? How about this addition: Autodiscover works just fine with Outlook 2007, 2010 and 2013 when connecting to Office 365.
It does not work with Outlook 2016. Multiple PC's.
Multiple attempts, all using the same Office 365 domain and same domain accounts. Tried from two different locations just to rule out an ISP issue.
And tried Office 2016 H&B click to run and Office 2016 Professional Plus. That pretty much rules out any problems with the Domain and DNS. CNAME Autodiscover for the domain points to autodiscover.outlook.com, just like it's supposed to. I waited for over an hour on some systems and it still would not connect. Tried multiple times & after reboots. Why should I need to mess with the registry to get something that works just fine with the older versions to work properly with Outlook 2016? I won't accept that this is OK.
Maybe not for everyone, but it's broken. I'm not the only one seeing this: I tried the suggestion from this thread of using the.onmicrosoft.com domain first but it did not work reliably on all systems for me. Using the MS KB tool that I posted originally was the only way I found to get it working reliably on all systems. I was having the same problem using 2016 off internal dns. Briefly switching to Google or other external dns works for auto discover and then I can switch back. Went back through to make sure no one changed the entries on our on premise dns server and everything was fine. Spent like half a day looking through forums for a solution in between knocking out tickets then I had a new user connect no problem to 2010.
![365 365](/uploads/1/2/5/4/125484936/137699699.gif)
That's when I realized it was solely new 2016 installs that's having the issue. I haven't looked in to it since the first day 2016 was released but I'm not surprised there's starting to be a little bit of noise about the issue. Nor did I realize there is a solution now. Everyone in this thread assumes OP is incompetent and gangs up on him? He then posts proof that it's actually happening to others (microsoft forum), and says the exact same thing is happening to him as well.
But since you guys haven't seen the problem you refuse to believe it might just exist? What if the problem only lies with certain DNS providers? Or is some strange ipv6-related bug that most people won't see yet? Or is some really nitpicky packet bug that only occurs in certain situations?
Ok so I am using Office 365 Mail I got through GoDaddy with my domain. I set it up and it worked through Edge and the Windows 10 Mail App just fine for about a week. I wake up one day and noticed the mail wasn't coming through to my Mail App on Windows 10 and when I went into the app it said it needed to update settings so I said ok. The WIN10 Mail app redirected me to the GoDaddy Office 365 LogIn and I logged in as usual and all I get is a # on a white blank page. I try a few things out and realize the same thing now happens through the Edge browser trying to check my email through the Office 365 website. Same white page with a #.
Funny thing is I can do the web Log in on any other browser. I'm thinking the last Windows 10 update broke this. Can anyone help me here?
I really liked using the Windows10 Mail App for my business Office 365 email. It seems Windows 10 uses the Edge browser to connect through the Mail App regardless of my default browser. I think it is the Edge browser messing all this up but not sure. I had this same issue and figured out a solution yesterday. In order to work around having to go through a login page at the account creation, in the account set up, select the advanced option at the very bottom. When I manually put in the right incoming and outgoing server, it works just fine.
My email is also through GoDaddy, but I believe this info is standard across all Office365 email. Inbound- outlook.office365.com outbound- smtp.office365.com Leave all the boxes checked below the info. Your username is your whole email. The First two boxes don't matter. It's simply what you want the mail program to name the account when you look at it and then what you want people to see your name as when you send email. So, I would just add a new account this way and then delete the other. There's no difference in how the account is used.
It just means you have to know the servers instead of having the app find them. I had this same issue and figured out a solution yesterday. In order to work around having to go through a login page at the account creation, in the account set up, select the advanced option at the very bottom. When I manually put in the right incoming and outgoing server, it works just fine. My email is also through GoDaddy, but I believe this info is standard across all Office365 email.
Inbound- outlook.office365.com outbound- smtp.office365.com Leave all the boxes checked below the info. Your username is your whole email.
The First two boxes don't matter. It's simply what you want the mail program to name the account when you look at it and then what you want people to see your name as when you send email. So, I would just add a new account this way and then delete the other. There's no difference in how the account is used. It just means you have to know the servers instead of having the app find them.