Org Deployment and Lockdown

This page is for users and consultants who operate in centrally managed environments (restricted modes, governance, and shared defaults).

Modes (what users experience)

Ask the LLM: “What mode is this MCP server running in, and what does that mean for what we can do?”

You want to…	Full	Read-only	Browse-only
Connect to a model/dataset	Available	Available	Available
Browse schema / search metadata	Available	Available	Available
Run DAX queries	Available	Available	Not available
Refresh	Available	Available (if enabled)	Not available
Edit schema/measures/security	Available	Not available	Not available

In some environments, Power BI Service connectivity can be enabled/disabled centrally. If you can’t list/connect to Service datasets, ask:

“Is Service (XMLA) connectivity enabled in this environment? If not, what’s the approved way to enable it?”

Policy guardrails

Some environments enforce policy rules that the LLM cannot override, even if the user asks. In practice, this means your org can:

Block the LLM from deleting tables, measures, or relationships - the assistant physically cannot execute the delete, regardless of how the request is phrased.
Require confirmation before renames or schema changes - the assistant must pause and ask you to approve before proceeding.
Enforce metadata standards - for example, require that every new measure includes a description and a dynamic format string before the operation is allowed.
Restrict bulk operations - allow single-item edits but block batch changes to prevent large-scale accidental damage.

Ask the LLM: "Before doing anything risky, check whether policy requires confirmation or blocks it."

Some orgs deploy an admin-owned policy bundle that:

From a user perspective: if the assistant says policy edits are locked, you’ll need an administrator to update the bundle.