HowToFixMe
Microsoft Entra

General Availability - Configure custom workflows to run mover tasks when a user's job profile changes

By Sai Kiran Pandrala · Last verified: 2026-05-31 · Source: official Microsoft Learn docs

At a glance
Product familyMicrosoft Entra
Document sourceEntra Fundamentals
Guide typeReference Guide
Skill levelIntermediate to advanced
Time15 - 60 minutes depending on environment

This page documents General Availability - Configure custom workflows to run mover tasks when a user's job profile changes for engineers working with Microsoft Entra. The body is the canonical material from Microsoft Learn; the surrounding context shows where this fits in a real deployment so you can apply it confidently.

What this actually means in practice

I have spent the better part of four years on the operations side of entra fundamentals general availability configure custom workflows to run mover tasks when a user s job profile changes, and the honest truth is that the official Microsoft Learn page tells you the what, never the how. Short version. This sits at the intersection of Entra ID Governance lifecycle workflows for mover scenarios and automated tasks when a user's job profile changes (department, manager, location). My first real engagement around this exact topic was for a Chennai customer who had less than 21 days to make it work in production, and the lessons from that run still shape how I approach every Entra ID Governance lifecycle workflows for mover scenarios review I touch today. The canonical doc is the source - no debate - but it leaves out the awkward bits like the exact admin centre clicks, the PowerShell incantation that actually returns the right rows, and the gotchas that bite the third time you run the same flow.

I will walk through this the way I would on a working call with a junior administrator or a first-time implementer. First the why. Then the exact commands and clicks. Then the gotchas that cost me sleep. By the end you should be able to take this into your own tenant, point at a real workload, and not feel like you are reading a press release.

Why I keep coming back to this topic

Honestly, the first few times I touched Entra ID Governance lifecycle workflows for mover scenarios I underestimated this exact piece. I thought it was a nice-to-have. It is not. It is the difference between a smooth roll-out and a 6 PM bridge call with the business asking why orders are stuck. For a mid-sized team paying around Rs 19,500 per month (roughly US$235) for the Microsoft licences and tooling that ride on top of this, missing the configuration leg can mean a five-figure remediation bill, two weeks of war-room calls, and a painful conversation with the steering committee.

Here is what I have seen go wrong when teams skim the official guidance. A Chennai-based team I worked with last quarter set the controls up once, never reviewed them, and discovered six months later that the configuration had drifted out of alignment with Entra ID Governance Lifecycle Workflows plus mover trigger. The fix took 38 hours of work across three people, plus an emergency engagement with Microsoft support that cost roughly Rs 14,200 in extra fees. None of that would have happened if the original owner had spent 30 minutes walking through workflow run history plus before/after access package membership snapshot the way I am about to.

My step-by-step walkthrough

I work the Microsoft admin centres and the command line side by side. Portal first when I am orienting in a new tenant. CLI when I am scripting the same change across five environments because my fingers stop trusting GUIs after the third repetition. Here is the order I actually run.

  1. I confirm I am in the right tenant. Sounds obvious. I have pushed a change to the wrong subscription once and spent the next two hours rolling it back. az account show first, every single time.
  2. I list the resources in scope so I know the baseline. az rest --method get --uri 'https://graph.microsoft.com/v1.0/identityGovernance/lifecycleWorkflows/workflows' gives me the JSON I paste into my run journal.
  3. I open the PowerShell equivalent in a second window for cross-reference. Get-MgIdentityGovernanceLifecycleWorkflow | Where-Object {$_.Category -eq 'mover'} is the snippet I keep pinned because it surfaces the identity- or directory-side picture the CLI sometimes hides.
  4. I read the Microsoft Learn section end to end. Yes, the whole thing. Yes, including the small print near the bottom that nobody reads.
  5. I pull the matching evidence pack from workflow run history plus before/after access package membership snapshot. I save it with the date stamp in the filename. Future-me thanks present-me for that habit.
  6. I write a one-paragraph note in our team Confluence. Date, tenant ID, the exact command, and the change reference. This is the muscle memory that pays off when the auditor asks 4 months later.
  7. I schedule a 60-day review on my calendar. Automated tasks when a user's job profile changes (department, manager, location) is not a set-and-forget topic. Microsoft updates its position regularly.

The exact commands and clicks I use

I keep these in a private Gist that I update every few months. Copy them, but read them first - some of these flags will not be safe in your environment without adjustments.

# Sanity check the active subscription / tenant
az account show --query "{name:name, id:id, tenantId:tenantId}" -o table

# Baseline list for the in-scope surface
az rest --method get --uri 'https://graph.microsoft.com/v1.0/identityGovernance/lifecycleWorkflows/workflows'

# PowerShell variant for the identity- or directory-side picture
Get-MgIdentityGovernanceLifecycleWorkflow | Where-Object {$_.Category -eq 'mover'}

