Anonymized engagement summary: Dynamics 365 CRM security-model, data-model and Unified Interface remediation after an EPC Group assessment, for a professional association (2021)
Anonymized engagement summaryProfessional association · 2021
Opening answer. In 2021 EPC Group was engaged by a professional association for ongoing Dynamics 365 CRM support and consulting. It followed an earlier EPC Group assessment of the association's Dynamics 365 system. The assessment's findings report set the priorities:
1. rationalize the security model, because access was effectively wide open: general users could see data they should not, and many could delete key records 2. clean up the data model by removing unnecessary custom fields and unused custom tables, and tidying the solution inventory 3. complete the migration to the Unified Interface with role-based apps 4. improve usability through department-specific forms and views 5. rationalize licensing, including the portal
The engagement also sets service-level objectives for break-fix support and for project work.
This is an anonymized engagement summary published under EPC Group's anonymized-engagement rule: the client is not named, no commercial terms are published, and every statement is EPC-reported. Named, documented engagements are in the Evidence Center.
Problem and scope
| Item | Scope |
|---|---|
| Organization | A professional association |
| Situation | A Dynamics 365 CRM system with security roles that left access wide open, an overgrown data model, the legacy web interface still in use, and licensing (including a portal) not matched to use |
| Security | Fix the security roles in use and check every role assignment |
| Data model | Evaluate custom fields against standard ones and migrate data before removing a custom field, updating business rules where needed; consolidate or remove tables and fields that are not used; clean up the solution-file inventory |
| Unified Interface | Complete the move off the legacy interface by designing apps for specific user groups, and review dashboards so they surface items needing immediate attention |
| Usability | Review forms and views, remove unused fields, and configure forms and views per department where requirements differ |
| Licensing | Review current and planned use of each module, including whether the out-of-the-box portal or a custom portal integrated with Dynamics 365 is more cost-effective |
| Support model | Service-level objectives for technical support (break-fix and urgent care across the Dynamics 365 platform, solutions, extensions and applications) and for project work (platform improvements and model-driven, canvas or hybrid app development), with a named escalation point and periodic engagement reviews |
Not reported: user counts, the number of custom fields and tables removed, and any measured result.
Approach and artifacts
Assessment first, then a prioritized plan. The work is ordered by risk, as set out in the assessment's findings report. Locking down the security model comes first because users could see and delete records they should not reach. Structural clean-up and the interface migration follow.
Clean the model safely. Data in a custom field is migrated to its standard equivalent and business rules are updated before the field is removed. Tables with no purpose are taken out, so the system becomes simpler without losing data.
Apps per user group. The Unified Interface migration is used to design apps around the groups that use them, each with only the forms and views that group needs.
What EPC Group delivered and what is not claimed
| Claim | Basis | Status |
|---|---|---|
| EPC Group assessed the association's Dynamics 365 system and reported findings | EPC engagement record | On file (EPC-reported) |
| The association contracted EPC Group for ongoing Dynamics 365 support and remediation | EPC engagement record | Contracted (EPC-reported) |
| Security model fixed, data model cleaned, apps delivered, or measured results | Not reported | Not claimed |
Related services
Dynamics 365 · Data governance · All case studies · Talk to a senior architect
Last updated by Errin O'Connor, Founder & Chief AI Architect, EPC Group
Author: Errin O'Connor, Founder & Chief AI Architect, EPC Group · Published October 25, 2026 · Project alias EPC-2021-ANON-ASSOC-D365 · Published under the anonymized-engagement rule.