Advance your Data & AI career with 50 days of live learning, dataviz contests, hands-on challenges, study groups & certifications and more!
Get registeredJoin us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM. Register now.
I am importing XML data that I am downloading from an old SSRS server using a direct URL. Something like
input = Xml.Tables(Web.Contents("https://ourreportserver.us.net/", [
RelativePath = "sites/" & office & "/_vti_bin/ReportServer?https%3a%2f%2fourreportserver.us.net%2fsites%2f" & office & "%2fReporting++MI%2fReportInQuestion.rdl&rs:Command=Render&StartDate=" & Date.ToText(start, [Format="M/d/yyyy", Culture="en-US"]) & "&EndDate=" & Date.ToText(end, [Format="M/d/yyyy", Culture="en-US"]) & "&Aparameter=true&rs:Format=XML",
Timeout=#duration(0,0,10,0)]))
This previously worked fine using Windows Authentication. However the server has recently been updated to use Okta SSO instead. Is there a way to get this to work again? If I try to select Organizational Account in the credential options I get the error "We were unable to connect because this credential type isn't supported for this resource" (whether I try at the level of ourreportserver.us.net, or at the sites/ or sites/office level).
I did try seeing what Web.BrowserContents brings up, and I can see it is the HTML for the login page.
Hi @MBZA ,
Could you please let us know whether your issue has been resolved or if you are still encountering any difficulties? Your feedback is important to the community and may assist others with similar concerns.
Thank You.
Hi @MBZA ,
May I know if your issue has been resolved, or if you still need any additional details? Please let us know if there’s anything else we can help with.
Thank you.
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.
Join the Fabric FabCon Global Hackathon—running virtually through Nov 3. Open to all skill levels. $10,000 in prizes!
Check out the October 2025 Power BI update to learn about new features.