This has to do with certificates and email - so I'm uncertain whether it should go in the security section (here) or in one ofthe Exchange forums... (?)
Anyway, here we go...
Usually I create a certificate request for the Exchange server on the Exchange server itself, submit the request and when the certificate is available, install the certificate and enable it.
What if an organization already has a wildcard certificate for its web servers...
What obstacles would prevent it from being used on an Exchange server?
The certificate is for "server authentication" - but probably not email (I know there are different certificate "types", "roles" or "templates" that may come into play here).
I was not involved in the purchase of the certificate, so I'm not sure if there is a maximum number of servers on which it can be used, or other legal considerations. That is something that must be taken into account all the same.
But from a technical standpoint, what would prevent a certificate (that can be exported, says the team involved in its acquisition) from being exported and imported to the Exchange server?
Getting a certificate specifically for the Exchange server might make more sense (I'm certainaly more familiar with that option) but would the situation above even be feasible?
One last note: there might be a migration to Exchange Online in the future.
Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.