Merge pull request #252269 from MicrosoftDocs/alexbuckgit/docutune-autopr-20230920-132739-2802923-ignore-build

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

Author: Jill Grant

articles/active-directory/saas-apps/teachme-biz-tutorial.md

@@ -1,6 +1,6 @@
 ---
-title: 'Tutorial: Azure Active Directory single sign-on (SSO) integration with Teachme Biz'
-description: Learn how to configure single sign-on between Azure Active Directory and Teachme Biz.
+title: 'Tutorial: Microsoft Entra single sign-on (SSO) integration with Teachme Biz'
+description: Learn how to configure single sign-on between Microsoft Entra ID and Teachme Biz.
 services: active-directory
 author: jeevansd
 manager: CelesteDG
@@ -14,30 +14,30 @@ ms.author: jeedes
 
 ---
 
-# Tutorial: Azure Active Directory single sign-on (SSO) integration with Teachme Biz
+# Tutorial: Microsoft Entra single sign-on (SSO) integration with Teachme Biz
 
-In this tutorial, you'll learn how to integrate Teachme Biz with Azure Active Directory (Azure AD). When you integrate Teachme Biz with Azure AD, you can:
+In this tutorial, you'll learn how to integrate Teachme Biz with Microsoft Entra ID. When you integrate Teachme Biz with Microsoft Entra ID, you can:
 
-* Control in Azure AD who has access to Teachme Biz.
-* Enable your users to be automatically signed-in to Teachme Biz with their Azure AD accounts.
+* Control in Microsoft Entra ID who has access to Teachme Biz.
+* Enable your users to be automatically signed-in to Teachme Biz with their Microsoft Entra accounts.
 * Manage your accounts in one central location.
 
 ## Prerequisites
 
 To get started, you need the following items:
 
-* An Azure AD subscription. If you don't have a subscription, you can get a [free account](https://azure.microsoft.com/free/).
+* A Microsoft Entra subscription. If you don't have a subscription, you can get a [free account](https://azure.microsoft.com/free/).
 * Teachme Biz single sign-on (SSO) enabled subscription.
 
 ## Scenario description
 
-In this tutorial, you configure and test Azure AD SSO in a test environment.
+In this tutorial, you configure and test Microsoft Entra SSO in a test environment.
 
 * Teachme Biz supports **SP and IDP** initiated SSO.
 
 ## Add Teachme Biz from the gallery
 
