What you’re seeing
- A runbook that ran fine for months suddenly fails with 'Authentication needed. Please call Connect-MgGraph'.
- The job connects with its managed identity, but every Graph call returns 403 or Authorization_RequestDenied.
- Runbook output shows errors about module versions, assemblies or methods not found.
- The failure started right after the Graph modules in the Automation account were updated.
- License assignments, user cleanups or reports the runbook handled have stopped happening.
Common causes
Every environment is different, but these are the causes our engineers find most often:
- The managed identity was never granted Microsoft Graph application permissions, or they were removed.
- Graph modules in the Automation account were updated unevenly, leaving mismatched versions.
- The runtime environment uses a PowerShell version that doesn't match the installed Graph modules.
- The system-assigned identity was disabled or recreated, so its old permissions no longer apply.
- The runbook mixes a user-assigned identity and a system-assigned identity and connects with the wrong one.
Why it matters
Runbooks are often trusted to handle repetitive but important tasks: removing licenses from leavers, disabling stale accounts, pulling security reports or syncing data. When one fails quietly, licenses get wasted, inactive accounts stay open and compliance reports go missing. Because nobody watches the job output, the failure may go unnoticed for weeks. Fixing it by giving the identity broad Graph permissions can create serious security exposure.
How AskTechGurus fixes it
Skip the trial and error. A certified engineer works on your actual system, finds the root cause, and fixes it properly.
Tell us what’s happening
Submit a ticket in about two minutes. Paste the error, describe what changed, and pick your tier. No charge to submit.
A certified engineer diagnoses it
A vetted, US-based systems engineer claims your ticket, usually within minutes during business hours, and investigates over a secure remote session you can watch and end at any time.
Fixed and verified with you
The engineer resolves the root cause and confirms with you that it’s working. You don’t just get a workaround, and you get a plain-English summary of what was wrong.
Pay only when it’s resolved
Fixed price from $99, invoiced only after you approve the fix. If it isn’t resolved, you don’t pay.
Frequently asked questions
Nothing changed in our runbook. Why did it break?
Changes to the Automation account's modules, runtime environment or identity can break a runbook without the code itself changing. Permission removals by another admin can do it too.
How much permission should the identity have?
Only what the runbook needs for its specific job. Broad permissions like full directory write access are risky if the account were ever misused.
Can AskTechGurus help with Azure Automation?
Yes. A certified US engineer reviews the runbook, modules and identity over a secure remote session. It starts at $99, and you pay only when it's resolved.