About me
I’m Andy Schwarz, a Dynamics 365 and Power Platform Solution Architect with more than 15 years of experience designing, building, and improving business applications.
I started my career as a developer, which still shapes the way I work today. I like architecture that works not only on diagrams, but in production — maintainable, secure, scalable, and understandable for the teams that have to live with it.
Over the years, I’ve worked across complex Dynamics 365 and Power Platform environments, from solution architecture and integrations to Dataverse, ALM, Azure, governance, and technical delivery.
My role is often somewhere between architect, developer, and advisor: understanding the business problem, challenging unnecessary complexity, and turning it into a solution that can actually be built and operated.
I work independently and bring a hands-on technical perspective to projects — whether that means reviewing an existing architecture, designing a new platform, solving a difficult technical problem, or helping a team make the right architectural decisions.
If none of these fit, send me the situation: contact@dynamicspro.de.
I started working with Microsoft CRM in 2007, writing code and building custom solutions long before Power Platform became the platform it is today.
Since then, my role has evolved from developer and technical specialist to Solution Architect, leading the design and delivery of increasingly complex Dynamics 365 and Power Platform solutions.
That technical foundation still matters. I’m comfortable moving between the big picture and the implementation details — from architecture and integration patterns to Dataverse, C#, APIs, Azure services and deployment pipelines.
It also means I don’t design architecture in isolation. I want to understand how a solution will actually be built, deployed, operated and changed over time.
From developer to architect
Good architecture should make things simpler, not more complicated.
I prefer clear boundaries, standard capabilities where they make sense, and custom development where it creates real value. Every additional component, integration or dependency should have a reason to exist.
For me, architecture is also about what happens after go-live: maintainability, observability, security, deployment, performance and the ability to change the system safely.
And sometimes the best architectural decision is deciding not to build something.
How I think about architecture
Architecture
Solution design for Dynamics 365, Dataverse and Power Platform — with a focus on scalability, maintainability and clear technical boundaries.
Technical depth
A development background and hands-on experience with C#, APIs, integrations, Azure and the wider Microsoft ecosystem.
Delivery
Architecture that considers ALM, Azure DevOps, environments, automated deployments and operations from the beginning.
Independent perspective
Technology decisions based on what fits the problem — including challenging requirements, unnecessary customization and complexity when needed.
What I bring to a project
Technology has been a constant throughout my career, and I still enjoy exploring new ideas, tools and ways of building better systems.
But there is more to life than architecture diagrams and deployment pipelines.
Outside of work, I enjoy spending time with my family, cycling, travelling and occasionally going far too deep into whatever new technology has caught my attention.
Curiosity is probably the common thread — both professionally and personally.
Beyond the architecture
Have a complex Dynamics 365 or Power Platform challenge?
Tell me what you're dealing with. I'll tell you whether and how I can help.