This page describes AAES Govern’s controls. AAES Operate has private-work permissions, operational reviews and recorded-spend limits; it does not include Govern. About AAES Govern
Before you enable this package
Keep api.powerbi.com and bind GROUP_ID, DATASET_ID and REPORT_ID. Verify access to the selected workspace and objects.
Read each action's effects and exclusions below. Before installation, also read the complete package requirements, including credential issuance, scope, expiry, and provider permissions. These are deployment prerequisites, not capabilities this package supplies.
Capabilities (7)
Each capability below is one registered operation. The complete package JSON includes its exact network destination allowlist. The repository stores it at packs/powerbi.json and embeds a copy in the release binary.
Risk tiers. R0 is the minimum for reads. R2 is the minimum for write, create, update, execute, and invoke. R3 is the minimum for delete, send, pay, deploy, approve, share, and transfer. Operators can raise these levels. R4, the highest tier, always requires two distinct verified people and step-up, and policy cannot lower it. A minimum tier does not measure the operation's business or confidentiality risk.
On supported execution paths routed through AAES Govern, the R3 actions listed below require approval by an authorized person. Bypass paths and observation-only registrations are outside that guarantee. A provider's restoration feature does not remove this approval requirement. A provider-side approval, such as approving a GitLab merge request, is also separate from AAES Govern human approval. The capability matrix shows which execution paths are implemented, restricted to lab use, or refused at startup. Live compatibility must be tested in your environment.
Field guide. Endpoint is the service address and request method. Connector is the adapter that makes the call. Custody describes how the credential is held; the credential reference identifies the value to resolve. Data class sets handling requirements: pii means personal data, financial means financial records, and internal means internal organizational data.
Returned data. Brokered execution defaults to a response digest and discards the body. Returning HTTP content needs a reviewed registration with bounded results, content-type and size limits, and any required data-owner acknowledgement. These packages do not configure that path. Bounded HTTP results do not support SQL, email or telephony.
Cost controls. A registered ceiling reserves budget; it does not cap the provider bill. Purchases and agreements stay refused by default. Money execution needs a reviewed binding to the actual rail request. Customer metered execution is currently disabled. Activation requires a reviewed release change and the matching verifier. After activation, an independent administrator sets the ceiling and another person approves. Any money binding still applies.
powerbi.datasets.read v1.0.0R0
- Kind
- tool
- Action
- read
- Endpoint
GET https://api.powerbi.com/v1.0/myorg/groups/GROUP_ID/datasets- Connector
- http
- Custody
- customer_vault
- Credential ref
secret-ref-powerbi-bearer-token- Data class
- internal
Read datasets.
List the datasets in one workspace (Get Datasets In Group); this pack registers the collection read only — Get Dataset In Group and the datasources/parameters sub-reads are not registered. Microsoft's documentation notes that a caller with only Read permission receives a limited subset of dataset properties — a documented API behavior, not a restriction this pack imposes.
GROUP_ID is a placeholder the deployment binds before enabling; api.powerbi.com is a real shared service host and is not substituted.
powerbi.dataset.execute_queries v1.0.0R0
- Kind
- tool
- Action
- read
- Endpoint
POST https://api.powerbi.com/v1.0/myorg/groups/GROUP_ID/datasets/DATASET_ID/executeQueries- Connector
- http
- Custody
- customer_vault
- Credential ref
secret-ref-powerbi-bearer-token- Data class
- internal
Run dataset queries.
Run read-only DAX queries against one dataset (Execute Queries In Group). Send one DAX query for one result table. Inspect response errors and completeness: HTTP 200 can contain limited data. Microsoft caps results at 100,000 rows or 1,000,000 values and 15 MB, whichever limit is reached first. AAES bounded HTTP results have a separate, smaller configured byte limit. The call changes no workspace data and is registered as read at R0.
The registration does not restrict DAX text. The caller can query any content accessible in the dataset; classify and handle the results according to that content.
The tenant administrator must enable Dataset Execute Queries REST API under Integration settings. The caller needs both Read and Build permissions. Service principals cannot use this operation with datasets that have row-level security or SSO-enabled data sources; those datasets reject this package's service-principal credential.
Bind GROUP_ID and DATASET_ID before enabling.
powerbi.dataset.refresh_history.read v1.0.0R0
- Kind
- tool
- Action
- read
- Endpoint
GET https://api.powerbi.com/v1.0/myorg/groups/GROUP_ID/datasets/DATASET_ID/refreshes- Connector
- http
- Custody
- customer_vault
- Credential ref
secret-ref-powerbi-bearer-token- Data class
- internal
Read dataset refresh history.
List the refresh history of one dataset (Get Refresh History In Group): refresh ids, types, start and end times and statuses — operational metadata about past refreshes, registered as a collection read.
GROUP_ID and DATASET_ID are placeholders the deployment binds before enabling; api.powerbi.com is a real shared service host and is not substituted.
powerbi.dataset.refresh v1.0.0R3
- Kind
- tool
- Action
- deploy
- Endpoint
POST https://api.powerbi.com/v1.0/myorg/groups/GROUP_ID/datasets/DATASET_ID/refreshes- Connector
- http
- Custody
- customer_vault
- Credential ref
secret-ref-powerbi-bearer-token- Data class
- internal
Refresh dataset.
Refresh one dataset (Refresh Dataset In Group). The refresh reads underlying sources and replaces the data served by dependent reports and dashboards. It is registered as deploy at R3 because it changes published content.
An empty body or one containing only notifyOption requests a standard refresh. Any other field requests an enhanced refresh. With commitMode=partialBatch, failure can leave the model partly loaded or a table empty; Microsoft recommends transactional to preserve previous data.
Shared capacities allow at most eight refreshes per day. These are provider limits, rather than controls imposed by this registration. Bind GROUP_ID and DATASET_ID before enabling.
On supported execution paths mediated by AAES Govern, the deploy action requires approval by an authorized person; this does not prevent calls through bypass or observation-only paths.
powerbi.dataset.delete v1.0.0R3
- Kind
- tool
- Action
- delete
- Endpoint
DELETE https://api.powerbi.com/v1.0/myorg/groups/GROUP_ID/datasets/DATASET_ID- Connector
- http
- Custody
- customer_vault
- Credential ref
secret-ref-powerbi-bearer-token- Data class
- internal
Delete dataset.
Delete a dataset from the workspace (Delete Dataset In Group). Every report and dashboard tile built on the dataset loses its data connection, and recreating the dataset later is a new artifact, not an undo. Registered as delete at the minimum R3 tier; delete is one of the designated actions requiring human approval.
GROUP_ID and DATASET_ID are placeholders the deployment binds before enabling.
powerbi.report.delete v1.0.0R3
- Kind
- tool
- Action
- delete
- Endpoint
DELETE https://api.powerbi.com/v1.0/myorg/groups/GROUP_ID/reports/REPORT_ID- Connector
- http
- Custody
- customer_vault
- Credential ref
secret-ref-powerbi-bearer-token- Data class
- internal
Delete report.
Delete a report from the workspace (Delete Report In Group). Dashboards pinning its visuals and anyone consuming the report lose it; the documented success response is 200 with no recoverable artifact returned. Registered as delete at the minimum R3 tier; delete is one of the designated actions requiring human approval.
GROUP_ID and REPORT_ID are placeholders the deployment binds before enabling.
powerbi.group.user.add v1.0.0R3
- Kind
- tool
- Action
- share
- Endpoint
POST https://api.powerbi.com/v1.0/myorg/groups/GROUP_ID/users- Connector
- http
- Custody
- customer_vault
- Credential ref
secret-ref-powerbi-bearer-token- Data class
- pii
Add users to a workspace.
Grant a principal access to a workspace (Add Group User). The body identifies the principal with identifier or emailAddress and assigns groupUserAccessRight: Viewer, Contributor, Member, or Admin. These identifying fields are personal data.
The grant covers everything in the workspace and lasts until a separate removal call. The unrestricted body permits Admin access. Enforce any viewer-only restriction in policy. Microsoft's documented permission propagation can take time; this registration imposes no timing guarantee.
Registered as share at R3. Bind GROUP_ID before enabling.
Credential reference
The credential field names a reference rather than containing credential material. Packs are designed not to contain secrets; the format checks cover only known credential formats and cannot prove that arbitrary text contains no secrets. Installing a package registers its capabilities. Configure the provider credentials, endpoints, and network access, then test the integration in your environment before enabling it.
- Reference
secret-ref-powerbi-bearer-token- Custody
- customer_vault
- Injection
- header (Authorization)
Configure the value and injection format specified in the package. Assign responsibility for credential rotation and revocation, restrict provider permissions, and keep credential material out of logs and responses.
Complete credential requirements
A Microsoft Entra ID (Azure AD) access token for the Power BI API, held in the client's own secret manager. The stored material must be the complete Authorization header value: the scheme 'Bearer', one separating space, then the access token. Token issuance is external: the deployment's custody job obtains tokens from the Microsoft identity platform token endpoint (login.microsoftonline.com/{tenant}/oauth2/v2.0/token) using a confidential client — a service principal authenticating with client credentials and requesting the single scope 'https://analysis.windows.net/powerbi/api/.default' — and writes the resulting token under this reference before expiry.
Service-principal authorization: for service principals Microsoft recommends assigning NO Power BI API permission scopes on the app registration — the documented scopes (Dataset.ReadWrite.All, Workspace.ReadWrite.All and similar) are DELEGATED permissions for signed-in-user flows and are never used by a client-credentials service principal, so this pack does not prescribe them as the SP's governing permissions. The service principal's real authorization is (1) the tenant setting 'Allow service principals to use Power BI APIs', which the tenant administrator must enable (optionally scoped to a security group containing the SP), and (2) a workspace role — Member or Admin for the write operations — on each workspace it governs; workspace assignment is the real blast-radius control.
Expiry and revocation: access tokens are short-lived (about an hour) and an expired value fails closed with a 401; the custody job must refresh proactively — the injector injects the stored value verbatim and performs no token lifecycle itself. Note carefully, distinguishing issuance from authorization: disabling the app registration stops NEW token issuance, but removing the service principal from a workspace does NOT block issuance — tokens keep being minted while the app registration lives, and workspace removal only means a (still bearer-valid) token's calls against that workspace fail authorization.
Already-issued tokens are never invalidated by either step and remain usable until they expire, so the token lifetime is the effective revocation window.
Least privilege: with no API scopes on the app registration, least privilege is exercised through workspace roles — add the service principal to only the workspaces this integration governs, with the minimum role that covers the enabled capabilities, and restrict the tenant setting's allowed security group to the group holding this SP.
Executor hygiene: the value must live only in executor memory for the lifetime of a call, must never be written to logs, traces or diagnostics, and must not appear in crash dumps; a deployment that cannot meet that bar must not enable the pack.
Resources
powerbi-workspace(api, internal):https://api.powerbi.com/v1.0/myorg/groups/GROUP_IDpowerbi-workspace-users(api, pii):https://api.powerbi.com/v1.0/myorg/groups/GROUP_ID/users
Technical package and review record
Complete provider requirements and exclusions
The endpoint host api.powerbi.com is a REAL shared service host — Microsoft's global Power BI API endpoint that serves every tenant — not a placeholder: do not substitute it, and do not treat its presence in the egress allowlist as an unsubstituted-pack marker. Tenant and data scoping come from the Microsoft Entra ID access token and the group (workspace) id in the path, not from the host.
GROUP_ID, DATASET_ID and REPORT_ID in the paths are placeholders the deployment binds to concrete workspace and artifact ids before enabling; the /v1.0/myorg prefix is Power BI's documented tenant-relative root, and the registered capabilities address workspace-scoped operations only (My Workspace variants of the same operations are not registered).
Approval classification: dataset refresh is registered with the deploy action at the minimum R3 tier rather than as an ordinary execution — a refresh rewrites the data every report and dashboard built on the dataset serves to its consumers, which is deploy-equivalent; deploy is one of the designated actions requiring human approval. Adding a principal to a workspace is registered as share at the minimum R3 tier: it grants a user, group or service principal a workspace role up to Admin, and the grant stays effective until a separate removal call.
Documented exclusions — this pack does not register: the Admin APIs (tenant-wide as-admin scans and metadata export — organization-wide surveillance scope, a separate governance review); Post Dataset User and Put Dataset User (direct dataset-level permission grants — share-class, pending review); Take Over In Group (transfers dataset ownership to the calling user — transfer-class); Bind To Gateway In Group, Update Datasources In Group and Set All Dataset Connections In Group (gateway binding and data-source credential operations — credential-adjacent writes requiring their own review); the push/streaming dataset row endpoints (PostRows and friends — direct row writes into datasets); report clone, export and import; dataflow refresh and transactions; and GenerateToken (embed-token issuance — a credential-issuance operation, not a business capability).
These operations are excluded. The Execute Queries capability is a POST-with-query-body endpoint used read-only: its body carries a DAX query and it changes nothing — see the capability's own note. Capacity behaviors documented by Microsoft are honest limits, not restrictions this pack imposes: shared capacities accept at most eight refreshes per dataset per day, and an enhanced refresh whose commitMode is partialBatch can leave the model partially loaded after a failure — Microsoft's own documentation advises transactional mode to preserve previous data.
Brokered execution defaults to digest mode: it records a response digest and discards the body. These schema-1 packs do not configure result delivery. Returning HTTP content needs a reviewed deployment registration with inline_bounded results, content-type and size limits, and any required data-owner acknowledgement. The bounded HTTP result path does not support SQL, email or telephony.
Download the complete package JSON for exact network allowlists, credential requirements, exclusions, and setup notes. Read these requirements before installation.
A paid, scoped evaluation includes the full review record in the evaluation package, which runs in your environment. This page shows the source links and review block. Discuss an evaluation to inspect the full record before installation.
Review block
This section reproduces the review block recorded in the pack file. The evidence and approval record is separate: for a reviewed pack, it is in the evaluation materials and in the release binary's embedded assets.
Review completed: 2026-09-22
9 sources, retrieved 2026-09-21
- https://learn.microsoft.com/en-us/rest/api/power-bi/datasets (retrieved 2026-09-21)
- https://learn.microsoft.com/en-us/rest/api/power-bi/datasets/get-datasets-in-group (retrieved 2026-09-21)
- https://learn.microsoft.com/en-us/rest/api/power-bi/datasets/refresh-dataset-in-group (retrieved 2026-09-21)
- https://learn.microsoft.com/en-us/rest/api/power-bi/reports/delete-report-in-group (retrieved 2026-09-21)
- https://learn.microsoft.com/en-us/rest/api/power-bi/groups/add-group-user (retrieved 2026-09-21)
- https://learn.microsoft.com/en-us/rest/api/power-bi/datasets/execute-queries-in-group (retrieved 2026-09-21)
- https://learn.microsoft.com/en-us/rest/api/power-bi/datasets/delete-dataset-in-group (retrieved 2026-09-21)
- https://learn.microsoft.com/en-us/rest/api/power-bi/datasets/get-refresh-history-in-group (retrieved 2026-09-21)
- https://learn.microsoft.com/en-us/power-bi/developer/embedded/embed-service-principal (retrieved 2026-09-21)
Current documentation links are navigation aids. They do not change the package, its historical sources or its review date. Review dates describe a documentation review, not a live integration test. No package is provider-endorsed.
Release identity
SHA-256 of the pack file bytes: 45ab25522003243902982ec51f6ccc234274ab0d7d0f147e5445e70849b2f586
Distributable: yes, digest matches the release manifest. Editing a package changes its release identity. A deployment plan checks its own file digests; it does not restore reviewed status or authenticate approval.
Use this package with AAES Govern
AAES Govern checks permissions, required approvals and spending limits for actions routed through its supported paths. Review the Govern integration documentation and the execution-path capability matrix before connecting an agent to Power BI.
The evaluation guide describes how to check the controls in your own environment. This package's documentation review does not establish live compatibility with your Power BI tenant.