Dynamics 365 CE consultant and contractor in Melbourne

Ways to work together

Contract developer or tech lead

Senior hands on your existing Dynamics 365 team, on a day rate, for as long as the work needs. Plugins in C#, model-driven apps, Power Automate, code reviews and mentoring juniors along the way. Direct or through your recruiter.

Integrations

Dynamics 365 connected to finance, ERP and payment systems through Azure Functions, Service Bus and web APIs. Most recently Oracle Financials. You don't need a second specialist for the Azure half. I do both sides. More on Dynamics 365 integrations.

ALM and deployments

Solutions, environments and Azure DevOps pipelines set up so releases are repeatable and boring, which is how they should be. Managed solutions through a pipeline, a short checklist for what each environment needs, and no manual changes in production.

Health check

Five days reviewing your architecture, release process, performance, security roles and licensing. You get a written report and a fix plan in priority order. Useful if you've inherited a build, your partner has moved on, or releases have started to feel risky. What the health check covers.

Power Pages

Portals for customers or members on the same Dataverse data your staff use. More on Power Pages.

Where Dynamics 365 projects usually get stuck

After this long on the platform, the same handful of problems come up again and again. None of them are exotic. They just get left until they hurt.

• Unmanaged changes in production. Someone fixed something directly in prod a year ago. Now there's an active layer sitting on top of every deployment and nobody knows why a field won't change.
• Releases that pass test and fail in production. Usually connection references pointing at the wrong connection, or an environment variable that never got a value in the new environment. The flows import fine and then don't run.
• External calls inside plugins. A synchronous plugin calling a finance system works in dev and times out on a busy day. That logic belongs in Azure, with retries and logging.
• Plugins that run on every save. Update steps registered with no filtering attributes, so every change to a record runs code that has nothing to do. Slow saves, slow imports, and the odd infinite loop error. How to fix plugin filtering attributes.
• Security roles grown by copy and paste. A pile of roles that are almost the same, and nobody wants to touch them in case someone loses access.
• Integrations nobody watches. Errors only surface when a user notices missing data. A failed call should show up in one place with the payload attached.

The fix is rarely a rebuild. It's mostly patience and finding the actual cause, then putting something in place so it doesn't come back next release.

Recent Dynamics 365 work

Client names left out on purpose. Happy to go through any of these on a call.

• Large public-sector organisation. Integrated Dynamics 365 with Oracle Financials and built a faster payment process on top of it.
• National member organisation. Ongoing Dynamics 365 CE development: plugins, forms, automation and deployment tooling.
• Emergency services organisation. Dynamics 365 and Power Platform delivery inside an established internal team.
• National logistics company. Proof of concept for sustainability reporting, with Databricks feeding Microsoft Sustainability Manager.

Why a one-person consultancy

Accurate Software Solutions is my company. When you hire it you get me, not a junior learning on your project, and not a different person every sprint. I build my own tooling to make deployments faster and safer, and I write things down so the next person isn't guessing.