Get started with PowerShell for Power Platform Administrators
PowerShell for Power Platform Administrators cmdlets are designed for managing and administering Microsoft Power Platform environments, Power Apps, and Power Automate flows. Use PowerShell for Power Platform Administrators when you want to build automated tools that interact with these resources.
This article helps you get started with the PowerShell module and teaches the core concepts behind it.
The easiest way to get started with the PowerShell module is by installing it on your local machine. Follow the instructions in Installation to import the module, or to update an outdated version you might have installed previously.
Sign in to Microsoft Power Platform
Sign in interactively with the Add-PowerAppsAccount cmdlet.
Add-PowerAppsAccount -Endpoint prod
Alternatively, you can sign in with a client ID and secret or certificate. To do this, you will need to Create a service principal.
$appId = "CLIENT_ID_FROM_AZURE_APP" $secret = "SECRET_FROM_AZURE_APP" $tenantId = "TENANT_ID_FROM_AZURE_APP" Add-PowerAppsAccount -Endpoint prod -TenantID $tenantId -ApplicationId $appId -ClientSecret $secret -Verbose
To perform the administration operations in the cmdlets, you'll need the following:
Any of these roles from Azure Active Directory, Tenant admin, Power Platform administrator, Dynamics 365 Service Administrator, can access the Power Apps admin PowerShell cmdlets. These roles no longer require a Power Apps plan for administrative access to the Power Apps admin PowerShell cmdlets. However, these administrators need to sign in to the Power Platform admin center at least once before using the PowerShell cmdlets. If this is not done, the cmdlets will fail with an authorization error.
Microsoft 365 Global admin, Azure Active Directory Global Administrator, Power Platform administrator, or Dynamics 365 administrator permissions are required if you need to search through another user's resources. Note that environment admins only have access to those environments and environment resources for which they have permissions.
For Dataverse for Teams environments, you must be either a Microsoft 365 Global Admin, Azure Active Directory Global Administrator, or Power Platform Administrator to manage environments from which you are not the owner of the team in Microsoft Teams.