I am getting this error while publishing all customizations

(2) Share

Report

Posted on by SJ-26120454-0

I am getting this error while publishing all customizations :

Commands.Publish failed: Principal user (Id=676d28bd-78b8-ef11-b8e8-0022485c31af, type=8, roleCount=2, privilegeCount=1238, accessMode='0 Read-Write', AADObjectId='0988c723-489d-4d69-8cdf-db7f507ab081', MetadataCachePrivilegesCount=10577, businessUnitId=2617e7a5-9e84-ef11-ac21-6045bd16e056), is missing prvReaduxagentproject privilege (Id=06a545ba-4396-48a5-98ee-42b0f8a56f71) on OTC=11417 for entity 'uxagentproject' (LocalizedName='UX Agent Project'). context.Caller=676d28bd-78b8-ef11-b8e8-0022485c31af. Consider adding missed privilege to one of the principal (user/team) roles.

Categories:

Power Apps Pro Dev & ISV

I have the same question (0)

All responses (3)

Answers (0)

Suggested answer

Valantis 1,971 on at

Like (2)

Report
Copy link

Link copied!

Hi @SJ-26120454-0,

you are missing prvReaduxagentproject (Read) privilege on the Dataverse table(entity) uxagentproject.

Best regards,

Valantis

✅ If this helped solve your issue, please Accept as Solution so others can find it quickly.

❤️ If it didn’t fully solve it but was still useful, please click “Yes” on “Was this reply helpful?” or leave a Like :).

🏷️ For follow-ups @Valantis.

📝 https://valantisond365.com/

Was this reply helpful? Yes No
Suggested answer

11manish 459 on at

Like (0)

Report
Copy link

Link copied!
Root Cause (why this happens)

In Microsoft Dynamics 365 / Microsoft Dataverse, this error:

missing prvReaduxagentproject privilege

means:

Your user does not have read access to the uxagentproject (UX Agent Project) table

This table is related to Copilot / Agent (bot) features

Important insight

Even if:

You removed bots/agents from your solution

The environment still has:

Metadata / dependencies related to Copilot agents

System components referencing uxagentproject

During Publish All Customizations, the system tries to:

Validate ALL metadata (not just your solution)

How to fix (best options)

Option 1: Add missing privilege (FASTEST FIX)

Ask admin to update your security role:

Go to Security Roles

Add Read permission for:

UX Agent Project (uxagentproject)

Or simply assign:

System Administrator (temporary test)

Option 2: Add Copilot/Agent related role

If your org uses Copilot:

Assign role like:

Copilot User / Agent related role (if available)

Option 3: Clear hidden dependencies

Check if any components still reference agents:

Forms

App modules

Site map

Environment features

Remove any leftover references

Option 4: Publish using elevated role (recommended practice)

Use a deployment/admin account

With full privileges

Avoids such permission issues

Was this reply helpful? Yes No
Kalathiya 1,572 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hello @SJ-26120454-0,

Usually this error comes up because your user doesn’t have permission to read one of the tables involved in the publish process. In your case, the missing privilege is Read access for the “UX Agent Project” (uxagentproject) table. When you click “Publish All Customizations,” the system tries to access all entities and if even one is restricted, it fails.

To fix it, just go to your Security Roles, open the role assigned to your user, find UX Agent Project, and give it at least Read permission. Save it and publish again and try again.

If you want a quick workaround, you can temporarily assign yourself the System Administrator role. Since this role has full access to all table so you will not face any issue during the solution publishing.

If this response resolves your issue, please mark it as the Verified Answer so it can help other community members as well.

---------------------------------------------------------------------------------

📩 Need more help? Just mention @Kalathiya and I’ll be happy to assist.

✔️ If this answer helped you, please tick “Does this answer your question?” so it can be marked as the Verified Answer.

💛 A Like always motivates me to keep contributing!

Was this reply helpful? Yes No