This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. We're covering it all. You won't want to miss it.
Learn moreDid you hear? There's a new SQL AI Developer certification (DP-800). Start preparing now and be one of the first to get certified. Register now
Big news for Fabric users, managing workloads just got a lot easier! With the new Workspace-level assignment feature, workspace admins can now add additional workloads directly to their own workspaces—no more waiting on tenant or capacity-level setup.
This update makes using additional workloads more accessible than ever. Once a workload is added, you can immediately create custom Fabric items in that workspace, giving teams the flexibility to build exactly what they need, where they need it.
The result? A more agile, scalable, and responsive Fabric experience—while still preserving governance and security.
New_in_Microsoft_Fabric_Empowering_Workspace_Admins_with_Direct_Workload_Assignm
Add workloads from the Workloads Hub and assign workloads directly to the workspace where the data and team is working.
With workspace-level assignment, you can now enable multiple workloads in a specific workspace without affecting the rest of the tenant. This allows teams to experiment, innovate, and deploy solutions tailored to their needs.
New_in_Microsoft_Fabric_Empowering_Workspace_Admins_with_Direct_Workload_Assignm
Fabric admins retain complete control on the availability of workloads in the tenant by configuring the newly added 'Allow workspace admins to add workloads' Tenant Settings under the Additional Workloads settings It’s enabled by default, and Fabric admins can turn it off at any time
Even with this new flexibility, Entra ID consent continues to apply as before. Users and/or tenant admins must still provide consent according to tenant policies before workloads can be used.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.