Attempting to resolve the host name name.
Attempting to test potential Autodiscover URL https : //:443/Autodiscover/Autodiscover.xml Testing of this potential Autodiscover URL failed. Teststeps: The Microsoft Connectivity Analyzer is attempting to test Autodiscover for. I let him run the following Test: "Office 365" - "Microsoft Office Outlook Connectivity Tests" - "Outlook Autodiscover" and personaly don't see anything wrong. We have also tried to setup a completly new E-Mail profile.
#Outlook for mac 2016 wont connect to office 365 echange password#
We've also logged in via to make sure mail and password are correct. Using his own private devices such as notebook, pc, mac, phone works.
Is there a possibility for me to receive a test account to try? So I can’t tell, if it would work with others. I only have one user, from which i know, who is trying to use Office 365. Whether PCs or Zero Clients (Virtual Machines). It doesn’t work on any of our domain joined devices. I cant find anything usefull in event log. Outlook client turns endlessly "Searching without any error message. One of our users has a Microsoft Office 365 Business Premium Account for one User.Īdding the account to outlook as usual automatically with name, email and password doesn’t work. Only Office365 mail address doesn’t work using Outlook in our domain. I’m afraid it has something to do with our own autodiscovery.Īutomatically adding our own mail addresses hosted by our on premise exchange and even adding other accounts such as Hotmail works fine. In our Domain we have our own Exchange 2016 server. We are having trouble with users who wish to connect their own private office 365 account automatically on a Domain joined Windows 7 client in Outlook 2013 and Outlook 2016.
0 kommentar(er)
