Five Tips for On-Premises Dynamics 365 Finance and Supply Chain Deployments
Most deployments of Dynamics 365 Finance and Supply Chain are SaaS in the Microsoft cloud. With that said, there is an on-premises, self-hosted deployment option. Below outlines some tips for those on-premises to make the deployment and ongoing support successful.
- Requirement Changes. Monitor software and hardware requirement changes.
- Consistent monitoring of the software and hardware requirements pages will help prevent surprises. For example, SQL Server 2019 became a requirement in Service Update 10.0.21. If this was not known, it all of a sudden becomes an unexpected project.
- References:
- Service Updates. Keep up to date on service updates.
- When issues do arise, Microsoft support will more times than not say the issue or bug is already fixed and you should upgrade to the latest service update. Do this often, our suggestion is once a quarter.
- Monitoring. Implement your own monitoring tools.
- For SaaS in the cloud, Lifecycle Services offers plenty of monitoring tools. On-premises get none of those. Configuring or developing a comprehensive monitoring system and set of tools is paramount for successful operation. Consider infrastructure monitoring and SQL performance. As time goes on, needs may change as transaction volume grows.
- Direct Database Access. Limit direct database use.
- As the saying goes, just because you can doesn’t mean you should. On-premises has the benefit of direct access to the SQL database. But this doesn’t mean you should use that. Not only does it lock the deployment into on-premises, but it could also corrupt the application. Only modify data directly if directed by Microsoft Support with a support case. Backup before you do!
- Number of Environments. Determine the correct number of environments.
- On-premises deployments require more planning for long-term requirements than cloud deployment. In the cloud, adding or removing an entire environment is a series of clicks. Not so much on-premises. Ensure to think about the now and the future needs of the business to select the right number of environments. Consider how many ISVs could be implemented that may need a separate environment for testing. Typically, Production and UAT are the minimum number of environments. In our experience, this is too scant and at least three environments should exist, Production, UAT, and QA Testing. The more you have, the more you have to manage but the more flexibility you have for troubleshooting.
The tips above summarize a few considerations when choosing to go on-premises vs SaaS in the cloud. Considering on-premises? Reach out to Corterra. We have the expertise to ensure your success!
