• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue Issues with Office365 setup and Plesk

smileyriley21

New Pleskian
Hi,

I hope you are all well and thanks in advance for any help and support.

We have a client who is using an external company to setup office365 to manage their emails. The website is hosted on our Plesk box.

Office365 is failing as it is somehow looking at the default self signed SSL certificate for the plesk panel and not getting any further

Any ideas how to resolve this? The IT company are baffled, my hosting company are baffled and everyone is blaming everyone else.

If you use "SSL Shoppers SSL Checker" tool and add any domain from either of our Plesk boxes that do not have a dedicated SSL certificate it comes up with the following errors, which relate to the default self signed certificate for the panel.

This certificate is self signed, users will receive a warning....
Certificate no allocated to this domain.

If I look at other domains we have hosted (not using Plesk) these errors are not reported.


Any help, much appreciated.

Kind Regards

Chris




PS: We host with both UKFast and Rackspace
 
When you use Office365, you must update several DNS records to route mails to the Microsoft systems instead of routing than through or to your Plesk server. Once you have updated the records, your Plesk server is no longer responsible for handling any mails of your domain. Exact and detailed information on the entries that need to be set in DNS is given by Office365 upon setup. If DNS is setup correctly, Office365 will not connect to the Plesk server at all. Nor during setup, neither during operations.

Bottom line: Make sure that the MX and TXT records that Microsoft requires for the Office365 configuration are set correctly and everything will work like a charm.
 
Back
Top