Microsoft Power Platform PowerShell modules allow administrators to automate and manage Power Apps, Power Automate, and Dataverse efficiently. This guide covers the installation, authentication, and configuration of PowerShell for Power Platform.
1️⃣ Prerequisites
✔ Windows 10/11 or Windows Server
✔ PowerShell 7.x (Recommended)
✔ Administrator Permissions
✔ Global Admin, Environment Admin, or Power Platform Admin roles
2️⃣ Installing Power Platform PowerShell Modules
To install the required PowerShell modules, follow these steps:
🔹 Install the Power Platform Administration Module
Install-Module -Name Microsoft.PowerPlatform.Administration -Scope CurrentUser
✔ Used for managing environments, settings, and security.
🔹 Install the Power Platform Dataverse (CDS) Module
Install-Module -Name Microsoft.PowerPlatform.Cds.Client -Scope CurrentUser
✔ Enables interaction with Dataverse (CDS).
🔹 Install the Power Apps Administration Module
Install-Module -Name Microsoft.PowerApps.Administration -Scope CurrentUser
✔ Allows management of Power Apps environments and security.
🔹 Install the Power Apps Management Module
Install-Module -Name Microsoft.PowerApps.PowerShell -Scope CurrentUser
✔ Provides commands for managing apps and flows.
3️⃣ Updating Power Platform PowerShell Modules
Keep modules updated for the latest features and security fixes:
Update-Module Microsoft.PowerPlatform.Administration
Update-Module Microsoft.PowerPlatform.Cds.Client
Update-Module Microsoft.PowerApps.Administration
Update-Module Microsoft.PowerApps.PowerShell
4️⃣ Importing Power Platform Modules
After installation, import the modules into the PowerShell session:
Import-Module Microsoft.PowerPlatform.Administration
Import-Module Microsoft.PowerPlatform.Cds.Client
Import-Module Microsoft.PowerApps.Administration
Import-Module Microsoft.PowerApps.PowerShell
✔ Note: Import happens automatically when you run a command.
5️⃣ Authenticating to Power Platform
🔹 Interactive Authentication
Add-PowerAppsAccount
✔ Opens a sign-in prompt for authentication.
🔹 Service Principal Authentication (For Automation)
$ClientId = "Your-App-ID"
$ClientSecret = "Your-Secret"
$TenantId = "Your-Tenant-ID"
$SecureSecret = ConvertTo-SecureString $ClientSecret -AsPlainText -Force
$Credential = New-Object System.Management.Automation.PSCredential ($ClientId, $SecureSecret)
Add-PowerAppsAccount -Username $ClientId -Password $SecureSecret -TenantId $TenantId
✔ Ideal for scheduled tasks and CI/CD automation.
6️⃣ Verifying Connection to Power Platform
Run the following command to verify access:
Get-AdminPowerAppEnvironment
✔ Returns a list of available Power Platform environments.
7️⃣ Configuring PowerShell Execution Policy (If Needed)
If you encounter execution policy restrictions, modify the policy:
Set-ExecutionPolicy RemoteSigned -Scope CurrentUser
✔ Ensures PowerShell can execute signed scripts.
8️⃣ Uninstalling Power Platform PowerShell Modules
To remove the modules, run:
Uninstall-Module Microsoft.PowerPlatform.Administration
Uninstall-Module Microsoft.PowerPlatform.Cds.Client
Uninstall-Module Microsoft.PowerApps.Administration
Uninstall-Module Microsoft.PowerApps.PowerShell