Skip to content

Commit 9f0a0d8

Browse files
authored
Merge pull request #104754 from msmimart/mm-scimcompat
[App Prov] Move SCIM compatibility file from manage-apps to app-provisioning
2 parents 44fd2bf + 3b2262d commit 9f0a0d8

File tree

6 files changed

+13
-6
lines changed

6 files changed

+13
-6
lines changed

.openpublishing.redirection.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -36485,6 +36485,11 @@
3648536485
"redirect_url": "/azure/active-directory/app-provisioning/application-provisioning-config-problem",
3648636486
"redirect_document_id": false
3648736487
},
36488+
{
36489+
"source_path": "articles/active-directory/manage-apps/application-provisioning-config-problem-scim-compatibility.md",
36490+
"redirect_url": "/azure/active-directory/app-provisioning/application-provisioning-config-problem-scim-compatibility",
36491+
"redirect_document_id": false
36492+
},
3648836493
{
3648936494
"source_path": "articles/active-directory/manage-apps/application-provisioning-configure-api.md",
3649036495
"redirect_url": "/azure/active-directory/app-provisioning/application-provisioning-configure-api",

articles/active-directory/manage-apps/application-provisioning-config-problem-scim-compatibility.md renamed to articles/active-directory/app-provisioning/application-provisioning-config-problem-scim-compatibility.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ ms.collection: M365-identity-device-management
2424

2525
Azure Active Directory (Azure AD) can automatically provision users and groups to any application or system that is fronted by a web service with the interface defined in the [System for Cross-Domain Identity Management (SCIM) 2.0 protocol specification](https://tools.ietf.org/html/draft-ietf-scim-api-19).
2626

27-
Azure AD's support for the SCIM 2.0 protocol is described in [Using System for Cross-Domain Identity Management (SCIM) to automatically provision users and groups from Azure Active Directory to applications](../app-provisioning/use-scim-to-provision-users-and-groups.md), which lists the specific parts of the protocol that it implements in order to automatically provision users and groups from Azure AD to applications that support SCIM 2.0.
27+
Azure AD's support for the SCIM 2.0 protocol is described in [Using System for Cross-Domain Identity Management (SCIM) to automatically provision users and groups from Azure Active Directory to applications](use-scim-to-provision-users-and-groups.md), which lists the specific parts of the protocol that it implements in order to automatically provision users and groups from Azure AD to applications that support SCIM 2.0.
2828

2929
This article describes current and past issues with the Azure AD user provisioning service's adherence to the SCIM 2.0 protocol, and how to work around these issues.
3030

@@ -44,7 +44,7 @@ This article describes current and past issues with the Azure AD user provisioni
4444

4545
No. As it would have constituted a breaking change to SCIM apps that were coded to work with the older behavior, the changes were not automatically applied to existing apps.
4646

47-
The changes are applied to all new [non-gallery SCIM apps](configure-single-sign-on-non-gallery-applications.md)
47+
The changes are applied to all new [non-gallery SCIM apps](../manage-apps/configure-single-sign-on-non-gallery-applications.md)
4848
configured in the Azure portal, after the date of the fix.
4949

5050
For information on how to migrate a pre-existing user provisioning job to include the latest fixes, see the next section.
@@ -113,5 +113,5 @@ Yes. If you had coded an application to the old behavior that existed prior to t
113113

114114

115115
## Next steps
116-
[Learn more about provisioning and de-provisioning to SaaS applications](../app-provisioning/user-provisioning.md)
116+
[Learn more about provisioning and de-provisioning to SaaS applications](user-provisioning.md)
117117

articles/active-directory/app-provisioning/toc.yml

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -77,7 +77,9 @@
7777
href: application-provisioning-configure-api.md
7878
- name: Reference
7979
items:
80-
- name: Choosing a provisioning method
80+
- name: SCIM 2.0 protocol compliance
81+
href: application-provisioning-config-problem-scim-compatibility.md
82+
- name: Choose a provisioning method
8183
href: isv-automatic-provisioning-multi-tenant-apps.md
8284
- name: Cloud HR provisioning
8385
items:

articles/active-directory/app-provisioning/use-scim-to-provision-users-and-groups.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -143,7 +143,7 @@ There are several endpoints defined in the SCIM RFC. You can get started with th
143143

144144
## Step 2: Understand the Azure AD SCIM implementation
145145
> [!IMPORTANT]
146-
> The behavior of the Azure AD SCIM implementation was last updated on December 18, 2018. For information on what changed, see [SCIM 2.0 protocol compliance of the Azure AD User Provisioning service](../manage-apps/application-provisioning-config-problem-scim-compatibility.md).
146+
> The behavior of the Azure AD SCIM implementation was last updated on December 18, 2018. For information on what changed, see [SCIM 2.0 protocol compliance of the Azure AD User Provisioning service](application-provisioning-config-problem-scim-compatibility.md).
147147

148148
If you're building an application that supports a SCIM 2.0 user management API, this section describes in detail how the Azure AD SCIM client is implemented. It also shows how to model your SCIM protocol request handling and responses. Once you've implemented your SCIM endpoint, you can test it by following the procedure described in the previous section.
149149

@@ -1490,7 +1490,7 @@ To help drive awareness and demand of our joint integration, we recommend you up
14901490
* **Sales and customer support readiness.** Ensure your sales and support teams are aware and can speak to the integration capabilities. Brief your sales and support team, provide them with FAQs and include the integration into your sales materials.
14911491
* **Blog post and/or press release.** Craft a blog post or press release that describes the joint integration, the benefits and how to get started. [Example: Imprivata and Azure Active Directory Press Release](https://www.imprivata.com/company/press/imprivata-introduces-iam-cloud-platform-healthcare-supported-microsoft)
14921492
* **Social media.** Leverage your social media like Twitter, Facebook or LinkedIn to promote the integration to your customers. Be sure to include @AzureAD so we can retweet your post. [Example: Imprivata Twitter Post](https://twitter.com/azuread/status/1123964502909779968)
1493-
* **Marketing website.** Create or update your marketing pages (e.g. integration page, partner page, pricing page, etc) to include the availability of the joint integration. [Example: Pingboard integration Page](https://pingboard.com/org-chart-for), [Smartsheet integration page](https://www.smartsheet.com/marketplace/apps/microsoft-azure-ad), [Monday.com pricing page](https://monday.com/pricing/)
1493+
* **Marketing website.** Create or update your marketing pages (e.g. integration page, partner page, pricing page, etc.) to include the availability of the joint integration. [Example: Pingboard integration Page](https://pingboard.com/org-chart-for), [Smartsheet integration page](https://www.smartsheet.com/marketplace/apps/microsoft-azure-ad), [Monday.com pricing page](https://monday.com/pricing/)
14941494
* **Technical documentation.** Create a help center article or technical documentation on how customers can get started. [Example: Envoy + Microsoft Azure Active Directory integration.](https://envoy.help/en/articles/3453335-microsoft-azure-active-directory-integration/
14951495
)
14961496
* **Customer communication.** Alert customers of the new integration through your customer communication (monthly newsletters, email campaigns, product release notes).

0 commit comments

Comments
 (0)