-To configure the integration of Teachme Biz into Azure AD, you need to add Teachme Biz from the gallery to your list of managed SaaS apps.
+To configure the integration of Teachme Biz into Microsoft Entra ID, you need to add Teachme Biz from the gallery to your list of managed SaaS apps.
 
 1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [Cloud Application Administrator](../roles/permissions-reference.md#cloud-application-administrator).
 1. Browse to **Identity** > **Applications** > **Enterprise applications** > **New application**.
@@ -46,22 +46,26 @@ To configure the integration of Teachme Biz into Azure AD, you need to add Teach
 
  Alternatively, you can also use the [Enterprise App Configuration Wizard](https://portal.office.com/AdminPortal/home?Q=Docs#/azureadappintegration). In this wizard, you can add an application to your tenant, add users/groups to the app, assign roles, as well as walk through the SSO configuration as well. [Learn more about Microsoft 365 wizards.](/microsoft-365/admin/misc/azure-ad-setup-guides)
 
-## Configure and test Azure AD SSO for Teachme Biz
+<a name='configure-and-test-azure-ad-sso-for-teachme-biz'></a>
 
-Configure and test Azure AD SSO with Teachme Biz using a test user called **B.Simon**. For SSO to work, you need to establish a link relationship between an Azure AD user and the related user in Teachme Biz.
+## Configure and test Microsoft Entra SSO for Teachme Biz
 
-To configure and test Azure AD SSO with Teachme Biz, perform the following steps:
+Configure and test Microsoft Entra SSO with Teachme Biz using a test user called **B.Simon**. For SSO to work, you need to establish a link relationship between a Microsoft Entra user and the related user in Teachme Biz.
 
-1. **[Configure Azure AD SSO](#configure-azure-ad-sso)** - to enable your users to use this feature.
-    1. **[Create an Azure AD test user](#create-an-azure-ad-test-user)** - to test Azure AD single sign-on with B.Simon.
-    1. **[Assign the Azure AD test user](#assign-the-azure-ad-test-user)** - to enable B.Simon to use Azure AD single sign-on.
+To configure and test Microsoft Entra SSO with Teachme Biz, perform the following steps:
+
+1. **[Configure Microsoft Entra SSO](#configure-azure-ad-sso)** - to enable your users to use this feature.
+    1. **[Create a Microsoft Entra test user](#create-an-azure-ad-test-user)** - to test Microsoft Entra single sign-on with B.Simon.
+    1. **[Assign the Microsoft Entra test user](#assign-the-azure-ad-test-user)** - to enable B.Simon to use Microsoft Entra single sign-on.
 1. **[Configure Teachme Biz SSO](#configure-teachme-biz-sso)** - to configure the single sign-on settings on application side.
-    1. **[Create Teachme Biz test user](#create-teachme-biz-test-user)** - to have a counterpart of B.Simon in Teachme Biz that is linked to the Azure AD representation of user.
+    1. **[Create Teachme Biz test user](#create-teachme-biz-test-user)** - to have a counterpart of B.Simon in Teachme Biz that is linked to the Microsoft Entra representation of user.
 1. **[Test SSO](#test-sso)** - to verify whether the configuration works.
 
-## Configure Azure AD SSO
+<a name='configure-azure-ad-sso'></a>
+
+## Configure Microsoft Entra SSO
 
-Follow these steps to enable Azure AD SSO.
+Follow these steps to enable Microsoft Entra SSO.
 
 1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [Cloud Application Administrator](../roles/permissions-reference.md#cloud-application-administrator).
 1. Browse to **Identity** > **Applications** > **Enterprise applications** > **Teachme Biz** > **Single sign-on**.
@@ -90,7 +94,9 @@ Follow these steps to enable Azure AD SSO.
 
 	![The Certificate download link](common/copy-metadataurl.png)
 
-### Create an Azure AD test user
+<a name='create-an-azure-ad-test-user'></a>
+
+### Create a Microsoft Entra test user
 
 In this section, you'll create a test user called B.Simon.
 
@@ -104,7 +110,9 @@ In this section, you'll create a test user called B.Simon.
    1. Select **Review + create**.
 1. Select **Create**.
 
-### Assign the Azure AD test user
+<a name='assign-the-azure-ad-test-user'></a>
+
+### Assign the Microsoft Entra test user
 
 In this section, you'll enable B.Simon to use single sign-on by granting access to Teachme Biz.
 
@@ -126,7 +134,7 @@ In this section, you create a user called Britta Simon in Teachme Biz. Work with
 
 ## Test SSO 
 
-In this section, you test your Azure AD single sign-on configuration with following options. 
+In this section, you test your Microsoft Entra single sign-on configuration with following options. 
 
 #### SP initiated:
 

articles/active-directory/saas-apps/teamgo-provisioning-tutorial.md

@@ -1,6 +1,6 @@
 ---
-title: 'Tutorial: Configure Teamgo for automatic user provisioning with Azure Active Directory'
-description: Learn how to automatically provision and de-provision user accounts from Azure AD to Teamgo.
+title: 'Tutorial: Configure Teamgo for automatic user provisioning with Microsoft Entra ID'
+description: Learn how to automatically provision and de-provision user accounts from Microsoft Entra ID to Teamgo.
 services: active-directory
 author: twimmers
 writer: twimmers
@@ -16,56 +16,62 @@ ms.author: thwimmer
 
 # Tutorial: Configure Teamgo for automatic user provisioning
 
-This tutorial describes the steps you need to perform in both Teamgo and Azure Active Directory (Azure AD) to configure automatic user provisioning. When configured, Azure AD automatically provisions and de-provisions users and groups to [Teamgo](https://www.teamgo.co/) using the Azure AD Provisioning service. For important details on what this service does, how it works, and frequently asked questions, see [Automate user provisioning and deprovisioning to SaaS applications with Azure Active Directory](../app-provisioning/user-provisioning.md). 
+This tutorial describes the steps you need to perform in both Teamgo and Microsoft Entra ID to configure automatic user provisioning. When configured, Microsoft Entra ID automatically provisions and de-provisions users and groups to [Teamgo](https://www.teamgo.co/) using the Microsoft Entra provisioning service. For important details on what this service does, how it works, and frequently asked questions, see [Automate user provisioning and deprovisioning to SaaS applications with Microsoft Entra ID](../app-provisioning/user-provisioning.md). 
 
 
 ## Capabilities Supported
 > [!div class="checklist"]
 > * Create users in Teamgo
 > * Remove users in Teamgo when they do not require access anymore
-> * Keep user attributes synchronized between Azure AD and Teamgo
+> * Keep user attributes synchronized between Microsoft Entra ID and Teamgo
 > * [Single sign-on](teamgo-tutorial.md) to Teamgo (recommended)
 
 ## Prerequisites
 
 The scenario outlined in this tutorial assumes that you already have the following prerequisites:
 
-* [An Azure AD tenant](../develop/quickstart-create-new-tenant.md) 
-* A user account in Azure AD with [permission](../roles/permissions-reference.md) to configure provisioning (e.g. Application Administrator, Cloud Application administrator, Application Owner, or Global Administrator). 
+* [A Microsoft Entra tenant](../develop/quickstart-create-new-tenant.md) 
+* A user account in Microsoft Entra ID with [permission](../roles/permissions-reference.md) to configure provisioning (e.g. Application Administrator, Cloud Application administrator, Application Owner, or Global Administrator). 
 * A Teamgo account with Azure integration supported. 
 
-## Step 1. Plan your provisioning deployment
+## Step 1: Plan your provisioning deployment
 1. Learn about [how the provisioning service works](../app-provisioning/user-provisioning.md).
 2. Determine who will be in [scope for provisioning](../app-provisioning/define-conditional-rules-for-provisioning-user-accounts.md).
-3. Determine what data to [map between Azure AD and Teamgo](../app-provisioning/customize-application-attributes.md). 
+3. Determine what data to [map between Microsoft Entra ID and Teamgo](../app-provisioning/customize-application-attributes.md). 
 
-## Step 2. Configure Teamgo to support provisioning with Azure AD
+<a name='step-2-configure-teamgo-to-support-provisioning-with-azure-ad'></a>
+
+## Step 2: Configure Teamgo to support provisioning with Microsoft Entra ID
 
 1. Sign-in to the [Teamgo dashboard](https://my.teamgo.co) and go to  the Settings. 
 1. Click on **Integrations** under settings.
-1. Under **Employee Directory**, look for **Azure Active Directory** and click on **Enable** button.
+1. Under **Employee Directory**, look for **Microsoft Entra ID** and click on **Enable** button.
 ![Integrations tab](media/teamgo-provisioning-tutorial/enable-azure-in-teamgo.png)
 1. Go to **SCIM Bearer Token** tab and copy the bearer token. The **Secret Token** will be required in the **Step 5**.
 ![Integration tab](media/teamgo-provisioning-tutorial/scim-bearer-token.png)
 
-## Step 3. Add Teamgo from the Azure AD application gallery
+<a name='step-3-add-teamgo-from-the-azure-ad-application-gallery'></a>
+
+## Step 3: Add Teamgo from the Microsoft Entra application gallery
 
-Add Teamgo from the Azure AD application gallery to start managing provisioning to Teamgo. If you have previously setup Teamgo for SSO you can use the same application. However it is recommended that you create a separate app when testing out the integration initially. Learn more about adding an application from the gallery [here](../manage-apps/add-application-portal.md). 
+Add Teamgo from the Microsoft Entra application gallery to start managing provisioning to Teamgo. If you have previously setup Teamgo for SSO you can use the same application. However it is recommended that you create a separate app when testing out the integration initially. Learn more about adding an application from the gallery [here](../manage-apps/add-application-portal.md). 
 
-## Step 4. Define who will be in scope for provisioning 
+## Step 4: Define who will be in scope for provisioning 
 
-The Azure AD provisioning service allows you to scope who will be provisioned based on assignment to the application and or based on attributes of the user / group. If you choose to scope who will be provisioned to your app based on assignment, you can use the following [steps](../manage-apps/assign-user-or-group-access-portal.md) to assign users and groups to the application. If you choose to scope who will be provisioned based solely on attributes of the user or group, you can use a scoping filter as described [here](../app-provisioning/define-conditional-rules-for-provisioning-user-accounts.md). 
+The Microsoft Entra provisioning service allows you to scope who will be provisioned based on assignment to the application and or based on attributes of the user / group. If you choose to scope who will be provisioned to your app based on assignment, you can use the following [steps](../manage-apps/assign-user-or-group-access-portal.md) to assign users and groups to the application. If you choose to scope who will be provisioned based solely on attributes of the user or group, you can use a scoping filter as described [here](../app-provisioning/define-conditional-rules-for-provisioning-user-accounts.md). 
 
 * Start small. Test with a small set of users and groups before rolling out to everyone. When scope for provisioning is set to assigned users and groups, you can control this by assigning one or two users or groups to the app. When scope is set to all users and groups, you can specify an [attribute based scoping filter](../app-provisioning/define-conditional-rules-for-provisioning-user-accounts.md).
 
 * If you need additional roles, you can [update the application manifest](../develop/howto-add-app-roles-in-azure-ad-apps.md) to add new roles.
 
 
-## Step 5. Configure automatic user provisioning to Teamgo 
+## Step 5: Configure automatic user provisioning to Teamgo 
+
+This section guides you through the steps to configure the Microsoft Entra provisioning service to create, update, and disable users and/or groups in TestApp based on user and/or group assignments in Microsoft Entra ID.
 
-This section guides you through the steps to configure the Azure AD provisioning service to create, update, and disable users and/or groups in TestApp based on user and/or group assignments in Azure AD.
+<a name='to-configure-automatic-user-provisioning-for-teamgo-in-azure-ad'></a>
 
-### To configure automatic user provisioning for Teamgo in Azure AD:
+### To configure automatic user provisioning for Teamgo in Microsoft Entra ID:
 
 1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [Cloud Application Administrator](../roles/permissions-reference.md#cloud-application-administrator).
 1. Browse to **Identity** > **Applications** > **Enterprise applications**
@@ -84,7 +90,7 @@ This section guides you through the steps to configure the Azure AD provisioning
 
 	![Provisioning tab](common/provisioning-automatic.png)
 
-5. Under the **Admin Credentials** section, input your Teamgo Tenant URL and Secret Token. Click **Test Connection** to ensure Azure AD can connect to Teamgo. If the connection fails, ensure your Teamgo account has Admin permissions and try again.
+5. Under the **Admin Credentials** section, input your Teamgo Tenant URL and Secret Token. Click **Test Connection** to ensure Microsoft Entra ID can connect to Teamgo. If the connection fails, ensure your Teamgo account has Admin permissions and try again.
 
  	![Token](common/provisioning-testconnection-tenanturltoken.png)
 
@@ -94,9 +100,9 @@ This section guides you through the steps to configure the Azure AD provisioning
 
 7. Select **Save**.
 
-8. Under the **Mappings** section, select **Synchronize Azure Active Directory Users to Teamgo**.
+8. Under the **Mappings** section, select **Synchronize Microsoft Entra users to Teamgo**.
 
-9. Review the user attributes that are synchronized from Azure AD to Teamgo in the **Attribute-Mapping** section. The attributes selected as **Matching** properties are used to match the user accounts in Teamgo for update operations. If you choose to change the [matching target attribute](../app-provisioning/customize-application-attributes.md), you will need to ensure that the Teamgo API supports filtering users based on that attribute. Select the **Save** button to commit any changes.
+9. Review the user attributes that are synchronized from Microsoft Entra ID to Teamgo in the **Attribute-Mapping** section. The attributes selected as **Matching** properties are used to match the user accounts in Teamgo for update operations. If you choose to change the [matching target attribute](../app-provisioning/customize-application-attributes.md), you will need to ensure that the Teamgo API supports filtering users based on that attribute. Select the **Save** button to commit any changes.
 
     |Attribute|Type|Supported for filtering
     |---|---|---|
@@ -115,7 +121,7 @@ This section guides you through the steps to configure the Azure AD provisioning
     |urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:department|String|
 10. To configure scoping filters, refer to the following instructions provided in the [Scoping filter tutorial](../app-provisioning/define-conditional-rules-for-provisioning-user-accounts.md).
 
-11. To enable the Azure AD provisioning service for Teamgo, change the **Provisioning Status** to **On** in the **Settings** section.
+11. To enable the Microsoft Entra provisioning service for Teamgo, change the **Provisioning Status** to **On** in the **Settings** section.
 
 	![Provisioning Status Toggled On](common/provisioning-toggle-on.png)
 
@@ -127,9 +133,9 @@ This section guides you through the steps to configure the Azure AD provisioning
 
 	![Saving Provisioning Configuration](common/provisioning-configuration-save.png)
 
-This operation starts the initial synchronization cycle of all users and groups defined in **Scope** in the **Settings** section. The initial cycle takes longer to perform than subsequent cycles, which occur approximately every 40 minutes as long as the Azure AD provisioning service is running. 
+This operation starts the initial synchronization cycle of all users and groups defined in **Scope** in the **Settings** section. The initial cycle takes longer to perform than subsequent cycles, which occur approximately every 40 minutes as long as the Microsoft Entra provisioning service is running. 
 
-## Step 6. Monitor your deployment
+## Step 6: Monitor your deployment
 Once you've configured provisioning, use the following resources to monitor your deployment:
 
 1. Use the [provisioning logs](../reports-monitoring/concept-provisioning-logs.md) to determine which users have been provisioned successfully or unsuccessfully
@@ -139,7 +145,7 @@ Once you've configured provisioning, use the following resources to monitor your
 ## Additional resources
 
 * [Managing user account provisioning for Enterprise Apps](../app-provisioning/configure-automatic-user-provisioning-portal.md)
-* [What is application access and single sign-on with Azure Active Directory?](../manage-apps/what-is-single-sign-on.md)
+* [What is application access and single sign-on with Microsoft Entra ID?](../manage-apps/what-is-single-sign-on.md)
 
 ## Next steps