Allow cross-tenant Private Link access to Fabric

[dhaworth]

The Microsoft Fabric docs provide this guide to configuring Private Link access to a Fabric tenant. However, in testing this approach a provisioned endpoint could not be connect from a separate Azure tenant. The private endpoint could be created, but when attepting to approve the connection the following error resulted:

Upon consulting Microsoft Support they concluded that it is not supported to create Private Link endpoint connections to Fabric from a different Azure tenant, citing the following documented limitations:

- Customers can't connect to Fabric resources in multiple tenants from a single virtual network, but rather only the last tenant to set up Private Link. 
- Each private endpoint can be connected to one tenant only. You can't set up a private link to be used by more than one tenant.

Private connectivty to Fabric from a separate tenant is a high priority for our customers who rely on our services to connect to their Fabric data sources, but have strict access requirements. Please consider enabling this functionality. You may contact me for a discussion on details and requirements, if desired. 

[boxysean]

I work at dbt Labs and we offer Fabric as a connector for dbt Cloud Enterprise customers. With this idea implemented, dbt Cloud users can maximally protect their data and risks of interception. Some security-conscious organizations who use or want to use dbt Cloud (or other 3rd party SaaS applications) require connecting with Azure Private Link to Fabric.