web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Apps / Virtual table from Fab...
Power Apps
Suggested Answer

Virtual table from Fabric Lakehouse returns 401 Unauthorized in Power Apps — all prerequisites met

(0) ShareShare
ReportReport
Posted on by
Hi all, 

I'm trying to create a Dataverse virtual table connected to a view in a Fabric Lakehouse SQL Analytics Endpoint, following the official reference architecture. The virtual table is created successfully with correct columns, but opening it in Power Apps returns a 401 Unauthorized error and no data.

 

Environment:


  • Fabric capacity: F64 Trial, Active, Sweden Central

  • Power Apps environment: Sweden region

  • User license: Power Apps Plan 2 Trial

  • Workspace role: Admin with full OneLake permissions (Read, Write, ReadAll etc.)

  • Authentication: Azure AD (not Basic)


  •  

What I have tried:


  • Both Microsoft Fabric connector and SQL Server connector — same result

  • Integer primary key (rad_id via CHECKSUM) — table creates correctly, 401 on open

  • Verified OneLake folder permissions — ReadAll confirmed

  • Verified region match between Fabric capacity and Power Apps environment

  • SQL Analytics Endpoint works correctly when queried directly inside Fabric

  • No RetrieveMultiple network call visible in browser trace when error occurs


  •  

Has anyone resolved this? Is this related to Known Issue 1121 (column mapping causing empty SQL Analytics Endpoint results)?

I have the same question (0)
  • Suggested answer
    Olufemi 7 Profile Picture
    72 on at
    Hello @AK-11051418-0,

    A 401 in Dataverse virtual tables against Fabric Lakehouse SQL endpoint is almost always an authentication delegation issue, not a schema or permissions problem. If no RetrieveMultiple call appears, the failure is occurring before query execution during Entra ID token exchange with the connector.

    Most likely causes are token audience mismatch or Conditional Access blocking non-interactive connector authentication; Fabric Lakehouse SQL endpoint may also have connector compatibility limitations depending on tenant configuration.

    Docs: Create and edit virtual tables that contain data from an external data source

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Launch!

Jump in, show your community spirit, and win prizes!

Kudos to our 2025 Community Spotlight Honorees

Expanding mentorship, skilling, and AI innovation

Congratulations to the May Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Apps

#1
Valantis Profile Picture

Valantis 424

#2
WarrenBelz Profile Picture

WarrenBelz 355 Most Valuable Professional

#3
11manish Profile Picture

11manish 290

Last 30 days Overall leaderboard