Scenario - customer wants to allow specific workloads in the tenant, disabling the rest. for example, allow only Power BI and OneLake / Data engineering but disable data science, RTI etc till they are individually approved by security & compliance team.
While Fabric technically unifies various product capabilities, software compliance assessment teams may not treat them all as single unit. For example, ability to ingest data vs visualizing approved dataset have different level implications on the data security posture.
By allowing selected workload deployment, adoption can begin faster, without waiting for all workloads/capabilities are approved.
The concept extends further to feature level. Security compliance team may take much longer to approve AI or data sharing features than reporting or data warehousing feature, considering org-wide policy status and risk assessment criteria differences across these capabilities.
Idea: (1) Ability to disable a Fabric workload at tenant / capacity level (2) Ability to turn off/on features
on:
Accelerate ontology adoption with out-of-the-box i...
on:
DO NOT CONVERT my Workspace to Fabric Free Trial W...
on:
MS Fabric: Manage Connections and gateways with Fo...
on:
CU% over time: Filter by workspace (Capacity Metri...
YSD
on:
Support the SSE protocol as Fabric Eventstream sou...