JOB DESCRIPTION:
- 10+ years of MS Dynamics experience
- Experience leading from an architecture standpoint, and is a strong enough technical resource to still be hands on with code
- Guide the client and project team, communicate clearly, and provide day-to-day technical leadership and oversight
- Support clients across the Microsoft Dynamics 365 CE platform including the various additional license modules. That said, historical projects show a clear trend in the commonality of Microsoft Dynamics CE modules utilized at clients. Below is an ordered list of the most to least common modules.
- Customer Service
- Sales
- Customer Insights
- Contact Center
- Field Service
- Most clients have some need for a public facing portal component and also require some amount of business logic or industry customization around their specific workflows, as such Microsoft Power Pages and Microsoft Power Automate are utilized on the majority of projects.
KEY PROJECTS:
- The organization utilizes Salesforce along with a public-facing portal to support
projects cultivated by individuals around the world. As architects and developers on this initiative, the objective is to bring functionality into an existing and actively used Dynamics environment. The approach maintains established architectural patterns, including the use of Power Automate and process-driven automation.
Key considerations include:
• Ensuring data integrity across business units
• Maintaining strict security boundaries through roles and security architecture
• Aligning with pre-existing solution patterns to minimize disruption
• Preserving scalability and maintainability within the broader enterprise ecosystem
2. The organization utilizes Dynamics across multiple teams and business units. Over time,early implementation decisions and organic growth resulted in:
• Deprecated fields and legacy functionality
• Accumulated technical debt
• Entrenched third-party solutions that could not be removed through standard
methods
• Inconsistent Application Lifecycle Management (ALM) practices
Previously, managed solutions were used selectively, while most customizations remained
unmanaged. This caused deployment conflicts due to "last change wins” behavior and
introduced instability across environments.
To address this, a full modernization effort was executed:
• Removal of deeply embedded third-party solution components
• Creation of a clean development environment
Selective extraction and migration of necessary assets
• Establishment of a strict managed-solution ALM model
• Migration across Development, Test, UAT, and Production environments as part of
go-live
As architects and developers, this required executing a large-scale table-to-table
migration across hundreds of tables in multiple environments while simultaneously
resolving technical debt.
This included:
• Removing hard-coded static values embedded in Flows and processes
• Refactoring automation for ALM compliance
• Standardizing solution deployment strategy
• Establishing a sustainable managed-solution-first model
The result was a significantly more stable, governable, and scalable platform foundation.
3. This engagement represents a long-running enterprise support model focused on continuous improvement rather than a fixed-scope implementation.
As organizational needs evolve, the team:
• Leverages new platform capabilities
• Improves and optimizes existing processes
• Onboards new teams and business units
• Designs and deploys new functionality to support operational growth
There is no single functionality target. Instead, the work is driven by a rolling backlog of
enhancements and strategic improvements.
Architecturally, the team prioritizes:
• Clear, maintainable solution patterns
• Alignment with existing implementation approaches
• Lowest total cost of ownership
• Knowledge transfer and sustainability for internal support teams
Design decisions intentionally favor maintainability. For example:
If functionality can be achieved via Power Automate rather than a custom plugin,
Power Automate is preferred to enable easier internal ownership.
• If a field requirement can be enforced through an existing business rule pattern
rather than JavaScript, the business rule approach is used to maintain consistency.
The guiding principle is long-term platform health and internal team empowerment rather
than over-engineering solutions.
