Exporting Paginated Report with EffectiveIdentity Fails for External User Not in Tenant

Hi Himanshu_G,

Thank you for reaching out to the Microsoft Fabric Forum Community.

Exporting a paginated report with effectiveIdentity fails for external users because Power BI requires the identity to be resolvable in Azure AD, even if stored credentials are used.

To support external users who aren't in your tenant:

Remove effectiveIdentity from the export call. Pass a custom parameter (e.g., @UserId) to the report. Implement RLS filtering inside the report or SQL using this parameter. This approach bypasses the identity validation issue while still enforcing user-specific Data access.

If you found this response helpful, please consider marking it as the accepted solution and giving it a thumbs-up to assist others in the community.

Thank you and best regards,
Prasanna Kumar

Hi Himanshu_G,

Yes You can Pass Custom parameters.

To enforce Row-Level Security (RLS) in embedded paginated reports—especially for external users not in Azure AD—you can pass a custom parameter like @UserId instead of using effectiveIdentity.

Use stored credentials in the RDL so the report doesn't rely on the user's identity for data access. During embedding, pass the user's identifier as a report parameter, which the report or SQL uses to filter data.

Example:

{
"parameters": [
{ "name": "UserId", "value": "external_user_123" }
]
}

This works for both internal and external users:

External: pass their custom ID.

Internal: pass mapped ID (e.g., email or UPN).

This keeps the report secure and RLS dynamic without needing Azure AD resolution.

If you found this response helpful, please consider marking it as the accepted solution and giving it a thumbs-up to help others in the community.

Thank you & regards,
Prasanna Kumar