This case #2402280040011813 is in regards to this issue: Solved: ISSUE+SOLUTION::published report Fabric datasource... - Microsoft Fabric Community
Apparently this is the reason:
• The Back-End cluster determines how authenticated clients interact with the Power BI service. The Back-End cluster manages visualizations, user dashboards, semantic models, reports, data storage, data connections, data refresh, and other aspects of interacting with the Power BI service. The Gateway Role acts as a gateway between user requests and the Power BI service. Users don't interact directly with any roles other than the Gateway Role. Azure API Management eventually handles the Gateway Role.
• Below is the document for the reference Power bi Security.
Power BI Security - Power BI | Microsoft Learn
Also, OAuth2 is the authentication method to use because, according to the SE:
If you are using on-prem datasource you will get option for windows and basic.
If you are using cloud will be Oauth2.
Because you are using lakehouse table and is since not an On-Prem this not authenticating you to use basic or windows.
In other words, even though Basic and Windows authentication methods wil be available they won't work because of the type of data source, and in this case, since the data source is in the cloud, only OAuth2 is the way to go.
Perhaps then the other authentication methods shouldn't be displayed since they won't work anyway. Causes unwarranted confusion in the UX.
on:
URL is not filtering on field parameter