Answered

[New Experience] Issue with running Jason Request/Request against a Power Bi model

(0) Share

Report

Posted on by MS-07070830-0

Hi everyone,

im currently trying to bring my classic Copilot Studio agent to the new experience but run into an issue with the power bi tool to request data from a bi model.

When i set up the tool it works when testing it the first time but when i open a new chat the request consistantly runs into this error:
This tool call couldn’t run The request is missing required info or uses unsupported values. Error details: Request validation · 400.

Im using the same LLM, same instructions and knowledge files. The classic agent works fine and does not use any topics.

The queries generated by the agent are fine.

I feel like there is a bug with the tool call.

It also fails to set up the permissions when used in teams or the copilot app. The card keeps poping up.

Any ideas?

Best Regards,
Markus

Categories:

General topics

I have the same question (0)

All responses (3)

Answers (1)

Sort by

Verified answer

Assisted by AI

Ashlesha-MSFT Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!
MS-07070830-0 A few things are worth checking because this sounds more like a session or authentication issue than a DAX/query generation problem.

Verify the connection after starting a new chat

Since the first request works but every new chat returns a 400 Request validation error, it suggests the Power BI tool may not be re-establishing its connection or passing the required context in new sessions.

Try removing and recreating the Power BI tool connection

Test with a minimal prompt

Create a new agent with only:

One Power BI tool

No knowledge sources

Default instruction

If the same behavior occurs, it's likely a platform issue rather than something in your agent configuration

Check whether it's specific to the New Experience

Since your Classic Copilot Studio agent works with the same model, instructions, and generated queries, this points toward a regression in the New Experience rather than an issue with the semantic model

Inspect the network request

Open your browser's Developer Tools (F12 → Network).

Capture the failing request and compare it with the successful first request.

Look for missing values such as:

conversation/session ID

tool connection ID

dataset or semantic model ID

tenant/workspace identifier

The response body for the 400 error may contain a more specific validation message

Permission prompt looping

The repeated permission card in Teams/Copilot is another indication that the connection or OAuth token isn't being persisted between sessions.

Try:

Disconnecting and reconnecting the Power BI connection.

Republishing the agent.

Testing in another browser or InPrivate window.

Testing with another user account if available.

Compare environments

Does the issue happen in:

Copilot Studio test pane?

Microsoft Teams?

Microsoft 365 Copilot app

If it fails everywhere except the first invocation, that's useful evidence for Microsoft.

If possible, capture the Correlation ID, Activity ID, and timestamp from the failed request and include them in a Microsoft support ticket. That will help the product team trace the failing request.

Was this reply helpful? Yes No
Ashlesha-MSFT Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

MS-07070830-0 Just following up on the answer I shared recently. Could you please let me know if it resolved your issue, or if you need any further clarification?

Was this reply helpful? Yes No
MS-07070830-0 4 on at

Like
a
(1)

Report
Copy link

Link copied!

Hi,

thank you for the feedback.

It is now working. Removing the tool and recreating it did the tick (even so i also tried that before). The agent is now able to query the model without issues.

It also works in Teams and Copilot 365. But i have no idea what changed or made this work now.

Best regards,

Markus

Was this reply helpful? Yes No