I was hoping that someone could help myself and others better understand the certificates feature.
Is this for storing certificates similar to storing product keys and so forth? Just want to be sure I am not missing some customized virtual directory path for a company to have their own OWA URL and Certificate. I know that was asked about in the forums 4 years ago, just making sure that over time this hasn’t been developed into a feature.
We use SAN certificates that we add and remove SANs as needed so I wanted to be sure that we still need to do this if we want the customer domain URL for OWA and autodiscovery and so forth to have a cert name match.
Thank You!
The certificates feature under documentation is just storing information about SSL certificates you have (documentation nothing to do with configuration). Also adding/removing names from a SSL for your clients sounds like you don’t really have it setup for a multi-tenant way. It works the way you are doing it but it isn’t best practice. That is why you would have to use the SRV method or the HTTP redirect method (although autodiscover v2 doesn’t support the redirect method anymore)
Got an article on the SRV method for multi-tenant as I am not familiar with this approach and only know the single OWA/ECP instance method with a single certificate of the SAN type. Please help point me in the right direction as we are interested in best practice for multi-tenant supporting autodiscover dns without seeing a cert mismatch warning to end users for say mail.CLIENTDOMAINNAME.com being used. Thank you and please assume I am looking to learn the best-practice method for any implementation. We are testing out your product and thus far lots of positive things to say so please excuse the ignorance in the multi-tenant methodology. Any assistance is much appreciated.
