I told the guys running Office 365 to uninstall it and use Office 2016 or be stuck with OWA and left it there. *Even with* these templates deployed and set up to configure Outlook automagically, Outlook 365 100% ignores all that configuration and goes to Office 365 directly, skipping the Exchange configuration entirely. Speaking of, after the original post I found out that the individual who was originally working on this network never deployed the Office 2016/365 ADMX templates, so I went ahead and did that. I do understand what's happened here is unsupported, but it's still really annoying that MS apps don't follow their own published rules! If an Office 365 account exists, apps completely ignore autodiscover records. It appears that Microsoft's bid for zero configuration means that any Microsoft mail app will prioritize Office 365 configuration above any other configuration. It appears this problem happens "all the time" to people who are planning on an Office 365 rollout in that window between starting O365 services and migrating on-prem Exchange. Once I found that thread linked above, I had some better search terms to look for. Right now I have no good solution to the "temporarily moved" error nor do I have a solution to Outlook's insane autodiscover prioritization, but at least I know I am not alone!Īfter spending yet more time on this problem, I believe there is no answer. Still, it suggests that Outlook itself does not follow Microsoft's published rules when Office 365 gets involved. Which describes exactly the symptoms I'm seeing, albeit in "real" Outlook 2016 and not Outlook 2016 365. While troublehooting the issue, I found this thread: So I've spent three hours working on that problem. :D Today, one of the other devs running O365 got the same warning. One of my devs who started the whole Office 365 problem got a warning that his "mailbox has been temporarily moved on Microsoft Exchange server." Because he did this to himself, I made him use OWA all day. I still have no resolution to this problem, and yesterday things got a little weirder. Again, application behavior, not IP/DNS/AD/"the internet" behavior. It is only Office 365 aware applications that have a problem here, which suggests there is something in Office 365 I can change to change their behavior. Put in an email address, they go find autodiscover, and everything is great. Office 365 autodiscover not working outlook android#Traditional activesync mail applications (say, Android Mail, or Outlook 2016) work perfectly. Office 365 autodiscover not working outlook windows#Outlook 365 (or Windows Mail, probably others) finds an email address associated with Office 365 and they try to retrieve mail settings from Office 365 instead of retrieving mail settings from the domain's actual autodiscover URL. The problem is strictly an application behavioral problem. The problem is NOT one of mail flow or really anything to do with mail. The domain has not and cannot be verified, those folks don't have the ability to do that. Separately an employee here signed up for and starting allocating 365 accounts. If nobody ever signed up for Office 365 then everything would be working 100% perfectly. A completely traditional 100% on premises domain network, with all related internal & external DNS. This is a "parallel" deployment where we have a fully functioning Exchange 2016 + Outlook 2016 deployment working. this is exactly the problem I had searching for an answer. I suspect there is a setting within the Office 365 admin that tells it where mail actually lives and to stop doing this, but I can't find the setting and I can't come up with the search terms to describe this phenomenon. This plays out on iPhones, Windows PCs, etc. You can actually watch this happen - for example in Outlook 365 on my Android tablet, when I add account, and enter my domain email address the banner instantly changes to "Office 365" and it rejects my domain password, but accepts my office365 password. and add account, it instantly recognizes the user account as a valid Office 365 user and then tries to get mail settings for that user from Office 365 instead of from autodiscover. When you use Outlook 365, or Windows Mail, etc. This problem is specific to certain Microsoft apps, or Office 365. The problem isn't with DNS - the on-premises Exchange and everything related works fine, MX is point to Exchange, autodiscover works properly. When you open Outlook 2016 and "add account" it goes off and looks for autodiscover and everything works properly.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |