Skip to content

Power Platform AI credits

Power Platform contributes per-environment credit-consumption context for AI features administered through the Power Platform admin center.

Onboarding scope

This guide covers the read-only power_platform connector in the Venturi platform connector package. It reads environment inventory and credit consumption and never creates environments, changes apps, or reallocates capacity.

Meters

Microsoft meters Power Platform AI consumption in two units, and the connector labels each row with the meter it came from:

  • Copilot Credits: consumption by Copilot Studio agents, agent flows, and AI features billed to Copilot Studio capacity, reported per environment in the Power Platform admin center under Licensing → Copilot Studio.
  • AI Builder credits: AI Builder capacity from the AI Builder add-on and from credits seeded in some Power Apps and Power Automate licenses. Microsoft no longer sells the add-on to new customers, who purchase Copilot Credits instead. After November 1, 2026, Microsoft removes seeded credits and only add-on credits remain active.

Tenants that move from AI Builder credits to Copilot Credits keep one continuous per-environment series. See Microsoft’s Copilot Credits capacity management and AI Builder credit management.

Required access

The names below are Venturi capability identifiers, not Microsoft OAuth scopes:

Venturi capability Purpose
PowerPlatform.Admin.Read Read admin consumption views.
Environment.Read.All Read environment context.
Analytics.Read Read analytics rows for usage attribution.

Do not grant environment creation, app mutation, or admin write permissions.

The vendor-side authorization is a Microsoft Entra app registration for the Power Platform API whose service principal holds the Power Platform reader role, which Microsoft defines as read-only access to all resources. Assign the role at tenant scope through Power Platform role-based access control; Microsoft documents role assignment for service principals as a preview feature. Do not register the app as a Power Platform management application (New-PowerAppManagementApp): Microsoft gives such an application the same permissions as a tenant administrator, and they cannot be narrowed. See Microsoft’s Power Platform API authentication, role assignment for service principals, and management application registration. The connector never sends the capability names above to Microsoft.

Setup

  1. Create a dedicated app registration and service principal in your Microsoft Entra tenant.
  2. Assign the service principal the Power Platform reader role at tenant scope.
  3. Store the certificate or client secret as an encrypted credential reference in Settings / Admin / Credentials.
  4. Configure VENTURI_POWER_PLATFORM_TENANT_ID; set VENTURI_POWER_PLATFORM_API_BASE only for a non-default cloud. The default lookback is 30 days; set VENTURI_POWER_PLATFORM_LOOKBACK_DAYS to change it. See sync windows and failure behavior.
  5. In Venturi, go to Integrations / Power Platform and run Test connection.

Verification

  • Test connection passes the read-only boundary check: environment and consumption reads succeed, and the service principal holds only the Power Platform reader role.
  • Consumption rows appear with environment, agent, or user context where the admin center exposes it, labeled with their meter.
  • The connector inventory marks the connector as read-only.

Rotation and offboarding

Rotate the app credential through Microsoft Entra administration, then update the credential reference in Settings / Admin / Credentials. Removing the connector stops new Power Platform AI credit syncs; also remove the role assignment.

Give feedback on this page

Sign in to send feedback. Opens in a new tab.

Copy page details 
Docs feedback: Power Platform AI credits
Page: https://docs.venturi.systems/connectors/power-platform/