Empower data owners and administrators with precise control over which data Copilot can access and use for responses. This ensures sensitive or irrelevant information isn't inadvertently shared or processed.
A centralized system allowing data responsible persons/admins to set clear controls at three key levels:
- Capacity Level: Define broad default settings or hard exclusions for entire data capacities.
- Workspace Level: Override or refine capacity-level policies for specific workspaces.
- Item Level: Provide the finest control, allowing direct inclusion or exclusion of individual items (semantic model, eventhouse, etc.) from Copilot's scope.
Key Benefits:
- Enhanced Trust & Compliance: Users and organizations gain confidence knowing data usage is controlled, meeting privacy and regulatory standards.
- Reduced Risk: Prevents Copilot from using sensitive, outdated, or inappropriate data.
- Empowered Data Owners: Puts control directly into the hands of those who understand the data best.
1 Comment
- We have restricted data on the tenant. This can’t be presented to GenAI. Please provide a project, workspace, item level override which can be controlled by Tenant Admins and automated via an API. Even more powerful - make it a DLP policy that Copilot honors. As a Tenant Admin - I’d like 100% control. Not delegated to Capacity Admins, Domain Admins and Workspace Admins. Also please consider a Certified for AI which is above Ready for AI or Prepped for AI. We’d want an Entra Security Group to approve the labeling. Honoring Sensitivity Labels is a must-have. default everything to No AI so that permission is granted by Governance.
Recent ideas
executeDaxQueries-like API call with effectiveUserName on SSO-enabled model with Service Principal
Please provide a way for a service principal to execute DAX - with an effective user name - against an SSO-enabled directlake semantic model and get per-user results that respect lakehouse OneLake Se...
