Add Power Apps Permission Errors in Entra ID to refer in PnP PowerShell
Summary
- Error
AADSTS650057 Invalid resourceoccurs whenhttps://service.powerapps.comisn’t included in the app registration permissions forPnP.PowerShell. - Fix by adding the Power Apps Service API with user delegated permission in Entra ID.
- Optional: add the permission through the app manifest with
requiredResourceAccess.
Symptom
If https://service.powerapps.com from the entra ID used in PnP PowerShell is missing, you’ll see an error similar to:

Get-PnPPowerApp: AADSTS650057: Invalid resource. The client has requested access to a resource which is not listed in the requested permissions in the client’s application registration. Client app ID: 94c967d3-9a15-48bd-80f5-457b6fa9ba19 (PnP.PowerShell). Resource value from request: https://service.powerapps.com. Resource app ID: 475226c6-020e-4fb2-8a90-7a972cbfc1d4.
Fix: Add Power Apps Service API Permission
- Open Entra ID → App registrations → locate
PnP.PowerShell(or your client app). - Go to API permissions → Add a permission → APIs my organization uses.
- Search and select “Power Apps Service”.

- Choose “Delegated permissions” (User delegated) and click Add.

- Admin consent may not be required for this scope; grant consent only if your tenant requires it.

Alternative: Add via Manifest
In the app registration manifest, add the following under requiredResourceAccess:
"requiredResourceAccess": [
{
"resourceAppId": "475226c6-020e-4fb2-8a90-7a972cbfc1d4",
"resourceAccess": [
{
"id": "0eb56b90-a7b5-43b5-9402-8137a8083e90",
"type": "Scope"
}
]
}
]
Verify
- Open a new session and re-run your PnP PowerShell command (e.g.,
Get-PnPPowerApp). The error should be resolved.