We are using Azure DevOps Power Platform Build Tools (1.0.13) extension.
We are currently trying to use the following step : "Power Platform Backup Environment" and we would like to know when the feature using the service principal name will be available?
We're using at the moment a service account and the MFA is not supported with this authentication type.
We have read this documentation : https://docs.microsoft.com/en-us/power-platform/alm/devops-build-tool-tasks#power-platform-backup-en....
Do you have a narrower timeline for the availability of this feature ?
Many thanks in advance!
I was encoutering the same path error.
Actually the API permission needed can be set only trough API or powershell (not via Azure portal app registration):
"Today, there's no way to do this via the Power Platform admin center; it must be done programmatically via Power Platform API or PowerShell for Power Platform administrators. A service principal can't register itself—by design, the application must be registered by an administrator username and password context. This ensures that the application is created knowingly by someone who is an administrator for the tenant."
Follow the steps described here:
It took me 5min to set it.
You have to be admin on powerapps.
1) create an app registration on Azure, note its appID
2) install powershell powerapps module if not done
3) run this script (just change yourappID parameter, nothing else)
You have to login as an admin of the targeted powerapps env.
$appId = "yourappID"
# Login interactively with a tenant administrator for Power Platform
Add-PowerAppsAccount -Endpoint prod -TenantID $tenantId
# Register a new application, this gives the SPN / client application same permissions as a tenant admin
New-PowerAppManagementApp -ApplicationId $appId
The first Microsoft-sponsored Power Platform Conference is coming in September. 100+ speakers, 150+ sessions, and what's new and next for Power Platform.
Join us for two optional days of workshops and a 3-day conference, you can choose from over 130 sessions in multiple tracks and 25 workshops.