Skip to content

Commit 18de936

Browse files
authored
Merge pull request #107917 from ArvindHarinder1/patch-95
Update application-provisioning-configure-api.md
2 parents 6344a46 + 1664e7a commit 18de936

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/active-directory/app-provisioning/application-provisioning-configure-api.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -171,7 +171,7 @@ Content-type: application/json
171171

172172
### Retrieve the template for the provisioning connector
173173

174-
Applications in the gallery that are enabled for provisioning have templates to streamline configuration. Use the request below to [retrieve the template for the provisioning configuration](https://docs.microsoft.com/graph/api/synchronization-synchronizationtemplate-list?view=graph-rest-beta&tabs=http).
174+
Applications in the gallery that are enabled for provisioning have templates to streamline configuration. Use the request below to [retrieve the template for the provisioning configuration](https://docs.microsoft.com/graph/api/synchronization-synchronizationtemplate-list?view=graph-rest-beta&tabs=http). Note that you will need to provide the ID. The ID refers to the preceding resource, which in this case is the ServicePrincipal.
175175

176176
#### *Request*
177177

@@ -263,10 +263,10 @@ Content-type: application/json
263263

264264
### Test the connection to the application
265265

266-
Test the connection with the third-party application. The example below is for an application that requires clientSecret and secretToken. Each application has its on requirements. Review the [API documentation](https://docs.microsoft.com/graph/api/synchronization-synchronizationjob-validatecredentials?view=graph-rest-beta&tabs=http) to see the available options.
266+
Test the connection with the third-party application. The example below is for an application that requires clientSecret and secretToken. Each application has its on requirements. Applications often use BaseAddress in place of ClientSecret. To determine what credentials your app requires, navigate to the provisioning configuration page for your application and in developer mode click test connection. The network traffic will show the parameters used for credentials. The full list of credentials can be found [here](https://docs.microsoft.com/graph/api/synchronization-synchronizationjob-validatecredentials?view=graph-rest-beta&tabs=http).
267267

268268
#### *Request*
269-
```http
269+
```msgraph-interactive
270270
POST https://graph.microsoft.com/beta/servicePrincipals/{id}/synchronization/jobs/{id}/validateCredentials
271271
{
272272
credentials: [
@@ -290,7 +290,7 @@ HTTP/1.1 204 No Content
290290
Configuring provisioning requires establishing a trust between Azure AD and the application. Authorize access to the third-party application. The example below is for an application that requires clientSecret and secretToken. Each application has its on requirements. Review the [API documentation](https://docs.microsoft.com/graph/api/synchronization-synchronizationjob-validatecredentials?view=graph-rest-beta&tabs=http) to see the available options.
291291

292292
#### *Request*
293-
```json
293+
```msgraph-interactive
294294
PUT https://graph.microsoft.com/beta/servicePrincipals/{id}/synchronization/secrets
295295
296296
{

0 commit comments

Comments
 (0)