Odd one this one since it feels like the "s" should always appear in a http but never mind.
We are running CRM2013 on prem and under HTTP://. We are installing ServerSide Email synchronisation to better use the creation/routing of inbound emails that need to map to the service team.
One of the requirements for Server Side is that the database is encrypted to ensure that account impersonation is done securely. It feels like this should be a pretty straight forward task of binding old http to new https.
I would appreciate any hints and tips that will help de-complicate this job or give me some indicators of areas where it could go badly wrong.
Kind regards
Dave