Microsoft Fabric for the Platform Administrator (DBA)
Applying the correct governance to your data products. Capacities, Workspaces, and Domains
Course Overview
In this workshop, we will explore the administration of Microsoft Fabric, with a focus on the organisation and management of data storage/compute through the configuration of capacities, domains, data products, environments and workspaces. We will discuss the application of data mesh and data fabric concepts in the context of Microsoft Fabric capabiltities, including organising data products for effective delivery to business users.
Additionally, we will demonstrate how to use domains and separate workspaces to serve reports to business users, providing them with the information they need to make informed decisions. Aligning industry governance standards to Microsoft Fabric features and access controls. Join us to learn how to effectively administer Microsoft Fabric beyond the simple Workspaces inherited from Power BI.
Course Objectives
o Should we separate our environments (dev, test, prod) using a set of Microsoft Fabric Workspaces, one Workspace per Environment?
o Should the data product be defined as everything across all environments to deliver a given use case or solution in Microsoft Fabric, is this natural?
o Should we further separate our Microsoft Fabric Workspaces based on the "medallion architecture" methodology, with alignment to the respective bronze, silver, gold storage containers?
o Should only our development environment Workspace be connected to source control?
o Should we have all Workspaces connected to the same source control repository for all environments and use a complex code branching strategy vs environments, meaning branch merging becomes our method of deployment?
o Should a business domain encompass all data products and all environments?
o Should we use sub domains to separate production and non-production environments, or some other classification?
o Should Capacities (compute) be aligned to environments, data products, sub domains or business domains, or something else? Maybe the whole tenant?
o Should we use trial capacities for our development environment, creating new trials as required?
o Should a role based access model be implemented at every level in this hypothetical hierarchy and if so, what roles? Experience reader, Workspace contributor, One Lake reader.
o Should data plane and control plane personas be separated for the production environments?
o Should we organise our folders in a Workspace based on the type of Experience Items created?
o Should we have one big capacity covering all parts of the solution, with dev and prod workloads sharing compute?
Training Format
• 1 Day Course
• All Training Materials Provided
• Mixed Theory, Labs and Debate
• Emerging Patterns
Technology Covered
Notes
Ideal with existing database administrators (DBAs) now needing to support Microsoft Fabric as a technology.