Merge pull request #251826 from MicrosoftDocs/alexbuckgit/docutune-autopr-20230918-141307-7479199-ignore-build

[BULK] - DocuTune - Rebranding of Azure Active Directory to Microsoft Entra (part 2) - app-provisioning

Author: Jill Grant

articles/active-directory/app-provisioning/provisioning-agent-release-version-history.md

@@ -1,6 +1,6 @@
 ---
-title: Azure Active Directory Connect Provisioning Agent - Version release history
-description: This article lists all releases of Azure Active Directory Connect Provisioning Agent and describes new features and fixed issues.
+title: Microsoft Entra Connect Provisioning Agent - Version release history
+description: This article lists all releases of Microsoft Entra Connect Provisioning Agent and describes new features and fixed issues.
 services: active-directory
 author: kenwith
 manager: amycolannino
@@ -13,6 +13,6 @@ ms.author: kenwith
 ms.reviewer: arvinh
 ---
 
-# Azure Active Directory Connect Provisioning Agent: Version release history
+# Microsoft Entra Connect Provisioning Agent: Version release history
 
 [!INCLUDE [cloud-sync-version-history.md](../../../includes/cloud-sync-version-history.md)]

articles/active-directory/app-provisioning/provisioning-workbook.md

@@ -38,7 +38,7 @@ At the top of the workbook, using the drop-down, specify the source and target i
 Theses fields are the source and target of identities.  The rest of the filters that appear are based on the selection of source and target.
 You can scope your search so that it is more granular using the additional fields.  Use the table below as a reference for queries.
 
-For example, if you wanted to see data from your cloud sync workflow, your source would be Active Directory and your target would be Azure AD.
+For example, if you wanted to see data from your cloud sync workflow, your source would be Active Directory and your target would be Microsoft Entra ID.
 
 
 >[!NOTE]

articles/active-directory/app-provisioning/sap-successfactors-attribute-reference.md

@@ -1,6 +1,6 @@
 ---
-title: SAP SuccessFactors attribute reference for Azure Active Directory
-description: Learn which attributes from SuccessFactors are supported by SuccessFactors-HR driven provisioning in Azure Active Directory.
+title: SAP SuccessFactors attribute reference for Microsoft Entra ID
+description: Learn which attributes from SuccessFactors are supported by SuccessFactors-HR driven provisioning in Microsoft Entra ID.
 services: active-directory
 author: kenwith
 manager: amycolannino
@@ -13,7 +13,7 @@ ms.author: kenwith
 ms.reviewer: chmutali
 ---
 
-# SAP SuccessFactors attribute reference for Azure Active Directory
+# SAP SuccessFactors attribute reference for Microsoft Entra ID
 
 In this article, you'll find information on:
 
@@ -25,7 +25,7 @@ In this article, you'll find information on:
 The table below captures the list of SuccessFactors attributes included by default in the following two provisioning apps:
 
 - [SuccessFactors to Active Directory User Provisioning](../saas-apps/sap-successfactors-inbound-provisioning-tutorial.md)
