Answered

Principal user is missing prvReadCanvasAppExtendedMetadata privilege for entity 'canvasappextendedmetadata'

(1) Share

Report

Posted on by vammers

Hello,

We have been deploying our solutions via azure release pipelines and power platform build tools into various environments. During a release today we started getting the error Principal user (Id=GUID, type=8, roleCount=1, privilegeCount=1209, accessMode=4) is missing prvReadCanvasAppExtendedMetadata privilege for entity 'canvasappextendedmetadata'.

We were able to release to this environment many times via release pipes without this issue before.

Also, we were not able to find any user / app registration or service principal with that guid in the environment and in our Azure AD.

Categories:

Power Apps Pro Dev & ISV

I have the same question (0)

All responses (2)

Answers (1)

Sort by

vammers 31 on at

Like
a
(0)

Report
Copy link

Link copied!

We fixed the issue ourselves.

As part of creating the release pipelines for various environments, we had created a Service application connection to each of the power platform environments. Created a new security role called DEVOPSIntegration as a copy of system administrator role and assigned the user to this role. Not sure how the permissions got changed ( the page to update custom entities probably needs a revisit from the MS Team) but they were misaligned to what the System admin role had in TEST and UAT environments (DEV and Prod were ok). Once we deleted the security role and re copied the permissions from system admin role, the deployments are all fine now.

Was this reply helpful? Yes No
Verified answer

shaboo 65 on at

Like
a
(0)

Report
Copy link

Link copied!

Solution;

We have same issue introduced part of our recent deployment. The app was working fine previously without assigning read privilege on "CanvasAppExtendedMetadata". The strange thing i have noticed we have two canvas apps one of which working as usual where as the other app thrown an error the App ID not found in tenant, the issue might be introduced part of the form deployed in the canvas app embeded.

Solution: Add a read privilege on "CanvasApp Extended Metadata" entity under custom entities which resolve the issue.

Was this reply helpful? Yes No