Agent Administration

(2) Share

Report

Posted on by CU05110824-0

I create an agent in copilot studio. I share my agent only to user A B C D E. I have published my agent to teams channel. I copy a link I get from picture 1 and send it to teams conversation user A B C D E because user A B C D E still cannot access agent from built with power platform (picture 2) although I have shown it to my teammates and shared users (picture 1). User A B C D E have re-logged in but agent still cannot be accessed from built with power platform. I have some scenarios.

1. Is it possible if I want to remove permission from user E and uninstall agent from teams user E?

2. If yes, is it possible that at some point in the future I want to re-add permission to user E and re-install agent in teams user E?

How to do that?

Categories:

Bot administration

Bot extensibility

Publish & channel management

I have the same question (0)

All responses (7)

Answers (0)

Suggested answer

Valantis 2,506 on at

Like (1)

Report
Copy link

Link copied!

Hi @CU05110824-0,

For the Built with Power Platform not showing for shared users this is a known propagation delay. It can take time to appear after sharing. Also make sure Power Platform apps are allowed in Teams by your admin, otherwise the section stays empty for users even when shared correctly.

Check Teams Admin Center > Manage Microsoft Power Platform apps.

For your two questions:
1. Yes you can remove User E. Go to Copilot Studio > your agent > Share, remove User E from the shared users list and save.

This removes their access. If you also want to uninstall it from their Teams, note that removing sharing does not auto-uninstall it for users who already installed it. User E would need to manually uninstall it from Teams, or you can use PowerShell to remove it remotely.

2. Yes you can re-add User E later. Just go back to Share, add them again, and share the installation link. They can reinstall it in Teams from the Built with Power Platform section or via the link.

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

AP-26031104-0 Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

@CU05110824-0,

Just wanted to check — was the issue with the “Built with Power Platform” not showing for shared users eventually resolved on your side after the propagation delay?

Also, did you need to make any additional changes (e.g., in Teams Admin Center or permissions) to fix it, or did it start working automatically after some time?

Appreciate your clarification!

Was this reply helpful? Yes No
CU05110824-0 38 on at

Like (0)

Report
Copy link

Link copied!

Hi @AP-26031104-0

No, it still does not show for shared user even after the change of day.

Was this reply helpful? Yes No
CU05110824-0 38 on at

Like (0)

Report
Copy link

Link copied!

Hi @Valantis

I have used PowerShell to remove it remotely with this code

Remove-MgUserTeamworkInstalledApp UserId $UserId UserScopeTeamsAppInstallationId $InstallationId

But I cannot re add user E

I have re-shared my agent to user E and share the link to user E in teams, but it returns an error "Your app package failed the validation" (Manifest parsing error message unavailable)

I even try to create new agent and share it to user E but it still returns the same error "Your app package failed the validation" (Manifest parsing error message unavailable)

But when I share the new agent to user A (for example), it works well without any error

Does it relate to the power shell code I used before?

Was this reply helpful? Yes No
Suggested answer

AP-26031104-0 Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!
CU05110824-0

The issue with User E failing to reinstall the Copilot Studio agent in Teams is caused by residual app metadata after using PowerShell to remove the app. To resolve:

Steps to fix:

Clear Teams cache on User E’s machine:

Close Teams completely

Delete %appdata%\Microsoft\Teams\Application Cache\Cache, Blob_storage, IndexedDB, Local Storage, tmp

Restart Teams and log in

Optionally, bump agent version in Copilot Studio and re-share the updated link to avoid manifest conflicts.

Alternatively, reinstall via PowerShell:

New-MgUserTeamworkInstalledApp -UserId <UserE-ID> -TeamsAppId <TeamsAppId>

Future best practice:

Avoid PowerShell uninstall if temporary access revocation is needed; remove sharing in Copilot Studio instead

This ensures User E can reinstall the agent without encountering "Your app package failed the validation" errors.

Was this reply helpful? Yes No
CU05110824-0 38 on at

Like (0)

Report
Copy link

Link copied!
Hi @AP-26031104-0

Delete %appdata%\Microsoft\Teams\Application Cache\Cache, Blob_storage, IndexedDB, Local Storage, tmp

What if I use web app and not windows app? Please don't recommend me to re-login or delete browsing data, because I have already done that and it doesn't work.

Was this reply helpful? Yes No
AP-26031104-0 Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!
The issue with User E not being able to reinstall the Copilot agent isn’t caused by browser cache or the web app. Since it only fails after the PowerShell uninstall, it’s likely due to stale app metadata on the Teams service.

To fix this:

Clean up the app – Run Get-MgUserTeamworkInstalledApp and remove it again using Remove-MgUserTeamworkInstalledApp.

Republish the agent – Make a small change to bump the version and generate a new link.

Reinstall via PowerShell – Use New-MgUserTeamworkInstalledApp -UserId <UserE-ID> -TeamsAppId <TeamsAppId> instead of the Teams link.

Check permissions – Ensure the agent is allowed for User E in Teams Admin Center. The “manifest validation” error is misleading — it usually comes from version conflicts or policy restrictions, not the app manifest itself.

Was this reply helpful? Yes No