Throughout this series<\/a>, we\u2019ve explored the possibilities and ways to grow and tailor your CRM and identified that though an implementation may be complete, your solution continuously evolves and changes. This means instead of considering your CRM a system to implement and abandon, it will require maintenance and attention to guarantee your investment was worthwhile and continues to perform as expected.<\/strong><\/p>\n This shouldn\u2019t be a cause for concern but instead considered as an opportunity for excitement to see all the ways you\u2019ll continue to benefit down the road from your Dynamics investment.<\/p>\n In this article, we\u2019ll explore things to consider for maintaining your Dynamics CRM deployment, including:<\/p>\n Once you deploy your system, check in to see if users leverage the capabilities as intended.<\/strong> Confident users who understand how new tools work greatly increase adoption. With user training enabling communications around best practices and standards, you can ensure that people follow data entry and business processes<\/a> correctly, resulting in good data quality.<\/p>\n Outside of general training post-implementation, users need continuous training to be aware of system changes that may occur throughout your platform\u2019s lifecycle. This may look like communications about new enhancements, lunch n\u2019 learns, or even periodically publishing self-service knowledge articles and job aids in your knowledge management system.<\/p>\n Data quality<\/a> is a critical component of your Dynamics 365 CRM maintenance activities. Good data quality is key to accurate outputs from your system processes and functionalities. You\u2019ll often hear garbage in, garbage out when it comes to data. Your system is only as useful as the information you provide.<\/p>\n Regular review and testing of your system functionalities can help ensure data quality. This might look like a business process for users who own records to routinely review their data and ensure it is up to date.<\/strong> This could also be a routine review and testing of field mapping to ensure accurate data carries over correctly. You should also have a cadence in place to process old, no-longer-needed records, whether that looks like deactivating or deleting. This will ultimately translate to accurate and consistent data, enabling you to be more efficient and provide stellar customer service<\/a>.<\/p>\n Another tip to ensure data quality is to implement required fields on forms and lock fields users should not update or change to ensure data quality.<\/p>\n Outside of implementing these review processes, Dynamics 365 has a few capabilities you can use to maintain your system\u2019s data quality, including Power Automate<\/a>, business rules, duplicate detection, and the record merge capability.<\/p>\n A regular review of reports and dashboards<\/a> affirms the information reflected populates accurately. Additionally, accessing new and current reports and dashboards is essential to maintenance tasks.<\/p>\n Dashboards and reports may require updates if you change fields, introduce new users to the system, add additional categories that may alter data displayed, or change business processes to introduce new stages or steps that might affect the logic of your reports and dashboards.<\/p>\n As part of your data loss prevention efforts, enable auditing for mission-critical entities to ensure you can retrieve and restore original records, if necessary, and monitor and track changes by date and user.<\/p>\n Additionally, establish a regular monitoring and reporting schedule for entity records that require maintaining a history for compliance. Lastly, standardize a review of how audit logs impact storage and capacity so that you have the space you need.<\/p>\n Prioritize the general awareness of activities impacting system performance. Implement regular reviews of system performance. This establishes a consistent user experience that results in users trust in the tools and their continued use as intended.<\/strong><\/p>\n Regular review of system performance and errors help to monitor that:<\/p>\n Using the Dataverse analytics area in the admin center is a great place to monitor high-level usage and performance.<\/p>\n Additional ways to monitor performance include leveraging the Solution Checker tool, verifying latency, and reviewing performance insights. You can read more about these capabilities in Microsoft documentation here<\/a>.<\/p>\n A standardized process to review user access helps to maintain system access and user permissions.<\/p>\n This process includes activities for granting and revoking access, such as purchasing and assigning licenses, creating and assigning security roles, and a regular review of existing application access.<\/p>\n A security access review process will ensure compliance and timely updates for user permissions. The recommended best practice is to grant users the least privilege required to achieve their job duties.<\/p>\n Outside of access to data, regularly monitoring system access and enabled users can save costs by disabling users and removing licenses users no longer need.<\/strong><\/p>\n The Dataverse analytics area in the Power Platform admin center provides great insights into usage by user and general environment analytics.<\/p>\n You need a strategy to manage your environments and establish processes about how to use these environments, who can create environments, and what data to store in each. This strategy ensures compliance and data access, and that users follow best practices for application development.<\/p>\n This might look like having dedicated admin accounts for making changes and user access to various development environments.<\/strong><\/p>\n Standard best practice is to ensure you have a development environment, testing environment, and production environment.<\/p>\n You can read more about establishing an environment strategy here<\/a>.<\/p>\n Users need a way to provide feedback and report system issues like a ticket management system or issue submission process. This enables you to stay on top of issues and allow you to quickly remediate and troubleshoot these.<\/p>\n Establish standards for how to test, remediate and fix issues. This might look like having a backlog where users can report bugs that the team can prioritize and resolve. Document resolutions to these issues in case you need to revisit them for future maintenance.<\/p>\n One of the major benefits of Dynamics 365 is that Microsoft continuously releases enhancements and new features for you to use.<\/p>\n It is important to stay current with upcoming releases and adequately prepare for these changes to keep your system operating smoothly.<\/p>\n The Microsoft release planner<\/a> is a great way to prepare for releases.<\/p>\n When anticipating releases, reviewing existing enabled functionalities the updates might impact and determining how you can implement and adopt these updates seamlessly is key.<\/p>\n This step might look like activities to gather requirements, get business stakeholder buy-in or approval to implement new features, establish a training plan, develop solutions, and develop test plans for new feature releases.<\/strong><\/p>\n Aside from new features, this activity should also include monitoring any feature deprecations you might need to prepare for and ensure the proper alternative infrastructure is in place before your current enabled functionality is no longer available.<\/p>\n Aside from keeping data quality and functionality up to par, another maintenance activity to consider is regularly monitoring your environment storage capacity.<\/p>\n Keeping your consumed capacity aligned with the available capacity guarantees performance and predicts unanticipated costs.<\/p>\n If you exceed the allotted environment capacity, this can result in a disabled environment, additional billing, and poor performance.<\/p>\n As an extension of your review and feedback process, you should also allow users to submit requests for enhancements or new functionality.<\/p>\n This process will drive system adoption and improve efficiency in how your platform processes information and addresses your organization\u2019s business needs.<\/strong><\/p>\n Business is evolving rapidly, and continuing to support changing business models and activities with your platforms can ensure you use the technology you\u2019ve invested in at the fullest capacity.<\/p>\n For example, you could add enhancement requests to your backlog for implementation as well as monitor if a feature is in the works or available from Microsoft<\/a>.<\/p>\n Establish a standard practice for user testing prior to the features Microsoft releases into production. Also, set standards for documenting and tracking test results for record keeping, ensuring compliance and that new functionality adequately meets the needs of your end users.<\/p>\n Now that we\u2019ve covered some of the standard processes you should have in place, we hope it is clear there are various critical elements and complexities to consider when maintaining a Dynamics 365 CRM. Putting the right team and resources in place can drive these activities, resulting in continued success and positive business outcomes.<\/p>\n Typical roles for system administration and maintenance include:<\/p>\n Ownership for the system\u2019s upkeep and maintenance allows you to continuously reap the benefits and advantages of your Dynamics system and that it continues to perform as intended and expected.<\/p>\n In the same way that we began our Dynamics journey, having a roadmap<\/a> that serves as your north star is critical for the continued success of your platform.<\/p>\n Revisit your roadmap often to continuously hone your vision and ensure maintenance activities support the direction outlined for implementation activities and beyond.<\/p>\n\n \n
Standard System Administration and Processes You Need<\/h2>\n
User Training<\/h3>\n
Data Quality<\/h3>\n
![\"Centric](\"https:\/\/centricconsulting.com\/wp-content\/uploads\/2023\/09\/Dynamics-Blog-Series-Part-5_Chart_082523.jpg\")
<\/a><\/p>\nReporting and Dashboards<\/h3>\n
Audit History<\/h3>\n
System Performance and Errors<\/h3>\n
\n
User Security, System Access, and Licensing<\/h3>\n
Managing Dynamics 365 CRM Environments<\/h3>\n
Issue Reporting Processes<\/h3>\n
Preparing for Microsoft Releases<\/h3>\n
Environment Storage Capacity<\/h3>\n
Continuous Improvement with Enhancements to Get the Most Out of Your Dynamics 365 CRM<\/h2>\n
Managing User Requests and Ensuring a Process is in Place<\/h3>\n
User Testing<\/h3>\n
It Starts with the Right Team<\/h2>\n
\n
\n
\n
\n
\n
Moving Forward with a Vision<\/h2>\n