Skip to content

Commit 234625c

Browse files
authored
Merge pull request #2821 from abhijananddv/patch-2
Update managed identity payload requirements - added version parameter
2 parents ddfbdf7 + 1b50dc9 commit 234625c

File tree

1 file changed

+18
-12
lines changed

1 file changed

+18
-12
lines changed

power-platform/admin/set-up-managed-identity.md

Lines changed: 18 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Learn how to set up Power Platform managed identity for Dataverse p
44
author: abhijananddv
55
ms.component: pa-admin
66
ms.topic: how-to
7-
ms.date: 09/18/2025
7+
ms.date: 10/10/2025
88
ms.subservice: admin
99
ms.author: abhijanand
1010
ms.reviewer: sericks
@@ -158,12 +158,14 @@ Set **Audience**, **Issuer URL**, and **Subject prefix** explicitly when deployi
158158

159159
To provision managed identity record in Dataverse, complete the following steps.
160160

161-
1. Make a POST call using a REST client (for example, Insomnia, Postman). Use a URL with payload in the following format.
161+
1. Make a POST call using a REST client (for example, Insomnia, Postman). Use a URL with payload in the following format.
162+
162163
```
163164
POST https://<<orgURL>>/api/data/v9.0/managedidentities
164165
```
165-
Be sure to replace **orgURL** with the URL of the organization.
166-
Ensure that **credentialsource** is set to **2** in the payload and **subjectscope** is set to **1** for environment-specific scenarios.
166+
Be sure to replace **orgURL** with the URL of the organization.
167+
168+
2. Ensure that **credentialsource** is set to **2** in the payload, **subjectscope** is set to **1** for environment-specific scenarios, and **version** is set to 1 in the payload.
167169

168170
**Sample payload**
169171
```json
@@ -173,10 +175,11 @@ To provision managed identity record in Dataverse, complete the following steps.
173175
"credentialsource": 2,
174176
"subjectscope": 1,
175177
"tenantid": "<<tenantId>>"
178+
"version": 1
176179
}
177180
```
178181

179-
2. Make a PATCH call to bind the plug-in assembly ID with the managed identity record that's created through the POST call in step 1.
182+
3. Make a PATCH call to bind the plug-in assembly ID with the managed identity record that's created through the POST call in step 1.
180183

181184
**Plug-in assembly**
182185
```
@@ -202,12 +205,15 @@ Verify that your plug-in can securely request access to Azure resources that sup
202205

203206
## Frequently asked questions (FAQs)
204207

205-
1. **How do I resolve the this error?**
208+
### How do I resolve the this error?
209+
If you receive the following error:
206210
**Getting Error – A configuration issue is preventing authentication.**
207-
**AADSTS700213: No matching federated identity record found**
208-
- Ensure the FIC is correctly configured and saved.
209-
- Verify that the issuer/subject matches the format specified above.
210-
- You can also find the expected format in the error stack.
211+
**AADSTS700213: No matching federated identity record found**
212+
Complete the following steps:
213+
1. Ensure the FIC is correctly configured and saved.
214+
1. Verify that the issuer/subject matches the format specified above.
211215

212-
3. **How do I resolve this error?** **Unable to reach or connect to Power Platform**
213-
- Please refer to [Power Platform URLs and IP address ranges](online-requirements.md) to ensure Power Platform endpoints are reachable and allowlisted.
216+
You can also find the expected format in the error stack.
217+
218+
## How do I resolve the "Unable to reach or connect to Power Platform" error?
219+
Please refer to [Power Platform URLs and IP address ranges](online-requirements.md) to ensure Power Platform endpoints are reachable and allowlisted.

0 commit comments

Comments
 (0)