Flow Action 'Export To File for Paginated Reports' failing suddenly > error "Effective identity on datasources with SSO enabled is not supported"

[KaySunset]

Hi all,

two of my flows are suddenly failing since saturday, there have been no changes from my end. The action that exports a file from paginated report (PBI premium per user) throws the error "Effective identity on datasources with SSO enabled is not supported". The two flows affected are supposed to export the files to a SFTP server in the following step.

All other flows exporting paginated reports from the same instance work perfectly fine. The only difference in setup is that the following action is Send to user per Mail instead of Create file on SFTP.

The error message implies that there might be an issue with my PBI connection, but many flows using the same connection work well. I have also set up a simple flow only with the export action. The two reports in question won't work (error hits immediately), all others will.

Any ideas?

Here's detailed error info:

{

    "statusCode": 400,

    "headers": {

        "Pragma": "no-cache",

        "Strict-Transport-Security": "max-age=31536000; includeSubDomains",

        "X-Frame-Options": "deny",

        "X-Content-Type-Options": "nosniff",

        "RequestId": "f012062f-fef6-45b3-9d8e-280e996ca66e",

        "Access-Control-Expose-Headers": "RequestId",

        "Timing-Allow-Origin": "*",

        "x-ms-apihub-cached-response": "false",

        "x-ms-apihub-obo": "true",

        "Cache-Control": "no-store, must-revalidate, no-cache",

        "Date": "Mon, 31 Jan 2022 08:14:47 GMT",

        "Content-Length": "140",

        "Content-Type": "application/json"

    },

    "body": {

        "error": {

            "code": "InvalidRequest",

            "message": "Effective identity on datasources with SSO enabled is not supported"

        }

    }

}

Many thanks in advance,

Kathrin

[Anonymous]

I'm having the same issue:
"Effective identity on datasources with SSO enabled is not supported"  
With the flow failing from Jan 28th... Any ideas on how to solve this will be much appreciated. 

[ElaineCRO]

I also started getting the same error since Jan 28.

The error happened due to a connection failure with my Azure SQL Server. No onde changed any settings, so i believe there was some internal update in Azure.

To solve it, i released the power automate IPs in my SQL Server firewall and now the flows are running correctly.

Get the IPs in the link https://docs.microsoft.com/pt-br/power-automate/ip-address-configuration 

[darlizzzz]

same problem

[rk2221]

Same issue, do we have any solution for this issue.

[kmankash55]

We are seeing the same issue at our company recently as well. We have a flow from Jan 18th failing with this error. 

Getting the error: Flow Action 'Export To File for Paginated Reports' failing suddenly > error "Effective identity on datasources with SSO enabled is not supported"

This is the Power BI action that we use.

@v-jefferni has anything changed with these Power BI actions?

[j500sut]

I'm having the same issue with exporting a paginated report using the REST API Export To in Group.

I have tested with a "normal" Power BI report and the export works just fine, so it seems to be only isolated to Pagenated reports.

It would be good to have this resolved quickly as its a critical process for my client.

[KaySunset]

My datasource is an analysis service tabular model, on which no firewall is enabled. Therefore, this solution will unfortunately not work for me..

[jagdish0909]

I am also facing same issue. It would be good if Microsoft share some solution quickly because many users are impacted and not able to delivered the reports.  

[j500sut]

Hi all! 

I managed to resolve the issue by opening the report in the service in Power BI Report Builder, re-entering the datasource credentials and re-publishing (no other changes were made).

I was informed that the user who published the report previously was using version 15.7.1740.1

After the republish using version 15.7.1796.1 and everything works now. I tested the API call from postman before re-running the Logic App.

Hope that helps!

[Anonymous]

Hi.

I am having same issues. I am using latest version of Report Builder.

There are several weird behaviors detected:

 1 - If Paginated Report is published using Windows Credentials it works on the PBI portal but it fails on the Logic App with the SSO error: "Effective identity on datasources with SSO enabled is not supported"

 2 - If Paginated Report is published using "Do not use credentials" the Logic Apps returns a "Bad Gateway" error.

Plus a weird behavior happens if you run the report on the portal it reverts back the connection from "Do not use credentials" to "Windows" Auth.

3 - If we try to specify a particular identity on the connector we get error " Exporting a paginated report with an effective identity with datasets is not supported "

Our paginated report dataset is connecting to a Power BI premium (XMLA) dataset using RLS.

Any ideas what is happening?

[jagdish0909]

Our issue was resolved. As per the above solution, we have re-enter the credentials and republish the rdl report again and Its working fine.

[Anonymous]

What you mean re-enter credentials? So you are hard coding your user and password on the datasource? That makes you have double reports published no? One for portal user consumption and another for subscriptions?

As far as I know the SSO should work and specifying user and password should not be required.

[j500sut]

Yes, and the workspace is isolated and the reports are only used for the automated process. So the credentials are a specific user to access the underlying datasource for us to keep track on connections to the AAS cube. 

The reports are not duplicated, the original is just overwritten.

If you have RLS configured on your reports, my solution might not fit your requirement.

One addi

[KaySunset]

Hi @j500sut ,

could you share yor credential/connection settings? We somehow don't get it to work. As we're also using an AAS cube as source, it should be similar to yours.

Thanks in advance!

[BM4]

We got hit by this one today out of the blue also; following some of the advice above from @j500sut, I took over the dataset in the service and re-entered the credentials (OAuth - O365) which appears to have done the trick. My reports are all pointing to an AAS instance.

The concerns here however are:

- Will this work again tomorrow, or the day after etc

- Do we need to apply this on all reports that are currently being picked up by PowerAutomate

    - If not, what are the exceptions?

- When will a 'fix' be applied!

[Anonymous · Accepted solution]

The problem seems to be fixed, All I did was reentering the credentials on the Power BI Service.

[KaySunset]

That's correct, for me it works even withot any credential update.

Many thanks for all the suggestions 🙂 

[jzaragoza]

It works for me. No need to republish my reports.

[sukajalan2]

Reentering credentials works for AAS as the datasource but it does not work if the datasource is a Power BI dataset. I tried to republish my reports and it does not work either.