Skip to content

Commit 02aacd5

Browse files
Merge pull request #251719 from MicrosoftGuyJFlo/patch-53
Microsoft Entra admin center
2 parents 40be643 + 670eb6f commit 02aacd5

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/active-directory/app-provisioning/inbound-provisioning-api-concepts.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,7 @@ With API-driven inbound provisioning, HR ISVs can ship native synchronization ex
4141
### Scenario 3: Enable system integrators to build more connectors to systems of record
4242
Partners can build custom HR connectors to meet different integration requirements around data flow from systems of record to Azure AD.
4343

44-
In all the above scenarios, the integration is greatly simplified as Azure AD provisioning service takes over the responsibility of performing identity profile comparison, restricting the data sync to scoping logic configured by the IT admin and executing rule-based attribute flow and transformation managed in the Microsoft Entra admin portal.
44+
In all the above scenarios, the integration is greatly simplified as Azure AD provisioning service takes over the responsibility of performing identity profile comparison, restricting the data sync to scoping logic configured by the IT admin and executing rule-based attribute flow and transformation managed in the Microsoft Entra admin center.
4545

4646
## End-to-end flow
4747
:::image type="content" source="media/inbound-provisioning-api-concepts/end-to-end-workflow.png" alt-text="Diagram of the end-to-end workflow of inbound provisioning." lightbox="media/inbound-provisioning-api-concepts/end-to-end-workflow.png":::

0 commit comments

Comments
 (0)