Chapter 3 of 6 · Before you start

Microsoft Fabric and Microsoft Purview governance for AI data

Optional module · Draft 7 hours

Chapter 3 of 6

Confirm these requirements:

  • One approved nonproduction Fabric workspace contains the gold lakehouse used for grounding.
  • The Fabric workspace runs on a Fabric or Premium capacity that supports the planned Fabric DLP scope.
  • The Fabric administrator can read tenant settings and operate OneLake security roles for the selected lakehouse.
  • The Microsoft Entra AI consumer group and restricted consumer group are known and approved.
  • The Purview operator can apply the selected sensitivity label and create a Fabric DLP policy in simulation mode.
  • The delivery owner can observe a permitted consumer identity and a restricted consumer identity.
  • PowerShell operators use PowerShell 7 or later for the module scripts.

Use group aliases in the artifacts. Keep tenant IDs, object IDs, live query output, prompts, responses, access tokens, and customer data in the approved customer system.

Implementation files#

TypeFileConsumer
Recordartifacts/fabric/tenant-settings-baseline.jsonThe Fabric administrator and tenant-settings drift check scripts
Deploymentartifacts/fabric/onelake-ai-consumer-role.jsonThe Fabric administrator and OneLake access verification scripts
Recordartifacts/purview/fabric-label-dlp-decision.jsonThe Purview operator and data product owner
Recordartifacts/verification/access-check-plan.jsonThe delivery owner and AI application owner

Resolve every __REQUIRED_*__ value before a service change. The preflight scripts reject each unresolved value and stop before any Fabric or Purview call.

Optional module

Microsoft Fabric and Microsoft Purview governance for AI data slide deck