Skip to content

Commit 69ca5a7

Browse files
Update scim-graph-scenarios.md
1 parent 2a5ba86 commit 69ca5a7

File tree

1 file changed

+10
-10
lines changed

1 file changed

+10
-10
lines changed

articles/active-directory/app-provisioning/scim-graph-scenarios.md

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ ms.collection: M365-identity-device-management
2323

2424
# Using SCIM and Microsoft Graph together to provision users and enrich your application with the data it needs
2525

26-
**Target audience:** This document is targeted towards developers building applications integrated with Azure AD. For others looking to integrate an existing application such as Zoom, ServiceNow, Dropbox, etc. you can skip this and review the application specific [tutorials](https://docs.microsoft.com/azure/active-directory/saas-apps/tutorial-list).
26+
**Target audience:** This document is targeted towards developers building applications integrated with Azure AD. For others looking to integrate an existing application such as Zoom, ServiceNow, and DropBox you can skip this and review the application specific [tutorials](https://docs.microsoft.com/azure/active-directory/saas-apps/tutorial-list).
2727

2828
**Common scenarios**
2929

@@ -37,7 +37,7 @@ ms.collection: M365-identity-device-management
3737
![SCIM Graph decision tree](./media/user-provisioning/scim-graph.png)
3838

3939
## Scenario 1: Automatically create users in my application
40-
Today, IT admins manually create user accounts in my application each time someone needs access or pereodically upload CSV files. The process is time consuming for customers and slows down adoption of my application. All I need is basic [user](https://docs.microsoft.com/graph/api/resources/user?view=graph-rest-1.0) information such as name, email, and userPrincipalName to create a user. Furthermore, my customers use various IdPs and I don't have the resources to maintain a sync engine and custom integrations with each IdP.
40+
Today, IT admins manually create user accounts in my application each time someone needs access or periodically upload CSV files. The process is time consuming for customers and slows down adoption of my application. All I need is basic [user](https://docs.microsoft.com/graph/api/resources/user?view=graph-rest-1.0) information such as name, email, and userPrincipalName to create a user. Furthermore, my customers use various IdPs and I don't have the resources to maintain a sync engine and custom integrations with each IdP.
4141

4242
**Recommendation**: Support a SCIM compliant [/Users](https://aka.ms/scimreferencecode) endpoint. Your customers will be able to easily use this endpoint to integrate with the Azure AD provisioning service and automatically create user accounts when they need access. You can build the endpoint once and it will be compatible with all IdPs, without having to maintain a sync engine. Check out the example request below for how a user would be created.
4343

@@ -65,7 +65,7 @@ POST /Users
6565
## Scenario 2: Automatically remove users from my application when they shouldn't have access anymore
6666
The customers using my application are security focused and have governance requirements to remove accounts when employees don't need them anymore. How can I automate deprovisioning from my application?
6767

68-
**Recommendation:** Support a SCIM compliant /Users endpoint. The Azure AD provisioning service will send requests to disable and delete when the user should not have access anymore. We recommend supporting both disabling and deleting users. See the examples below for what a disable and delete request look like.
68+
**Recommendation:** Support a SCIM compliant /Users endpoint. The Azure AD provisioning service will send requests to disable and delete when the user shouldn't have access anymore. We recommend supporting both disabling and deleting users. See the examples below for what a disable and delete request look like.
6969

7070
Disable user
7171
```json
@@ -91,26 +91,26 @@ DELETE /Users/5171a35d82074e068ce2 HTTP/1.1
9191
## Scenario 3: Automate provisioning groups and managing group memberships in my application.
9292
My application relies on groups for access to various resources, and customers want to reuse the groups that they have in Azure AD. How can I import groups from Azure AD and keep them updated as the memberships change?
9393

94-
**Recommendation:** Support a SCIM compliant /Groups [endpoint](https://aka.ms/scimreferencecode). The Azure AD provisioning service will take care of creating groups and managing memmbership updates in your application.
94+
**Recommendation:** Support a SCIM compliant /Groups [endpoint](https://aka.ms/scimreferencecode). The Azure AD provisioning service will take care of creating groups and managing membership updates in your application.
9595

9696
## Scenario 4: Enrich my application with data from Microsoft services such as Teams, Outlook, and OneDrive.
97-
My application is built into Microsoft Teams and relies on message data. In addition, we store files for users in OneDriveHow can I enrich my application with resources across Microsoft?
97+
My application is built into Microsoft Teams and relies on message data. In addition, we store files for users in OneDrive. How can I enrich my application with the data from these services and across Microsoft?
9898

99-
**Recommendation:** The Microsoft Graph is your entry point to access Microsoft data. Each workload exposes APIs with the data that you need. The Microsoft graph can be used along with SCIM provisioning for the scenarios above. You can use SCIM to provision basic user attributes into your application while calling into graph to get any other data that you need.
99+
**Recommendation:** The [Microsoft Graph](https://docs.microsoft.com/graph/) is your entry point to access Microsoft data. Each workload exposes APIs with the data that you need. The Microsoft graph can be used along with [SCIM provisioning](https://docs.microsoft.com/azure/active-directory/app-provisioning/use-scim-to-provision-users-and-groups) for the scenarios above. You can use SCIM to provision basic user attributes into your application while calling into graph to get any other data that you need.
100100

101-
## Scenario 5: Track changes in Microsoft services such as Teams, Outlook, and others.
101+
## Scenario 5: Track changes in Microsoft services such as Teams, Outlook, and Azure AD.
102102
I need to be able to track changes to Teams and Outlook messages and react to them in real time. How can I get these changes pushed to my application?
103103

104104
**Recommendation:** The Microsoft Graph provides [change notifications](https://docs.microsoft.com/graph/webhooks) and change tracking for various resources. Note the following limitations of change notifications:
105105
- If an event receiver acknowledges an event, but fails to act on it for any reason, the event may be lost
106106
- If an event receiver acknowledges an event, but fails to act on it for any reason, the event may be lost
107-
- Change notifications do not always contain the [resource data](https://docs.microsoft.com/graph/webhooks-with-resource-data)
107+
- Change notifications don't always contain the [resource data](https://docs.microsoft.com/graph/webhooks-with-resource-data)
108108
For the reasons above, developers often use change notifications along with change tracking for synchronization scenarios.
109109

110-
## Scenario 6: Automatically create, update, and delete users and groups in Azure AD and Active Directory
110+
## Scenario 6: Automatically create, update, and delete users and groups in Azure AD.
111111
My application creates information about a user that customers need in Azure AD. This could be an HR application than manages hiring, a communications app that creates phone numbers for users, or some other app that generates data that would be valuable in Azure AD. How do I populate the user record in Azure AD with that data?
112112

113-
**Recommendation** The Microsoft graph exposes /Users and /Groups endpoints that you can integrate with today to provision users into Azure AD. Please note that Azure Active Directory does not support writing those users back into Active Directory.
113+
**Recommendation** The Microsoft graph exposes /Users and /Groups endpoints that you can integrate with today to provision users into Azure AD. Please note that Azure Active Directory doesn't support writing those users back into Active Directory.
114114

115115
> [!NOTE]
116116
> Microsoft has a provisioning service that pulls in data from HR applications such as Workday and SuccessFactors. These integrations are built and managed by Microsoft. For onboarding a new HR application to our service, you can request it on [UserVoice](https://feedback.azure.com/forums/374982-azure-active-directory-application-requests).

0 commit comments

Comments
 (0)