Share
ReportHello everyone,
I’m seeing inconsistent behavior when updating the user password policy via Microsoft Graph from Power Automate and would like to confirm if this is expected or supported.
Scenario
Using HTTP with Microsoft Entra ID (preauthorized) in Power Automate, I call:
PATCH /v1.0/users/{userPrincipalName}
Body:
{
"passwordProfile": {
"forceChangePasswordNextSignIn": false
}
}Observed behavior
- Immediately after creating a user, the request sometimes succeeds and returns:
{"statusCode":204,...}
- Re‑running the same request minutes later (no changes to flow, connector, permissions, or payload) consistently returns:
No configuration changes were made between executions.
Can Microsoft confirm whether updating passwordProfile.forceChangePasswordNextSignIn via Power Automate / Graph is:
Best‑effort only?
Explicitly unsupported for automation scenarios?
Thanks in advance for any clarification.
Categories:
I have the same question (0)
All responses (
Answers (
943
