Forum Discussion
Get data using Web.Contents when Okta SSO is in use
- 10 months ago
Hi MBZA ,
Thanks for posting your query in the Microsoft Fabric Community. You’re right about the authentication change. The SSRS server now uses Okta SSO, which depends on browser based login flows. Power BI’s Web.Contents function doesn’t support these interactive sign ins and only works with direct authentication methods like Windows, Basic, or API keys.
As a result, when Power BI attempts to connect, it’s redirected to the Okta login page, leading to the credential type not supported error.
Helpful Reference:
Web.Contents - PowerQuery M | Microsoft LearnAs an alternative
1. Using a service or API account that authenticates directly, bypassing Okta.
2. Automating report exports with PowerShell or an API and connecting Power BI to the exported XML file.
Regards,
Yugandhar.
Hi MBZA ,
Thanks for posting your query in the Microsoft Fabric Community. You’re right about the authentication change. The SSRS server now uses Okta SSO, which depends on browser based login flows. Power BI’s Web.Contents function doesn’t support these interactive sign ins and only works with direct authentication methods like Windows, Basic, or API keys.
As a result, when Power BI attempts to connect, it’s redirected to the Okta login page, leading to the credential type not supported error.
Helpful Reference:
Web.Contents - PowerQuery M | Microsoft Learn
As an alternative
1. Using a service or API account that authenticates directly, bypassing Okta.
2. Automating report exports with PowerShell or an API and connecting Power BI to the exported XML file.
Regards,
Yugandhar.