u/Powerth1rt33n

We're trying to give users access to the SQL endpoint of our newest lakehouse, but we're running into issues with permissions. When they connect through the Onelake Catalog menu in Power BI, they're able to connect with no problems. But if they try to use the actual endpoint string, either to connect from Power BI or to connect from SQL Studio, or they try to use the Open In SQL Studio option of the lakehouse endpoint, it gives them a permissions issue.

As far as I can tell, the problem is that they don't have access to the workspace that the Lakehouse is in. When they open it in Fabric, it shows up as being in their My Workspace, not the actual workspace it's in, and I can't figure out a combination of permissions that will give them the ability to use the endpoint properly without giving them access to the entire workspace. Has anyone else run into this and solved it?

Just got the annual email making sure my shipping address is up to date. Fingers crossed it ships out in a relatively timely manner but we've all learned the hard way not to hold our breath.

Hi all - as the result of a merger, we're in the process of migrating a separate organization's Azure tenant into our tenant. Does anyone here have experience with how this will affect the Fabric/Power BI architecture that they have in place? We want to maintain their reporting with as little disruption as possible. Migration docs say that the old location of Sharepoint files etc will be given a redirect URL to the new location and user IDs in the old tenant will be mapped to the new IDs, but frankly the promise of it being Just That Easy is hard to believe. Have any of you ever done something like this? How easily did it work out?