What I do
I've spent years working inside live Dynamics 365 Customer Engagement implementations — not just studying them. That means designing security models that actually hold up under real org charts, writing plugins that survive production load, wiring Power Automate into Dataverse without creating a mess of unmaintainable flows, and explaining all of it clearly enough that the next developer (or the client) doesn't get lost.
VitalDynamics365 is where I write that experience down. The goal is simple: content that reflects how Dynamics 365 CE projects actually run, not a rehash of documentation. Every tutorial and interview answer on this site is written from scratch, based on real scenarios I've worked through.
How I think about the work
Most of my career has been on the consulting side of Dynamics 365 CE: someone else owns the product, I make it work. But I've never been satisfied just configuring what's asked for. Give me a business problem and my instinct is to ask what the actual end-to-end solution should look like, then build that — not just the ticket in front of me.
That's the entrepreneurial streak underneath the consulting work. A few things I keep coming back to:
- Build the whole thing, not just your piece. Understanding the full flow — data model, security, automation, and the actual person using the screen — produces better decisions than optimizing one layer in isolation.
- Default to building, not just configuring. The platform gives you tables, forms, and workflows out of the box. The interesting work starts when the out-of-the-box answer isn't quite right and you have to design something that is.
- Question the standard approach before repeating it. "That's how it's usually done" is a starting point for a conversation, not a reason on its own. Some of the better solutions I've shipped came from asking why the common pattern didn't quite fit this case.
- Ship something real, then improve it. A working v1 that real people use teaches you more in a week than a perfect design teaches you in a month.
Products & things I've built
Outside client work, I build complete applications on Dynamics 365 CE and the Power Platform, end to end — data model through to the interface someone actually uses. Two examples:
Shuttle Court Booking App
A model-driven app for booking and managing shuttle court time slots — built from requirements through to a working scheduling system. Full case study →
Employee Expense Management System
A model-driven app covering expense submission, multi-level manager approvals, policy compliance, and reimbursement tracking — designed to replace a manual, spreadsheet-driven process.
This site is the same instinct pointed at content instead of a data model: a full, structured step-by-step learning path built from scratch, not assembled from a template.
Areas of focus
- Core platform configuration — security roles, business units, teams, sharing, and solution architecture.
- Server-side extensibility — plugins, custom workflow activities, and integration logic.
- Web API & Dataverse — querying, updating, and integrating Dataverse with external systems.
- Power Platform — Power Apps (canvas and model-driven), Power Automate, and Power BI reporting on top of Dataverse.
- Interview & career prep — helping developers and consultants prepare for real D365 CE interviews with practical, scenario-based questions.
Why this site exists
A lot of Dynamics 365 learning material online is either outdated, overly generic, or written to sell a course. This site is neither. It's a working reference — the kind of explanation I wish existed when I was learning the platform, and the kind of interview prep that reflects what actually gets asked in real interviews rather than a recycled question list.