While there are many IT services that our clients can move to the cloud, messaging seems to be most popular. Over a series of blog posts, we are going to share a few key lessons from cloud messaging deployments.
Define your requirements up front. Get them clearly documented and then let them drive all of your decisions: everything from What security features do we require in our cloud messaging platform? to How much email will we migrate to the cloud during our transition? The third part in this series will dive deeper into this topic.
Service monitoring can be tricky. Your cloud messaging vendor will not always notify you that an outage has occurred. Since the cloud solution isn’t a server that resides on premise, monitoring it will require special attention. And since accessing the cloud messaging platform requires an Internet connection, differentiating between an Internet problem and a cloud messaging problem is critical.
Make sure the path to support and issue escalation is clear. Email is serious business. If downtime occurs, it’s important that your personnel know how to engage the support of the cloud messaging vendor. Ensure that multiple individuals are authorized to open support incidents in case someone is out of the office.
If you go to the cloud, you may still need servers on-premise. It may seem counter-intuitive, but there are a number of architectural and migration scenarios that necessitate infrastructure on-premise. As a simple example, the scan-to-email multifunction printer in your corporate office may require a SMTP server on the corporate network.
In the next post in the series, we will cover four additional lessons learned in our cloud messaging deployments.