I help organizations and Dynamics implementation partners design, integrate and extend Microsoft Dynamics 365 Finance & Operations — from technical architecture and custom development to Azure integrations and enterprise delivery.
Most Dynamics 365 Finance & Operations projects are staffed for functional configuration. The moments that decide whether a program lands on time are technical: how the ERP talks to the rest of the landscape, how customizations are built so upgrades keep working, and what happens when volumes and integrations start to grow.
Bring in a senior technical specialist when the standard implementation approach is no longer enough.
Where I typically get involved
Six areas that together cover the technical side of a Dynamics 365 Finance & Operations program.
Technical architecture, extensions, customization and platform capabilities — built the way the platform expects, so updates and upgrades don't become projects of their own.
Robust integrations between Dynamics 365 Finance & Operations and external systems using asynchronous, API-based patterns instead of brittle point-to-point links.
Event-driven integration on Azure: Service Bus for decoupling, Functions for processing, API-based access where synchronous calls are the right choice.
Solution design, integration patterns, application architecture, scalability, security and the governance that keeps a landscape coherent over years.
Hands-on enterprise development in X++ and C#, from extensions and custom services to APIs and the components around them.
Technical design, architecture decisions, development standards and troubleshooting — working alongside functional consultants and implementation teams.
Dynamics 365 Finance & Operations rarely operates as an isolated system. It sits in the middle of warehousing, commerce, e-commerce, product data, reporting and whatever the business ran before. The architecture below is the reference shape I design towards — select a node to see its role.
Dynamics 365 Finance & Operations publishes events and exposes services; everything else consumes them through an Azure layer that absorbs failures, volume spikes and change. No system needs to know how another one works internally.
Select any node in the diagram to see how it fits.
The goal is not simply to make systems communicate. The goal is to create an integration landscape that remains reliable, scalable and maintainable as the business grows.
Engagements range from a few days of architecture review to a full technical lead role for the duration of an implementation.
Design and review of Dynamics 365 Finance & Operations technical architecture, integration landscapes and solution designs — before build starts, or as a second opinion on a design that already exists.
Design and implementation of integrations between Dynamics 365 Finance & Operations, Azure and external applications, including the operational side: monitoring, retries and error handling.
X++ extensions, APIs, custom services and technical customization that stays compatible with One Version updates.
Azure Functions, Service Bus and cloud-based integration architecture around Dynamics 365 Finance & Operations.
Independent technical advice for organizations and implementation partners — vendor-neutral, and written down so it can be acted on.
Investigating difficult technical issues, integration failures, performance problems and architectural bottlenecks.
Temporary technical leadership or specialist capacity during implementation, migration, upgrade or go-live phases.
A technical career that has followed the platform itself: from Dynamics AX 2009 and AX 2012 to the current cloud versions of Dynamics 365 Finance & Operations.
I started as a Dynamics AX developer and grew into the technical architect role over successive versions of the product. That history matters on today's projects: many organizations moving to Dynamics 365 Finance & Operations are carrying customizations, interfaces and habits from AX 2009 or AX 2012, and knowing where those came from makes it far easier to decide what to keep, what to rebuild and what to retire.
Across implementations, upgrades and support engagements I have been responsible for technical design, custom development, integration architecture and the technical side of go-lives, working for end customers as well as Microsoft Dynamics implementation partners.
Technical architecture and integration design for large-scale, multi-entity Dynamics 365 Finance & Operations implementations, including the surrounding landscape that has to keep running through a phased go-live.
Moving organizations from AX 2009 and AX 2012 to Dynamics 365 Finance & Operations: code assessment, re-implementation of customizations as extensions, data migration and cut-over.
Replacing point-to-point interfaces with event-driven Azure integrations, and designing high-volume processing patterns that scale with transaction volumes rather than against them.
Performance problems, integration failures and difficult technical issues on live environments, for IT departments and implementation partners.
Client names, industries and figures are confidential and can be discussed in a conversation.
The tools I work with day to day. Depth is in Dynamics 365 Finance & Operations and the Azure integration services around it.
I'm Jack Dekker, a Microsoft Dynamics professional specializing in the technical side of Dynamics 365 Finance & Operations: architecture, development and integration. I've worked inside implementation programs long enough to know that the best design is the one the team can actually build, run and change later.
I work directly with end customers, with Microsoft Dynamics implementation partners who need senior technical capacity, and with IT departments and project teams that own the platform after go-live.
The difference between a senior architect and a capable developer shows up in decisions, not lines of code.
Solutions are designed around long-term maintainability, not just around making an integration work today.
A thorough understanding of the Finance & Operations platform, its extension model and its limits.
Experience across Dynamics 365 Finance & Operations, Azure and Power Platform, and how they should divide the work between them.
No product or vendor agenda. Advice is about what fits your landscape.
Able to move from architecture diagrams into actual X++, C# and Azure implementation.
Whether you need architectural guidance, integration expertise or additional technical capacity, let's discuss what you're trying to achieve.
Describe the project or the problem in a few lines by email, or call to discuss directly.