This post covers module 10 in the Cloud Skills challenge. This is where the video series and the challenge modules start to diverge a bit. Modules 8, 9 and 13 were not covered in the Learn Together video series, so I will be covering those last. Modules 10, 11 & 12 were covered in a different order in the Learn Together series, but for this blog, I am putting them in the order of how they appear in the Microsoft Learn challenge instead.
Previous posts in this series:
Microsoft Learn Module
This module covers the configuration and management of Microsoft Fabric including user access and key things to be aware of in the admin center. There is no exercise in this module although users could follow along with the windows presented in some of the units where they can.
Learn Together links (recordings from wave 1)
This topic was covered in Session 9 of the Learn Together series. The link below is the session I watched on this topic. Some concepts I missed the first time so I did go back to re-watch some elements of the recording to make sure my notes and understanding were OK here.
Key Takeaways
"Capacity" is not "space". The word capacity to me means size or volume, but in the context of Microsoft Fabric, when someone says "Microsoft Fabric capacity is required", it refers to the set of resources available at a given time to be used. Different items consume capacity at different times, and the capacity an organization has defines how a resource can perform an activity or produce output from an activity. A single tenant can have one or more capacities, through Fabric SKUs or Fabric Trials.
The Power BI Admin role in Microsoft 365 will transition to Fabric Admin. While an admin may work primarily in the Fabric admin portal, other tools can be used to manage Fabric:
- PowerShell cmdlets
- Admin APIs and SDKs
- Admin monitoring workspace (created automatically when initiating a Fabric Trial)
- Microsoft 365 admin center (managing users and the licenses assigned to users)
I also learned more about promoting and certifying content. Content endorsement is an essential part of governance, and to me with my background being SMB (Small & medium-sized businesses), some of the best practices I could see not being strictly followed for this. The concept of having a group of users in the organization that "review and endorse content" does not align with smaller companies where the team that performs the data modelling or prepares content might be counted on one hand. Still, there would be ways to ensure that content is validated and trusted, even if the process in a smaller company is less rigorous.
- Promoted content can be promoted by contributors or admins so the barrier to entry is relatively low.
- Certified content generally implies an independent review of the content and only admins can "certify" content.
