Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams: 2026

how to assign an approval to a SharePoint Person column value with the Claims property

Q: How long does how to assign an approval to a sharepoint person column value with the claims property typically take on Power Automate Approvals — Modern Approvals, Adaptive Cards & Teams — 2026?

For most Power Automate Approvals — Modern Approvals, Adaptive Cards & Teams — 2026 workflows, 5 to 30 minutes including verification. Large workspace migrations, anything touching API token rotation or SSO cutover, or cross-region exports can stretch to half a day because you have to wait for re-share notifications, OAuth re-consent, or coordinated team windows.

Q: Is there a rollback path?

Yes for most Power Automate Approvals — Modern Approvals, Adaptive Cards & Teams — 2026 changes. Snapshot the platform version, screenshot the workspace settings, export the audit log, and write down the API token before any change. A few operations are one-way (deleted scenarios past the trash window, irreversible plan downgrades, permanently revoked connectors). Check the in-product help for the specific operation before you commit.

Q: Will this affect other teammates in the Power Automate Approvals — Modern Approvals, Adaptive Cards & Teams — 2026 workspace?

Often yes. Power Automate Approvals — Modern Approvals, Adaptive Cards & Teams — 2026 workspaces share sharing policies, plan quotas, member rosters, and connected-app permissions across the whole tenant (one connected-app grant holds permissions for many integrations, one sharing policy covers all scenarios, one plan tier covers all members). Use the Power Automate Approvals — Modern Approvals, Adaptive Cards & Teams — 2026 workspace audit log and the connected-apps list to enumerate dependencies before changing a shared component.

By Sai Kiran Pandrala · Last verified: 2026-05-31 · Source: community forums (r/nocode, r/automation, r/GoogleAppsScript, r/PowerAutomate, r/n8n, r/make, r/ClaudeAI), vendor status pages and changelogs, vendor help centers, in-product help

At a glance

Platform	Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams. 2026
Category	Automation Tools
Guide type	Procedure
Skill level	Beginner to intermediate
Time	5 - 30 minutes including verification

Automation engineers and no-code builders running Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026 hit how to assign an approval to a SharePoint Person column value with the Claims property often enough that there is a stable fix pattern. Here's the order I'd run things as an experienced day-to-day operator would run it during a real build session, not a hypothetical lab. My standard pattern for this is documented below end to end.

What how to assign an approval to a sharepoint person column value with the claims property actually involves on Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026

Real-world context. Last time I walked through this on a real machine, the budget shook out to ~Rs 500 to Rs 2,500 INR per month for premium tiers (around $6 to $30 USD/month). Plan for ~20 minutes to wire up actually at the keyboard, and ~1 to 2 hours to test end-to-end once you factor in the back-and-forth. Keep an API key, the workflow JSON, and a test payload within arm’s reach before you start, stopping mid-step to hunt for them is how a 30-minute job turns into an afternoon.

On Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026 in my experience the most useful first-pass tools are Browser DevTools on flow.microsoft.com/manage to inspect approval payload, Power Automate run history > Approvals action Outputs pane, Power Automate Action center (flow.microsoft.com/manage/approvals). Each of these surfaces a different layer of the failure - keep at least the first one in your personal notes so the next time this happens you do not start cold.

For verification on Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026, the methods that survive contact with a real Monday-morning workload are send a test card via Adaptive Cards Designer Preview mode and validate JSON before pasting and set Body of response option to comma-separated 'Approve,Reject,Need info' and confirm three buttons render. Anything less than that and you are shipping on vibes.

Authoritative sources for Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026 that I cross-reference before committing to a fix: learn.microsoft.com/en-us/power-automate/get-started-approvals, learn.microsoft.com/en-us/power-automate/approvals-known-issues, learn.microsoft.com/en-us/power-automate/overview-adaptive-cards. Marketing blog posts and Medium writeups are signal, not ground truth.

