You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: power-platform/admin/set-up-managed-identity.md
+18-12Lines changed: 18 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: Learn how to set up Power Platform managed identity for Dataverse p
4
4
author: abhijananddv
5
5
ms.component: pa-admin
6
6
ms.topic: how-to
7
-
ms.date: 09/18/2025
7
+
ms.date: 10/10/2025
8
8
ms.subservice: admin
9
9
ms.author: abhijanand
10
10
ms.reviewer: sericks
@@ -158,12 +158,14 @@ Set **Audience**, **Issuer URL**, and **Subject prefix** explicitly when deployi
158
158
159
159
To provision managed identity record in Dataverse, complete the following steps.
160
160
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
+
162
163
```
163
164
POST https://<<orgURL>>/api/data/v9.0/managedidentities
164
165
```
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.
167
169
168
170
**Sample payload**
169
171
```json
@@ -173,10 +175,11 @@ To provision managed identity record in Dataverse, complete the following steps.
173
175
"credentialsource": 2,
174
176
"subjectscope": 1,
175
177
"tenantid": "<<tenantId>>"
178
+
"version": 1
176
179
}
177
180
```
178
181
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.
180
183
181
184
**Plug-in assembly**
182
185
```
@@ -202,12 +205,15 @@ Verify that your plug-in can securely request access to Azure resources that sup
202
205
203
206
## Frequently asked questions (FAQs)
204
207
205
-
1.**How do I resolve the this error?**
208
+
### How do I resolve the this error?
209
+
If you receive the following error:
206
210
**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.
211
215
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