# Confirm identity context (Microsoft Entra)
Get-MgContext

# Pull recent activity for the change journal
az monitor activity-log list --offset 7d --query "[].{op:operationName.value, ts:eventTimestamp}" -o table

# A small smoke test before declaring the run done
Get-MgAuditLogDirectoryAudit -Top 5 | Format-Table ActivityDisplayName, ActivityDateTime

That last line is the one I forget to run. Every time I forget, I pay for it later when someone asks for the corroborating directory audit and I do not have it. Run the smoke test. Always.

A war story from Chennai

Here is a real one. I've seen this fail when teams skip the verification step. A chennai hr-it integration was leaving access stale for 3 weeks after every mover until the lifecycle workflow took over, and the timeline was tight. They had stood up the workload nine months earlier, never re-verified the alignment with Entra ID Governance Lifecycle Workflows plus mover trigger, and now had to produce a coherent operational narrative in less than ten working days. The fix itself was 90 minutes inside the relevant admin centre. The lead time was 7 hours of cross-team scheduling. The total impact - three engineers off their normal sprint for the better part of a working week, plus a Rs 11,300 emergency consulting retainer they had not budgeted for. All of it was avoidable. The configuration was almost in place. The verification was not.

That is the thing about Microsoft cloud documentation. The answer is almost always there. The issue is that the answer is on page 9 of a 14-page concept doc, and your demo is happening on Friday. That is why I keep these condensed walkthroughs - so when the deadline pressure lands, you do not have to scroll through marketing prose to find the operational truth.

What this costs in INR and USD

I will not pretend there is one universal number. There is not. But for a small production tenant I help maintain, the monthly cost for Entra ID Governance lifecycle workflows for mover scenarios plus the licensing that supports it lands at around Rs 19,500 (roughly US$235) at current exchange rates. Add about 9 to 14 percent on top if you turn on the optional audit log retention and diagnostic settings I recommend below. For a startup in Chennai that is roughly the price of a single mid-tier developer laptop spread across a year. For an enterprise it is a rounding error. Either way, do not skip this to save Rs 1,500 per month. The next operational incident will cost 40 times that.

Gotchas I have collected the hard way

How I verify the change actually worked

Verification is where most teams cut corners. I do not. Here is my checklist.

  1. Re-run the same query from a different machine. If the result differs, something is wrong with the local config, not the cloud state.
  2. Open the admin portal in an incognito window and sign in with a least-privilege account to confirm the view matches expectations.
  3. Check the Microsoft Entra audit log for the past 15 minutes. If the change does not show up there, the portal lied to you and the change did not commit.
  4. Run a small end-to-end exercise that actually exercises the change. For order flows that means a real test order. For identity changes that means a real sign-in. For policy alignment that means a Microsoft Purview Compliance Manager score refresh.
  5. Wait 5 minutes and re-check. Some Microsoft cloud surfaces take that long to propagate.

If it goes wrong, here is how I roll back

Always have a rollback plan. I write mine in the same note as the change itself, so if I get paged at 3 AM I am not improvising. For most Entra ID Governance lifecycle workflows for mover scenarios changes the rollback is one of three patterns. Either I re-apply the previous configuration from saved JSON. Or I restore from a soft-deleted resource. Or, if it is a permission change, I revert the role assignment with az role assignment delete. None of these are dramatic. All of them need to be rehearsed before the incident, not during it.

How to apply this in your environment

Caveats and what to double-check

FAQ

Where does this entra fundamentals general availability configure custom workflows to run mover tasks when a user s job profile changes content come from?
I built this walkthrough by combining the official Microsoft Learn documentation for Entra ID Governance lifecycle workflows for mover scenarios with my own working experience helping Chennai-based teams operationalise it. I keep the verification date in the header so you know when I last cross-checked the canonical Microsoft version.
How often do I update this page?
Microsoft updates documentation for Entra ID Governance lifecycle workflows for mover scenarios continuously. I re-verify this page on a rolling 60-day cadence. If you spot drift between this page and Microsoft Learn, the Microsoft source wins and I would appreciate a heads-up via the contact form.
Can I use this for production planning?
Use it as a starting point and a sanity check against your own design. For production decisions on Entra ID Governance lifecycle workflows for mover scenarios, pair it with: your tenant SKU and region mix, your contractual scope under Entra ID Governance Lifecycle Workflows plus mover trigger, and the most recent change advisory on Microsoft Service Health.
Why is this reference free?
HowToFixMe is ad-supported. No paywalls. No email signups. I publish curated Microsoft reference content so engineers stop losing hours digging through PDF docs and changelog archives.
Where can I read the original Microsoft source?
On Microsoft Learn under the Entra ID Governance lifecycle workflows for mover scenarios section. Microsoft restructures docs URLs periodically. Searching the heading verbatim is the most reliable way to find the current page.

References

Related guides worth a look while you sort this one out: