Issue with Power Platform API reassign and Copilot Studio

Question

Issue with Power Platform API reassign and Copilot Studio

Fornalczyk, Mateusz 5

For governance process I'm trying to reassign the owner of Copilot Studio Agent from service principal to an actual user.

I implemented the API action

POST https://api.powerplatform.com/copilotstudio/environments/{EnvironmentId}/bots/{BotId}/api/botAdminOperations/reassign?api-version=1

via custom connector and I'm using my global administrator account for the connection.
To the main issue - when I try running it on an agent in my Dev environemnt in unamanaged solution every thing works great it returns 204. But when I try to do it in the target environment it returns 500 error. All the Ids are correct ones including users entra object id

 {
  "ErrorCode": 500,
  "ErrorMessage": "Sequence contains no elements",
  "DiagnosticsMessage": null,
  "ErrorInfo": null
}

Nivedipa-MSFT 4,251 Reputation points Microsoft External Staff Moderator

2026-03-13T11:05:32.02+00:00
Hello Fornalczyk, Mateusz - Thanks for bringing this issue to our attention.
The "Sequence contains no elements" error indicates that the API cannot locate either the user or the bot in the target environment.

Most common reason: The user may not be provisioned as a systemuser in the Dataverse of the target environment.

Recommended steps to resolve:

Ask the user to sign in to the target environment at least once (via make.powerapps.com, selecting the appropriate environment).

Ensure the Bot ID matches the target environment, as it could differ from Dev if a managed solution was used.

Check that the bot is not part of a managed solution, since managed components can restrict ownership changes.

Quick check:

GET https://{targetenv}.crm.dynamics.com/api/data/v9.2/systemusers?$filter=azureactivedirectoryobjectid eq '{UserEntraObjectId}'

If the result is empty, this confirms the issue. Provision the user first, then try again.
Fornalczyk, Mateusz 5 Reputation points

2026-03-16T09:13:19.8666667+00:00

Hi, both user and id match and exist in the tables. The issue is with the managed solution as for unamnaged it works fine. Is there any way to 'un-restrict' the ownership changes
Nivedipa-MSFT 4,251 Reputation points Microsoft External Staff Moderator

2026-03-17T10:08:10.4866667+00:00
Hello Fornalczyk, Mateusz
Managed solutions block ownership changes via the Copilot Studio API. Three workarounds:

**1.Dataverse PATCH** — Update `ownerid` directly:

PATCH https://{env}.crm.dynamics.com/api/data/v9.2/bots({BotId}) { "******@odata.bind": "/systemusers({UserId})" }

2. Create an active layer — Open the agent in Copilot Studio in the target environment, make a trivial edit and save (creates an unmanaged layer), then retry the reassign API

3. Power Platform Admin Center — Environments → Resources → Copilot Studio agents → select agent → Change owner (admin UI bypasses managed restrictions)

Your answer

Nivedipa-MSFT 4,251 Reputation points Microsoft External Staff Moderator

2026-03-13T11:05:32.02+00:00

Hello Fornalczyk, Mateusz - Thanks for bringing this issue to our attention.
The "Sequence contains no elements" error indicates that the API cannot locate either the user or the bot in the target environment.

Most common reason: The user may not be provisioned as a systemuser in the Dataverse of the target environment.

Recommended steps to resolve:

Ask the user to sign in to the target environment at least once (via make.powerapps.com, selecting the appropriate environment).

Ensure the Bot ID matches the target environment, as it could differ from Dev if a managed solution was used.

Check that the bot is not part of a managed solution, since managed components can restrict ownership changes.

Quick check:

GET https://{targetenv}.crm.dynamics.com/api/data/v9.2/systemusers?$filter=azureactivedirectoryobjectid eq '{UserEntraObjectId}'

If the result is empty, this confirms the issue. Provision the user first, then try again.
Fornalczyk, Mateusz 5 Reputation points

2026-03-16T09:13:19.8666667+00:00

Hi, both user and id match and exist in the tables. The issue is with the managed solution as for unamnaged it works fine. Is there any way to 'un-restrict' the ownership changes
Nivedipa-MSFT 4,251 Reputation points Microsoft External Staff Moderator

2026-03-17T10:08:10.4866667+00:00

Hello Fornalczyk, Mateusz
Managed solutions block ownership changes via the Copilot Studio API. Three workarounds:

**1.Dataverse PATCH** — Update `ownerid` directly:

PATCH https://{env}.crm.dynamics.com/api/data/v9.2/bots({BotId}) { "******@odata.bind": "/systemusers({UserId})" }

2. Create an active layer — Open the agent in Copilot Studio in the target environment, make a trivial edit and save (creates an unmanaged layer), then retry the reassign API

3. Power Platform Admin Center — Environments → Resources → Copilot Studio agents → select agent → Change owner (admin UI bypasses managed restrictions)