Anonymized engagement summary: Dynamics 365 CRM security-model, data-model and Unified Interface remediation after an EPC Group assessment, for a professional association (2021)
Contracted — countersigned (EPC-reported; documents private)First-pass editionA professional association (client not named) · 2021 · Project ID EPC-2021-ANON-ASSOC-D365
Last updated by Errin O'Connor, Founder & Chief AI Architect, EPC Group
Opening answer. In November 2021 a professional association's President countersigned a statement of work with EPC Group 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 statement of work also sets service-level objectives for break-fix support and for project work.
Disclosure. This is an EPC-reported anonymized engagement summary. The client is not named. The countersigned statement of work, which restates the assessment's findings, is retained privately and is not published in the Evidence Center, so this account is outside the Evidence Center's documented-engagement counts. Every engagement fact below is taken from that document.
Verification class
Contracted — countersigned (EPC-reported; documents private). The association's President signed the statement of work in November 2021. It cites the report of findings and recommendations from the Dynamics 365 assessment that preceded it. No remediation record, acceptance or outcome measurement is cited or claimed.
Buyer problem and scope
| Item | What the statement of work states |
|---|---|
| Buyer | A professional association (client not named); signed by its President |
| 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 |
Unknowns, not stated in the document cited: 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.
Document (held privately):
| Document | Date |
|---|---|
| Statement of work, Dynamics 365 ongoing support and consulting, restating the assessment's findings (countersigned) | November 2021 |
Results and limitations
| Claim | Basis | Status |
|---|---|---|
| EPC Group assessed the association's Dynamics 365 system and reported findings | Cited in the countersigned statement of work | On file (EPC-reported; documents private) |
| The association contracted EPC Group for ongoing Dynamics 365 support and remediation | Countersigned statement of work, November 2021 | Contracted (EPC-reported) |
| Security model fixed, data model cleaned, apps delivered, or measured results | No document cited | Not claimed |
Provenance
- Source: the countersigned statement of work (November 2021), held privately. Engagement ID: EPC-2021-ANON-ASSOC-D365, an alias unrelated to the client's name.
- Anonymization: organization type only, under EPC Group's anonymized-case rule; the association's name, membership, location, staff names and commercial terms are not published.
- Not claimed: client endorsement, completion, or any measured result.
- Author: Errin O'Connor, Founder & Chief AI Architect, EPC Group, who signed the statement of work for EPC Group.
Revision history
- 2026-10-25: anonymized engagement summary published from the engagement's countersigned statement of work.
Related service
Dynamics 365 consulting · Talk to a senior architect
Author: Errin O'Connor, Founder & Chief AI Architect, EPC Group · Published: 2026-10-25.