Work IQ MCP tools — repeated individual approvals + intermittent freeze on “Approve”

(1) Share

Report

Posted on by YJ-02010636-0

I'm publishing a Power Platform solution using 8 Work IQ MCPs exposed as tools, and running into two related issues:

Approval friction: Users must approve each MCP/tool individually. There’s no apparent way to approve a group of tools.

Freeze on approval: Intermittently, after clicking “Approve”, the dialog freezes and the action never completes — no error, no fallback, just a stuck state.

Questions:

Is per-tool approval the expected behavior, or is there a way to bulk-approve / persist trust across MCP tools?

Has anyone seen the approval dialog freeze issue? Why does it fail sometimes for some users?

Recommended troubleshooting or logging approach to isolate the freeze?

Any production-ready patterns to reduce this friction for end users?

Categories:

Model context protocol

I have the same question (0)

All responses (2)

Answers (0)

Sort by

Suggested answer

11manish 2,983 on at

Like (0)

Report
Copy link

Link copied!

The per-tool approval requirement is currently expected behavior.

The freezing approval dialog is not expected and is likely related to session state, authentication, backend registration timing, or a platform

defect.

For troubleshooting, I'd start with HAR traces, browser network logs, and Entra sign-in logs for affected users. From a production perspective,

the most effective mitigation is usually to reduce the number of exposed tools and group functionality into fewer MCP endpoints wherever

possible, thereby minimizing approval prompts and opportunities for the approval workflow to fail.

Was this reply helpful? Yes No
Suggested answer

Valantis 6,456 on at

Like (1)

Report
Copy link

Link copied!

Hi @YJ-02010636-0,

Per-tool approval is expected behavior. Microsoft's own Work IQ MCP docs explicitly state "Approve each tool call when prompted" as the standard flow. There is currently no bulk approval or persistent trust mechanism across MCP tools. With 8 tools that's going to generate significant approval friction for every conversation where multiple tools are invoked.

To reduce this in production: consolidate where possible. If multiple Work IQ tools serve related purposes, consider whether you can route through fewer tools and have those tools handle more internally. This is the only currently supported way to reduce the approval count per interaction.

For the approval dialog freeze: this is not documented expected behavior, it's likely a combination of factors since Work IQ MCP only became generally available on June 16, 2026 and is still very fresh.

The most likely causes are session/auth token expiry mid-flow, network latency between the browser and the Work IQ backend, or a race condition in the approval dialog when multiple tool calls are queued. Browser DevTools network tab during a freeze will show whether the approval API call is hanging or returning an error silently.

For affected users specifically, check if they have valid Microsoft 365 Copilot licenses (required for Work IQ MCP) and that Copilot Credits are provisioned in PPAC for the environment. A missing license or billing issue can cause silent failures on the approval step without a clear error message.

Ref: https://learn.microsoft.com/en-us/microsoft-copilot-studio/use-work-iq

Best regards,

Valantis

✅ If this helped solve your issue, please Accept as Solution so others can find it quickly.

❤️ If it didn’t fully solve it but was still useful, please click “Yes” on “Was this reply helpful?” or leave a Like :).

🏷️ For follow-ups @Valantis.

📝 https://valantisond365.com/

💼 LinkedIn

▶️ YouTube

Was this reply helpful? Yes No