Across a 60-day observation window, we recorded 117 market signals in the Dynamics 365 CRM and Power Platform stream, and those signals attached to 117 distinct company records. One signal per company record. That ratio is the most useful thing in the dataset, and it is the part most people skim past.
Before going further, a note on what this evidence is. These are recorded market-intelligence signals, captured on last seen or date found, not on posting date. They include historical, inferred and search-page evidence. A signal is not a verified live advertisement, and the sample should not be read as a monthly hiring total or as 117 independent hiring decisions. What it does give is a shape, and the shape is worth planning around.
Breadth, not depth
When signals cluster heavily on a handful of company records, you are usually looking at a small number of large programmes doing volume resourcing. That is not what this window shows. The spread is flat and wide, which is more consistent with many organisations each looking for one or two people than with a few building squads of eight.
For a hiring manager, the practical consequence is competition for singletons. You are not competing with three big programmes for a pool of thirty. You are competing with a long list of employers who each want the same profile: one capable Power Platform or Customer Engagement person who can work without a scaffolding of seniors around them. That profile is the scarcest one in this stream, and it is the one that moves fastest when it does become available.
The role titles are converging
Titles recorded in this window include Automation Specialist, Automation, Power Platform Engineer, Power Platform Developer, AI Engineer and Azure. Technologies named across the records include Power Platform, Power Automate, Power Apps, Customer Engagement, Dynamics 365 and Dataverse.
Two things stand out. First, “Automation” appears both as a specialist title and as a loose descriptor, which tells you the role definition is still being worked out inside the organisations writing it. Second, AI Engineer and Azure sit in the same stream as Power Apps and Dataverse. Our reading is that automation work and AI work are being briefed together, sometimes into a single headcount.
That is an observation about how roles are being written, not proof that organisations have an AI programme running. But if you are about to write a brief, assume candidates are reading a market where both are being asked for. If your role is pure Power Apps and Power Automate with no AI component, say so plainly rather than adding fashionable scope you cannot support. Over-briefed roles attract applications and lose offers.
Where the records sit
Locations recorded include Australia broadly, New South Wales, Sydney and Auckland. Sydney and New South Wales presence is unsurprising. The Auckland appearance matters more than its share of the sample suggests, because New Zealand based Dynamics and Power Platform capability is frequently briefed into Australian programmes and because trans-Tasman candidates often appear in both markets at once. If you are running a search out of Melbourne or Brisbane and your shortlist is thin, the New Zealand market is worth including before you widen your salary band.
Financial services and the consulting bench
Industries named in the records are Financial Services, IT Services, IT Consulting and Technology. The consulting weighting is the one to plan around. When IT Services and IT Consulting firms are visible in a stream, they are typically building or replenishing bench capability, and they hire the same people you want, usually faster and with a project pipeline to sell against.
Financial services records bring a different pressure. Dataverse and Customer Engagement work inside a regulated environment carries security clearance, data residency and change-control requirements that lengthen onboarding and narrow the pool. If you sit in that sector, your constraint is rarely the technical shortlist. It is the gap between offer and first productive day.
Why a permanent CE hire tells you more than it looks like
A direct permanent Dynamics 365 CRM hire is a stronger indicator than a contract one. It suggests an internal Customer Engagement environment already exists and that there is a development roadmap being funded beyond go-live. Organisations do not take on permanent CE headcount to run a one-off implementation. They take it on to own the thing afterwards.
Treat that as interpretation rather than fact for any individual record. We cannot confirm project stage from a signal, and we would not ask you to act as though we could. But as a pattern across a stream, permanent CE demand and Power Platform automation demand appearing together points at organisations moving from delivery to sustained product ownership. That shift changes who you should hire. The person who configures a greenfield build is not always the person who maintains, extends and governs it for three years.
What we would recommend
- Decide whether you are buying build or buying ownership. Write the brief for one. Candidates can tell the difference and will self-select out of a confused one.
- Separate the AI scope from the automation scope. If you want both in a single hire, fund it as a senior role and say what the AI work actually is.
- Compress your process. In a market where demand is spread across many employers each seeking one or two people, a four-stage process over five weeks is the main reason offers fail.
- Price against consulting firms, not against your internal grade. If IT Services and IT Consulting employers are in the same pool, that is your benchmark whether you like it or not.
- Plan governance before the second Power Platform hire, not after the tenth app. Our guide on preparing for scalable Power Platform automation covers how to set that up before sprawl makes it expensive, and if your reporting layer is going the same way, the Power BI Centre of Excellence guide runs the same argument for data.
How to resource this
Most of the organisations in this stream are hiring one person into an environment that already has opinions about how things should be done. That is a matching problem more than a sourcing problem. The shortlist needs to be built against your Dataverse model, your integration pattern and your appetite for citizen development, not against a generic title.
Our Dynamics 365 CRM and Power Platform recruitment practice is built for exactly that, across Australia and New Zealand, permanent and contract. If you want to see who is genuinely available before you commit to a process, the Talent Portal is the quickest way to form a view.
If you are scoping a programme now and want a read on what your role will realistically attract, get in touch and we will talk it through before you advertise.