
About
About Me
I’m Chris Munro, a Dynamics 365 and Power Platform technical lead with a background in mathematics and software development.
I specialise in making complex business systems understandable, supportable and safe to change.
Much of my experience is on the customer side of Dynamics 365: working with established and sometimes heavily customised systems, understanding how they really work, solving difficult problems, designing improvements and helping organisations build the capability to operate them effectively.
My perspective
A lot of Dynamics 365 content focuses on how to build something. I’m particularly interested in what happens around and after the build.
How do you understand a system you didn’t build? How do you safely change something with incomplete documentation? When should you use Power Automate rather than a plugin or an Azure service? How do you distinguish a simple configuration change from a high-risk change? How do you reduce dependency on individual experts or suppliers?
These are often less about knowing a particular product feature and more about technical judgement: understanding the problem, identifying dependencies, evaluating trade-offs and finding the simplest sustainable solution.
That’s the perspective I try to bring to the articles on this site.
What I work with
My core experience is with Dynamics 365 Customer Engagement and the wider Microsoft Power Platform, particularly Dynamics 365 Customer Service, Dataverse, Power Automate, Power Pages and model-driven applications.
My work also crosses into JavaScript, C#, Azure integration, Azure Data Factory, Azure DevOps, ALM, solution architecture and application support.
I’ve worked across the application lifecycle: discovery and requirements, solution design, development, testing, release, support, troubleshooting and continuous improvement.
Background
Before specialising in Dynamics 365, I worked in software development and scientific computing. I have a BSc in Mathematics, an MSc in Applied Numerical Computing and a PhD in Numerical Analysis.
That background still influences how I approach technology: understand the system, look for evidence, identify the underlying problem and test assumptions before making changes.
About this site
I use this site to write about three areas:
Technical Guides: practical Dynamics 365, Dataverse, Power Platform and Azure techniques.
Architecture & Decisions: choosing between approaches, understanding trade-offs and designing solutions that remain maintainable.
Running Dynamics: the less-discussed challenge of operating, supporting and improving established Dynamics 365 platforms in real organisations.
The common theme is understanding complex systems and making them work better.
https://www.linkedin.com/in/chrismvnro/