-- [SuccessFactors to Azure AD User Provisioning](../saas-apps/sap-successfactors-inbound-provisioning-cloud-only-tutorial.md)
+- [SuccessFactors to Microsoft Entra User Provisioning](../saas-apps/sap-successfactors-inbound-provisioning-cloud-only-tutorial.md)
 
 Please refer to the [SAP SuccessFactors integration reference](./sap-successfactors-integration-reference.md#retrieving-more-attributes) to extend the schema for additional attributes. 
 
@@ -113,7 +113,7 @@ Please refer to the [SAP SuccessFactors integration reference](./sap-successfact
 
 ## Default attribute mapping
 
-The table below provides the default attribute mapping between SuccessFactors attributes listed above and AD/Azure AD attributes. In the Azure AD provisioning app "Mapping" blade, you can modify this default mapping to include attributes from the list above. 
+The table below provides the default attribute mapping between SuccessFactors attributes listed above and AD/Azure AD attributes. In the Microsoft Entra provisioning app "Mapping" blade, you can modify this default mapping to include attributes from the list above. 
 
 | \# | SuccessFactors Entity                  | SuccessFactors Attribute | Default AD/Azure AD attribute mapping   | Processing Remark                                                                            |
 |----|----------------------------------------|--------------------------|-----------------------------------------|----------------------------------------------------------------------------------------------|

articles/active-directory/app-provisioning/sap-successfactors-integration-reference.md

@@ -1,6 +1,6 @@
 ---
-title: Use SCIM, Microsoft Graph, and Azure Active Directory to provision users and enrich apps with data
-description: Using SCIM and the Microsoft Graph together to provision users and enrich your application with the data it needs in Azure Active Directory.
+title: Use SCIM, Microsoft Graph, and Microsoft Entra ID to provision users and enrich apps with data
+description: Using SCIM and the Microsoft Graph together to provision users and enrich your application with the data it needs in Microsoft Entra ID.
 services: active-directory
 author: kenwith
 manager: amycolannino
@@ -16,27 +16,27 @@ ms.reviewer: arvinh
 
 # Using SCIM and Microsoft Graph together to provision users and enrich your application with the data it needs
 
-**Target audience:** This article is targeted towards developers building applications to be integrated with Azure Active Directory (Azure AD). If you're looking to use applications already integrated with Azure AD, such as Zoom, ServiceNow, and DropBox, you can skip this article and review the application specific [tutorials](../saas-apps/tutorial-list.md) or review [how the provisioning service works](./how-provisioning-works.md).
+**Target audience:** This article is targeted towards developers building applications to be integrated with Microsoft Entra ID. If you're looking to use applications already integrated with Microsoft Entra ID, such as Zoom, ServiceNow, and DropBox, you can skip this article and review the application specific [tutorials](../saas-apps/tutorial-list.md) or review [how the provisioning service works](./how-provisioning-works.md).
 
 **Common scenarios**
 
-Azure AD provides an out of the box service for provisioning and an extensible platform to build your applications on. The decision tree outlines how a developer would use [SCIM](https://aka.ms/scimoverview) and the [Microsoft Graph](/graph/overview) to automate provisioning. 
+Microsoft Entra ID provides an out of the box service for provisioning and an extensible platform to build your applications on. The decision tree outlines how a developer would use [SCIM](https://aka.ms/scimoverview) and the [Microsoft Graph](/graph/overview) to automate provisioning. 
 
 > [!div class="checklist"]
 > * Automatically create users in my application
 > * Automatically remove users from my application when they shouldn't have access anymore
 > * Integrate my application with multiple identity providers for provisioning
 > * Enrich my application with data from Microsoft services such as Teams, Outlook, and Office.
-> * Automatically create, update, and delete users and groups in Azure AD and Active Directory
+> * Automatically create, update, and delete users and groups in Microsoft Entra ID and Active Directory
 
 ![SCIM Graph decision tree](./media/user-provisioning/scim-graph.png)
 
 ## Scenario 1: Automatically create users in my app
 Today, IT admins provision users by manually creating user accounts or periodically uploading CSV files into my application. The process is time consuming for customers and slows down adoption of my application. All I need is basic user information such as name, email, and userPrincipalName to create a user. 
 
 **Recommendation**: 
-* If your customers use various IdPs and you do not want to maintain a sync engine to integrate with each, 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. Check out the example request below for how a user would be created using SCIM.
-* If you require user data found on the user object in Azure AD and other data from across Microsoft, consider building a SCIM endpoint for user provisioning and calling into the Microsoft Graph to get the rest of the data. 
+* If your customers use various IdPs and you do not want to maintain a sync engine to integrate with each, support a SCIM compliant [/Users](https://aka.ms/scimreferencecode) endpoint. Your customers will be able to easily use this endpoint to integrate with the Microsoft Entra 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. Check out the example request below for how a user would be created using SCIM.
+* If you require user data found on the user object in Microsoft Entra ID and other data from across Microsoft, consider building a SCIM endpoint for user provisioning and calling into the Microsoft Graph to get the rest of the data. 
 
 ```json
 POST /Users
@@ -62,7 +62,7 @@ POST /Users
 ## Scenario 2: Automatically remove users from my app
 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?
 
-**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. 
+**Recommendation:** Support a SCIM compliant /Users endpoint. The Microsoft Entra 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. 
 
 Disable user
 ```json
@@ -86,16 +86,18 @@ DELETE /Users/5171a35d82074e068ce2 HTTP/1.1
 ```
 
 ## Scenario 3: Automate managing group memberships in my app
-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?  
+My application relies on groups for access to various resources, and customers want to reuse the groups that they have in Microsoft Entra ID. How can I import groups from Microsoft Entra ID and keep them updated as the memberships change?  
 
-**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. 
+**Recommendation:** Support a SCIM compliant /Groups [endpoint](https://aka.ms/scimreferencecode). The Microsoft Entra provisioning service will take care of creating groups and managing membership updates in your application. 
 
 ## Scenario 4: Enrich my app with data from Microsoft services such as Teams, Outlook, and OneDrive
 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?
 
 **Recommendation:** The [Microsoft Graph](/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](./use-scim-to-provision-users-and-groups.md) 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. 
 
-## Scenario 5: Track changes in Microsoft services such as Teams, Outlook, and Azure AD
+<a name='scenario-5-track-changes-in-microsoft-services-such-as-teams-outlook-and-azure-ad'></a>
+
+## Scenario 5: Track changes in Microsoft services such as Teams, Outlook, and Microsoft Entra ID
 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?
 
 **Recommendation:** The Microsoft Graph provides [change notifications](/graph/webhooks) and [change tracking](/graph/delta-query-overview) for various resources. Note the following limitations of change notifications:
@@ -104,15 +106,17 @@ I need to be able to track changes to Teams and Outlook messages and react to th
 - Change notifications don't always contain the [resource data](/graph/webhooks-with-resource-data)
 For the reasons above, developers often use change notifications along with change tracking for synchronization scenarios. 
 
-## Scenario 6: Provision users and groups in Azure AD
-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? 
+<a name='scenario-6-provision-users-and-groups-in-azure-ad'></a>
+
+## Scenario 6: Provision users and groups in Microsoft Entra ID
+My application creates information about a user that customers need in Microsoft Entra ID. 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 Microsoft Entra ID. How do I populate the user record in Microsoft Entra ID with that data? 
 
-**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. 
+**Recommendation** The Microsoft graph exposes /Users and /Groups endpoints that you can integrate with today to provision users into Microsoft Entra ID. Please note that Microsoft Entra ID doesn't support writing those users back into Active Directory. 
 
 > [!NOTE]
 > 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/d365community/forum/22920db1-ad25-ec11-b6e6-000d3a4f0789). 
 
 ## Related articles
 
 - [Review the synchronization Microsoft Graph documentation](/graph/api/resources/synchronization-overview)
-- [Integrating a custom SCIM app with Azure AD](use-scim-to-provision-users-and-groups.md)
+- [Integrating a custom SCIM app with Microsoft Entra ID](use-scim-to-provision-users-and-groups.md)

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

@@ -1,6 +1,6 @@
 ---
-title: Tutorial - Test your SCIM endpoint for compatibility with the Azure Active Directory (Azure AD) provisioning service.
-description: This tutorial describes how to use the Azure AD SCIM Validator to validate that your provisioning server is compatible with the Azure SCIM client.
+title: Tutorial - Test your SCIM endpoint for compatibility with the Microsoft Entra provisioning service.
+description: This tutorial describes how to use the Microsoft Entra SCIM Validator to validate that your provisioning server is compatible with the Azure SCIM client.
 author: kenwith
 ms.author: kenwith
 manager: amycolannino
@@ -16,7 +16,7 @@ ms.reviewer: arvinh
 
 # Tutorial: Validate a SCIM endpoint
 
-This tutorial describes how to use the Azure AD SCIM Validator to validate that your provisioning server is compatible with the Azure SCIM client. The tutorial is intended for developers who want to build a SCIM compatible server to manage their identities with the Azure AD provisioning service.
+This tutorial describes how to use the Microsoft Entra SCIM Validator to validate that your provisioning server is compatible with the Azure SCIM client. The tutorial is intended for developers who want to build a SCIM compatible server to manage their identities with the Microsoft Entra provisioning service.
 
 In this tutorial, you learn how to:
 
@@ -27,8 +27,8 @@ In this tutorial, you learn how to:
 
 ## Prerequisites
 
-- An Azure Active Directory account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
-- A SCIM endpoint that conforms to the SCIM 2.0 standard and meets the provision service requirements. To learn more, see [Tutorial: Develop and plan provisioning for a SCIM endpoint in Azure Active Directory](use-scim-to-provision-users-and-groups.md).
+- A Microsoft Entra account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
+- A SCIM endpoint that conforms to the SCIM 2.0 standard and meets the provision service requirements. To learn more, see [Tutorial: Develop and plan provisioning for a SCIM endpoint in Microsoft Entra ID](use-scim-to-provision-users-and-groups.md).
 
 
 ## Select a testing method
@@ -43,7 +43,7 @@ The first step is to select a testing method to validate your SCIM endpoint.
 
 **Discover schema** - If your end point supports /Schema, this option lets the tool discover the supported attributes. We recommend this option as it reduces the overhead of updating your app as you build it out.
 
-**Upload Azure AD Schema** - Upload the schema you've downloaded from your sample app on Azure AD.
+**Upload Microsoft Entra Schema** - Upload the schema you've downloaded from your sample app on Microsoft Entra ID.
 
 
 ## Configure the testing method
@@ -80,7 +80,7 @@ In addition to using the SCIM Validator tool, you can also use Postman to valida
 The endpoints are in the `{host}/scim/` directory, and you can use standard HTTP requests to interact with them. To modify the `/scim/` route, see *ControllerConstant.cs* in **AzureADProvisioningSCIMreference** > **ScimReferenceApi** > **Controllers**.
 
 > [!NOTE]
-> You can only use HTTP endpoints for local tests. The Azure AD provisioning service requires that your endpoint support HTTPS.
+> You can only use HTTP endpoints for local tests. The Microsoft Entra provisioning service requires that your endpoint support HTTPS.
 
 1. Download [Postman](https://www.postman.com/downloads/) and start the application.
 1. Copy and paste this link into Postman to import the test collection: `https://aka.ms/ProvisioningPostman`.
@@ -117,7 +117,9 @@ That's it! You can now run the **Postman** collection to test the SCIM endpoint
 
 If you created any Azure resources in your testing that are no longer needed, don't forget to delete them.
 
-## Known Issues with Azure AD SCIM Validator
+<a name='known-issues-with-azure-ad-scim-validator'></a>
+
+## Known Issues with Microsoft Entra SCIM Validator
 
 - Soft deletes (disables) aren’t yet supported.
 - The time zone format is randomly generated and fails for systems that try to validate it.
@@ -126,4 +128,4 @@ If you created any Azure resources in your testing that are no longer needed, do
 
 
 ## Next steps
-- [Learn how to add an app that's not in the Azure AD app gallery](../manage-apps/overview-application-gallery.md)
+- [Learn how to add an app that's not in the Microsoft Entra app gallery](../manage-apps/overview-application-gallery.md)