Paulo Nunes on 03 May 2024 12:51:01
Currently, if the following settings are set on at the Power BI tenant level, private communication while embedding Power BI dashboards on a page is broken and requires public access to urls such as "wabi-*****-primary-redirect.analysis.windows.net":
privateLinksEnabled=True
allowAccessOverPublicInternet=True
The private communication is only fully private if the second option is set to false as mentioned here - https://learn.microsoft.com/en-us/fabric/security/security-private-links-use#step-8-disable-public-access-for-fabric
There are use cases and costumers that require both ways to communicate with Power BI to be work simultaneously. The only workaround is to map "wabi-*****-primary-redirect.analysis.windows.net" addresses to one of the private endpoint addresses leveraging a custom dns entry or a hosts file on the client machines. These sort of addresses are not mapped to any private endpoint through private DNS - this would solve this issue.