Hi together,
for about a week, no data can be imported from Power BI Service Semantic Models. When clicking “Pick” on the table name, the error “Failed to retrieve a list of tables: Bad Request” appears.
The connector has already been checked and tested.
Hi @xChristophx
Thank you for reporting the issue, we're investigating it.
Hi @xChristophx
We've confirmed and reproduced the issue. After some investigation, it seems that this is a major outage on Microsoft's end.
We'll inform you when it's resolved, unfortunately currently it seems there are no feasible workarounds for the powerBi import
You can manually paste the table name in the action settings, as a workaround.
Thank you very much, but unfortunately, that doesn't help us very much.
The reason for this is we need to draw evaluations from multiple semantic models and therefore from a large number of tables.
I suggest contacting Microsoft support for that issue. We can't do much if their API is not available.
I have found a working interim solution for us.
Until the API provides a list of tables again, I will solve this using a separate table in M-Code, which will have the same name in every semantic model and will return a list of tables. This will enable an iterative table retrieval.
In the attached screenshot, the approach in M-Code can be seen.
UPDATE
It looks like Microsoft unknowingly made a breaking change and is now trying to fix it without much success. The INFO functions in DAX introduced in 2023 don't work and they don't know when it will be fixed.
We will wait until more information is provided by Microsoft. Unfortunately, we can't do much here 
To add to the topic, it's not just the DAX INFO() methods that are failing, which we heavily rely on; the EVALUATE TOPNSKIP expression is also not working.
We use this expression for pagination purposes with large datasets, and it fails when the skip value is non-zero. So, the full extent of the outage is still unknown, and currently, Microsoft hasn't provided an ETA for fixing the problem.
Update from Microsoft:
Based on the latest update from our internal team, the fix is currently scheduled for March 24, 2025 . In the meantime, I will keep you updated on any further developments or changes
