New Adobe Analytics API 2.0, not working on service?

I’ve encountered this issue as well;

 it only occurs in the Service, while the Desktop version works fine. This is causing significant problems for our report refreshes. When will this be resolved?

Sorry for the delay. It doesn't work; it's a connector issue when using Power BI Desktop. The Microsoft team is already working on it to try to fix it. I hope they do so soon.

But you have two alternative solutions:

- It works in data flows, so you can do the same thing you do in Power Query, but in data flows, and load the data flow into the Power BI Desktop model.

- Use native calls to the Adobe API 2.0.

I’ve successfully tested both; the second option requires recursion if you’re using multiple dimensions, and you’ll need an access token. The first option is easier since you can simply copy and paste the Power Query script.

I hope this helps, and above all, I hope they update the Quick Connector soon, since it’s often more convenient to work with it.

Regards

Hi mperez​ ,

This looks like a Power BI Service-side issue rather than an M-code problem. Since your query already uses Implementation="2.0" and works in Desktop, but the Service fails during credential validation with “This API endpoint has been discontinued”, the Service connector may still be calling an Adobe Analytics 1.4 endpoint internally.

Try deleting and recreating the Adobe Analytics data-source connection/credentials in Power BI Service. If the same error persists, open a Microsoft support ticket and provide the PBIX, Desktop version, M query and exact error, as Adobe API 1.4 was retired and there is no client-side setting to force the Service authentication flow to use 2.0.

Migrating to the 2.0 API

Thanks!!

I'm facing the same issue, was a solution found?

I deleted the old 1.4 Data Source and recreated 2.0 in Power BI Desktop which seemed to work until authentication failure after publishing to the PBI service.

Unablet to authenticate the data connection in PBI Service.

Update:
Microsoft Fabric service status

I have also tried the Dataflows method but it doesn't work in PBI Service. Desktop is working fine.

I am also facing same issue....
I checked my queries has implementation = 2.0 already desktop version working but web version gives error of API endpoint discontinued
And resolution will be appreciated.

Hi mperez​ ,

Could you review the suggestion provided above and let us know if you have any additional questions, we are happy to address. 

Thanks!!

Power BI customers may experience failures when creating new Adobe Analytics connections or updating credentials for existing connections, resulting in the error: “DataSource.Error: This API endpoint has been discontinued.” As a workaround, Customers can create the Adobe Analytics connection through Dataflows Get Data and then use that connection with their Semantic Model. Engineers have identified the root cause and a fix for the issue will be deployed by end-of-day 09/14/2026.

Notification DateTime: 09/09/2026 11:29 AM PDT

Regions: All

Microsoft Fabric service status

Hi mperez​ ,

This is a known gap in the Power BI service, not something on your end. The desktop connector already talks to the 2.0 API, but the service's credential re-authentication flow for the Adobe Analytics connector still calls a 1.4 endpoint under the hood. Since Adobe fully retired 1.4, that credential handshake fails with exactly the error you're seeing, even though your query uses Implementation="2.0".

This is a backend fix Microsoft needs to ship, not a config issue on your report. In the meantime:

• Scheduled refresh in the service will keep failing until this is patched
• Desktop refresh will keep working since it doesn't route through that broken credential path
• If you need this live, a temporary workaround is exporting refreshed data from Desktop and publishing, or piping data through a Dataflow/Gateway on-prem where the credential path differs

Worth opening a support ticket referencing this if you haven't, it strengthens the case for prioritizing a fix. I'd also flag it on the Fabric Ideas forum if there isn't already a thread, since this affects anyone still using the native Adobe Analytics connector post-deprecation.

Hi mperez​  , marketingdork​  and marketingdork​ ,

Could you please confirm whether issue got resolved or not from your end?

Thanks!!