Hi @Guillaume SPECQUE ,
Welcome to Microsoft Q&A!
Since I know little about OVH, I'd like to confirm which version of Exchange server you are using? Noticed that you selected "Office 365 service" when running the test using Microsoft Remote Connectivity Analyzer, so is it that your email accounts are hosted in Exchange Online?
Besides, please run an Outlook connectivity test using the following link instead and see if any clues can be found:
https://testconnectivity.microsoft.com/tests/O365Ola/input
It's also suggested to use the Test E-Mail Autoconfiguration service in Outlook and check the output:
- While Outlook is running, click the CTRL key and then right-click the Outlook icon in the system tray, select “Test Email Autoconfiguration”.
- Confirm that your email address is in the address field, uncheck “Use Guessmart” and “secure Guessmart authentication” boxes. Then click the “Test” button.
- Once it runs, check the Log tab and Results tab.
Furthermore, I can understand that you may have already verified that there's no problem on OVH side, but considering that the issue is indeed involving OVH, personally I'd still suggest trying to visit the OVH community as well to see if there are others who are in the same situation or have experienced similar issue.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
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.
no im not on exchange online but on a ovh private exchange offer...
Hello Yuki, and thanks a lot for your precious help.
We are not alone in ths situation, at least 2 other OVH customers with exactly same problem, at the same time...
I tried your link and iv got this error:
Test de la connectivité Outlook.
Le test de la connectivité Outlook a échoué.
Étapes de test
L’analyseur de connectivité de Microsoft essaie de tester la découverte automatique pour sxxx@xxxx.com...
Merci de patienter.Échec de la découverte automatique de test.Étapes de testEssai de chaque méthode pour contacter le service de découverte automatique.Échec de contact du service de découverte automatique avec toute méthode.
Étapes de testTentative de test de l’URL potentielle de découverte automatique https://autodiscover-s.outlook.com:443/Autodiscover/Autodiscover.xmlLe test de cette URL de découverte automatique éventuelle a échoué.Étapes de testTentative de test de l’URL potentielle de découverte automatique https://xxxx.com:443/Autodiscover/Autodiscover.xml
Le test de cette URL de découverte automatique éventuelle a échoué.
Étapes de testNous vérifions s’il existe un enregistrement CNAME de découverte automatique dans DNS pour votre domaine «xxxx.com» pour Office 365.Désolé...
Nous n’avons pas pu valider l’enregistrement CNAME de découverte automatique dans le DNS. Si votre boîte aux lettres n’est pas dans Office 365, vous pouvez ignorer cet avertissement. En savoir plus sur ce problème et sa résolutionDétails supplémentaires
Votre domaine « xxx.com » ne contient aucun enregistrement de découverte automatique CNAME.
I changed nothing on my dns and domains since at least 3 years.
Ive got 0365 licences but i'm using OVH Exhange Private offer, since 10 years. And it is the first time iv got this big problem.
For the second test i cant open Outlook because of this ID problem, as it doesn't recognize my ID it open another ID popup... until it close Outlook.
Thanks a lot for your help Yuki
Hi @Guillaume SPECQUE ,
The test link I shared earlier is intended for Office 365, so you can just ignore the output since you are not using Exchange Online. Please try the link below instead and see if there would be any clues.
https://testconnectivity.microsoft.com/tests/Ola/input
Be sure the remove all personal information like domain name and email address if you need to share the output.
Given this, agree with your assumption that it could be related to any recent update on OVH, so I'd recommend continue trying to contact OVH to take a further look into this issue.
Sign in to comment