The rest of this page is the structured fix path. Start with diagnose, then remediation, then the automation options so you do not have to do this by hand the next time it surfaces. Verify and safety sections at the end are the discipline that keeps the fix from regressing the next time you open the platform.

Diagnose first, fix second

Second pass: open the Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026 workspace admin or settings panel and look at the audit log or activity feed for the failing window. Most modern automation platforms surface an audit trail (the platform's execution history, the connector run log, the integration activity feed). The audit log tells you whether the failure was your action, a teammate changing a connected account in the same minute, or a platform-side rollout. Many "permission denied" or "connection not found" reports trace to a credential-level change pushed in the same admin panel in the previous hour - the audit trail makes that obvious without guesswork.

Fourth: open the vendor status page for Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026 and the connector's upstream status pages for the failing window. The smoking guns are an open incident touching the exact service area you are using, a recent post-mortem covering the same symptom, or a Trust Center advisory on a partial outage. Cross-reference the timestamp of your first failed run against the incident start time - if they match within 5 minutes, stop debugging your own setup and subscribe to the incident updates. Many vendors lag the status page behind the actual incident by 10 to 30 minutes; if Twitter and Reddit are both lit up but the status page is green, trust the crowd and treat it as upstream until proven otherwise.

Fifth: replay the failing run against a second account or a second connector on the same Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026 workspace. The point is to isolate "my credentials" from "my account" from "the whole workspace." If a teammate's identical scenario works but yours does not, the failure is local cache or a stale OAuth grant. If the same scenario fails for everyone in the same workspace, you have a tenant-wide config change or a vendor-side incident. Pin the platform version explicitly while you do this: the platform's About panel, the build hash in the footer, or the engine version returned by a diagnostic call. The version pin is what isolates "their rollout broke me" from "my client is out of date."

Field notes from real Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026 incidents

Before I mark an Power Automate Approvals ticket resolved I always run `go to flow.microsoft.com > Action items > Approvals and confirm the request appears` once more and screenshot the output, that habit has caught at least three silent regressions for me. My go-to verification step is `send a test card via Adaptive Cards Designer Preview mode and validate JSON before pasting`; I learned the hard way that the Power Automate Approvals UI will happily lie about whether a flow really ran.

On any Microsoft problem in Power Automate Approvals, the first three questions I ask are: which runtime, which tenant, which trigger source. Defaults shift quietly between platform updates. Whenever a teammate pings me about an Power Automate Approvals automation misbehaving, I make them open Adaptive Cards Designer (adaptivecards.io/designer) before we even look at the symptom they reported.

Tools I actually reach for

For most Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026 stalls I start with Microsoft Teams Approvals app activity tab, fall back to Adaptive Cards Designer (adaptivecards.io/designer), Microsoft 365 admin center > Message center for actionable message policy, Power Automate Action center (flow.microsoft.com/manage/approvals) when Microsoft Teams Approvals app activity tab cannot surface the answer, and keep Browser DevTools on flow.microsoft.com/manage to inspect approval payload handy for the cases where neither answers. That ordering is not academic - it matches the layers of the failure as they tend to surface, so the cheapest signal lands first and the heavier tooling only comes out when the simpler answer does not hold up. My muscle-memory shortcut for this is to run the first tool while the failing screen is still open, not after I have already restarted the platform.

Verification I run before I call it fixed

Before I mark a Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026 stall resolved, the verification loop below is what I actually run. Each step proves a different layer is green, and the order matters - the cheaper checks gate the more expensive ones.

send a test card via Adaptive Cards Designer Preview mode and validate JSON before pasting

If that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.

set Body of response option to comma-separated 'Approve,Reject,Need info' and confirm three buttons render

If that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.

open Teams > Approvals app and confirm the same request shows under Received

Only when every line above runs clean do I close the loop and update my notes with the timestamps.

Where I check first when the docs disagree

When two sources contradict each other on a Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026 detail, the disambiguation order I lean on is stable. I usually check learn.microsoft.com/en-us/power-automate/approvals-known-issues for the ground-truth view on this part of Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026. I usually check learn.microsoft.com/en-us/power-automate/overview-adaptive-cards for the ground-truth view on this part of Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026. I usually check adaptivecards.io/explorer for the ground-truth view on this part of Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026. Marketing blog posts and Medium writeups are signal, not ground truth, and I treat them as such until the references above either confirm or contradict the claim.

Solution-focused remediation path

Start by sorting the Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026 failure into one of three buckets, because roughly 80% of cases fall here. Bucket one is auth / account drift: you are signed into the wrong account, the SSO session expired, MFA tripped, or the workspace owner changed your role. Bucket two is sync / cache drift: the platform has a stale view of the connector, the offline cache disagrees with the cloud, or a recent edit has not synced yet. Bucket three is plan / quota / sharing: the action requires a higher plan tier, the workspace hit an operation or task cap, or the connector you are trying to use was revoked. Pick the bucket first, then act. Before you act, capture a baseline screenshot of the failing run plus the run id so you can prove whether the fix actually moved the needle. Decision point: if the failure is intermittent and you are on a paid Business / Enterprise plan, open the in-product support chat first - vendor support on a paid tenant beats hours of speculative debugging on cost and on liability if the failure recurs.

Before any destructive step on a Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026 workspace, slow down and stage rollback. Snapshot the current platform version, the current workspace settings (Settings -> screenshot every tab), the connected-apps list, the current sharing policy, and the current member list to a notes entry first. Capture the failing screenshot, the Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026 incident id if any, and the timestamp window. Photograph (screenshot) the workspace state from two angles: the scenario or script that is failing, and the workspace settings page that controls the relevant policy. Then do the destructive step (revoke a connector, change a sharing default, remove a member, delete a connected app) inside a test workspace or a test scenario first, never the whole workspace. Capture the platform version, the API permissions, the connected-app list, the workspace member roster, and the relevant integration log snapshot to your notes before the destructive step. Decision point: if you are on a paid plan, the cheapest correct path is almost always to open the in-product support chat in parallel with the rollback - the support rep can confirm whether a vendor-side rollout is responsible while you are still staging the change, which avoids a needless workspace edit if the fix is server-side.

When the Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026 fault tracks to integration failures, automation delays, or webhook drops from the trigger source (the trigger source, the connector, the upstream provider), treat the integration plane as suspect. Open the integration log in the connected service (the trigger source's webhook log, the platform's connector run history) and read the response status the Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026 endpoint actually returned - most "scenario not firing" reports are actually "webhook firing but the connector failed and the platform backed off." Verify the connected account is still authorized (the OAuth grant in Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026 is not silently revoked) and that the trigger event is what you think it is. Decision point: if the trigger is firing but Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026 is rate-limiting it, throttle the scenario (bump the polling interval, add a sleep module, enable batch mode) and re-run. Verify the connected workspace is the right workspace - a common foot-gun is the personal workspace being authorized while the work workspace holds the data.

Automate this fix so you do not do it twice

Fleet API token + OAuth grant rotation via vendor admin

Rotating a personal access token on one Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026 workspace by hand is fine; rotating across a team of workspaces is how you end up with twelve different tokens, four expired ones, and an unknown blast radius. Drive rotation through the Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026 admin SDK or REST under a service account with the rotation scope only, store the new token in a personal password manager (1Password, Bitwarden, vendor secrets manager) with versioning enabled, and roll the consumer scripts one workspace at a time with a health check between each. Pin the API version explicitly during rotation so a coincident vendor rollout does not look like a rotation failure.

# Rotate the platform API token (regenerate via the admin UI, capture in 1Password)
op item create --vault Work --category "API Credential" \ --title "power platform token 2026-05-31" \ password="$NEW_PLATFORM_TOKEN" notes="Rotated $(date -Iseconds)"
# Capture the old token as deprecated so cutover is reversible
op item create --vault Work --category "API Credential" \ --title "power platform token OLD 2026-05-31" \ password="$OLD_PLATFORM_TOKEN" notes="Old token marked deprecated"

Codify the platform version pin and rollback as a single notes entry

Once a stable platform version is identified for the Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026, write the version string, the build hash, and the workspace policy state to a personal notes entry with the date in the title. Reproducible rollback is then a single download-and-install plus a sign-in. Pin the workspace policy state explicitly so a vendor-side default change does not silently shift behavior under you. Stage the notes entry next to a checklist that lists the failing screenshot, the Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026 incident id (if any), and the support case number; the second time the workflow breaks at 9 a.m. you do not want to be rediscovering which platform build was actually green.

# Personal notes template (power)
Date: 2026-05-31
Platform: power
Working build: 2.45.1 (Build hash: a1b2c3d)
Account: work@example.com
Workspace: ws-prod-power
Failing screenshot: ~/notes/power-2026-05-31.png
Support case: SUPP-power-12345
Rollback path: download installer from vendor releases page, sign out, reinstall, sign back in

Automate Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026 session + sharing-policy snapshots via vendor CLI or API

On the Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026, regular session and policy snapshots catch silent role changes, sharing-default drift, and stale OAuth grants well before the workflow starts failing in prod. Pair vendor health checks (the platform's admin SDK, the platform's users API, the connector listing) with a token-validity check so both vendor-side and account-side issues land in one folder. Run the scheduled task on a control plane device (a small VPS, a GitHub Actions runner, a Cloud Function) under a tightly scoped service account that mirrors the real workspace policy.

# List workspace members + roles
curl -H "Authorization: Bearer $PLATFORM_TOKEN" \ https://api.example.com/v1/workspace/members \ > power-members.json
# List active connectors + their last-tested timestamp
curl -H "Authorization: Bearer $PLATFORM_TOKEN" \ https://api.example.com/v1/connectors \ > power-connectors.json
# Validate the bearer token itself
curl -H "Authorization: Bearer $PLATFORM_TOKEN" \ https://api.example.com/v1/me \ > power-me.json

Common pitfalls and what to watch for

Read-only validation before any write is the single step most Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026 fixes skip, and it is the step that lets you roll back when a fix backfires. Screenshot every existing settings page (the workspace settings, the sharing policy, the connected-apps list, the members page, the plan tier page), capture the failing screenshot in a notes entry, export the relevant log to CSV if the platform supports it (the platform's run-history export, the audit-log download), and screenshot the activity feed showing the failing window before any change. On Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026 workspaces with multiple environments (test workspace, real workspace) record the platform version, the settings state, and the connected-apps list in each before toggling anything, because a "fix" pushed only to the test workspace is a known regression vector when the real workspace has a different policy.

The mirror-image mistake is confusing a user-side symptom with a vendor fault on Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026. A persistent 403 is often a connector-level change pushed by the workspace owner rather than a Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026 bug. A "scenario not found" can be a moved scenario rather than a deleted one. A "webhook not firing" is frequently a corporate proxy or firewall dropping the Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026 egress IP rather than a vendor-side regression.

Verify the fix worked

Reproduce the original failing run against Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026 on the same device AND a second device with the same account. If the failing toast or error code still surfaces on any device, you have not fixed it.
Watch for 24 to 48 hours via the Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026 workspace audit log + the integration history + your personal notes. Cached error states and CDN caches mask slow-burn drift and intermittent regional issues.
Smoke-test under realistic load: replay the workflow against a test workspace for at least 30 minutes at your normal working pace, log success / error and the timestamp per attempt to a notes file.
Capture the new state in a personal notes entry so the next time this happens you do not rediscover it. Note platform version + workspace policy + connected-apps list + failing screenshot + verbatim error string + fix applied. Push to a shared team wiki if your team uses one.
If the fix involved an API token rotation or a workspace policy change, commit the new token to your password manager and screenshot the workspace settings for archival.

Safety, rollback, blast radius

Test in a Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026 test workspace or on a duplicate scenario first before any change that touches the real workspace. Snapshot the platform version, the workspace settings, the connected-apps list, and the sharing policy before changing anything.
Apply the principle of least surprise when granting share access or connected-app permissions. Review the share list against the people who actually need access - extra shares are extra blast radius.
Use idempotent runs where the Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026 API supports it (the platform's run id de-dupe, external id keys on destination records) so a retried run does not create duplicate records.
Know your rollback path. Platform version rollback is a one-line download-and-install; an API token rotation is reversible if you kept the old token in the password manager during cutover; a workspace policy change is reversible only if you saved the previous policy in a screenshot.
For team-wide or workspace-wide changes, line up a maintenance window with team notification before pushing through the admin console.

FAQ

How long does how to assign an approval to a sharepoint person column value with the claims property typically take on Power Automate Approvals: Modern Approvals, Adaptive Cards & Teams, 2026?

For most Power Automate Approvals. Modern Approvals, Adaptive Cards & Teams, 2026 workflows, 5 to 30 minutes including verification. Large workspace migrations, anything touching API token rotation or SSO cutover, or cross-region exports can stretch to half a day because you have to wait for re-share notifications, OAuth re-consent, or coordinated team windows.

Is there a rollback path?

Yes for most Power Automate Approvals: Modern Approvals, Adaptive Cards & Teams, 2026 changes. Snapshot the platform version, screenshot the workspace settings, export the audit log, and write down the API token before any change. A few operations are one-way (deleted scenarios past the trash window, irreversible plan downgrades, permanently revoked connectors). Check the in-product help for the specific operation before you commit.

Will this affect other teammates in the Power Automate Approvals. Modern Approvals, Adaptive Cards & Teams, 2026 workspace?

Often yes. Power Automate Approvals: Modern Approvals, Adaptive Cards & Teams, 2026 workspaces share sharing policies, plan quotas, member rosters, and connected-app permissions across the whole tenant (one connected-app grant holds permissions for many integrations, one sharing policy covers all scenarios, one plan tier covers all members). Use the Power Automate Approvals. Modern Approvals, Adaptive Cards & Teams, 2026 workspace audit log and the connected-apps list to enumerate dependencies before changing a shared component.

What if my platform version or workspace policy does not match these steps?

Vendor defaults move between releases. The steps in this page reflect mainstream defaults as of 2026-05-31 but the underlying workflow patterns do not change as fast. If a path differs on your version, fall back to the in-product help, the Power Automate Approvals: Modern Approvals, Adaptive Cards & Teams, 2026 status page incident history, or the community forum - those almost always still work.

Where do I get vendor support if I am still stuck?

If you have a paid Business / Enterprise plan, open a case via the in-product help chat with: the exact verbatim error string, the failing screenshot, the URL of the scenario or workspace, your account email, the platform version, and your reproduction steps. The Power Automate Approvals. Modern Approvals, Adaptive Cards & Teams, 2026 community forum and r/nocode are the no-cost public alternatives - search there first; 80 percent of common Power Automate Approvals: Modern Approvals, Adaptive Cards & Teams, 2026 issues already have a working answer voted to the top.

References

Vendor help center for Power Automate Approvals. Modern Approvals, Adaptive Cards & Teams, 2026 (official help articles, API docs, Trust Center)
Community forums (r/nocode, r/automation, r/GoogleAppsScript, r/PowerAutomate, r/n8n, r/make, r/ClaudeAI, vendor community)
In-product help and the Power Automate Approvals: Modern Approvals, Adaptive Cards & Teams, 2026 changelog
Vendor status pages and X/Twitter status handles, plus post-mortem incident reports

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