Skip to content

Commit 49511df

Browse files
Update
1 parent cce804a commit 49511df

File tree

4 files changed

+150
-6
lines changed

4 files changed

+150
-6
lines changed

articles/active-directory/saas-apps/g-suite-provisioning-tutorial.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -293,7 +293,6 @@ Now any end user that was made eligible for the group in PIM can get JIT access
293293
* 10/17/2020 - Added support for more G Suite user and group attributes.
294294
* 10/17/2020 - Updated G Suite target attribute names to match what is defined [here](https://developers.google.com/admin-sdk/directory).
295295
* 10/17/2020 - Updated default attribute mappings.
296-
* 03/18/2021 - Manager email is now synchronized instead of ID for all new users. For any existing users that were provisioned with a manager as an ID, you can do a restart through [Microsoft Graph](/graph/api/synchronization-synchronizationjob-restart?preserve-view=true&tabs=http&view=graph-rest-beta) with scope "full" to ensure that the email is provisioned. This change only impacts the GSuite provisioning job and not the older provisioning job beginning with Goov2OutDelta. Note, the manager email is provisioned when the user is first created or when the manager changes. The manager email isn't provisioned if the manager changes their email address.
297296

298297
## More resources
299298

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

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ The scenario outlined in this tutorial assumes that you already have the followi
3636

3737
## Step 1. Plan your provisioning deployment
3838
1. Learn about [how the provisioning service works](../app-provisioning/user-provisioning.md).
39-
1. Determine who will be in [scope for provisioning](../app-provisioning/define-conditional-rules-for-provisioning-user-accounts.md).
39+
1. Determine who is in [scope for provisioning](../app-provisioning/define-conditional-rules-for-provisioning-user-accounts.md).
4040
1. Determine what data to [map between Azure AD and Tailscale](../app-provisioning/customize-application-attributes.md).
4141

4242
## Step 2. Configure Tailscale to support provisioning with Azure AD
@@ -46,9 +46,9 @@ Contact Tailscale support to configure Tailscale to support provisioning with Az
4646

4747
Add Tailscale from the Azure AD application gallery to start managing provisioning to Tailscale. If you have previously setup Tailscale for SSO, you can use the same application. However it's 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).
4848

49-
## Step 4. Define who will be in scope for provisioning
49+
## Step 4. Define who is in scope for provisioning
5050

51-
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. 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 to the application. If you choose to scope who will be provisioned based solely on attributes of the user, you can use a scoping filter as described [here](../app-provisioning/define-conditional-rules-for-provisioning-user-accounts.md).
51+
The Azure AD provisioning service allows you to scope who is provisioned based on assignment to the application and/or based on attributes of the user. If you choose to scope who is 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 to the application. If you choose to scope who is provisioned based solely on attributes of the user, you can use a scoping filter as described [here](../app-provisioning/define-conditional-rules-for-provisioning-user-accounts.md).
5252

5353
* Start small. Test with a small set of users before rolling out to everyone. When scope for provisioning is set to assigned users, you can control this by assigning one or two users to the app. When scope is set to all users, you can specify an [attribute based scoping filter](../app-provisioning/define-conditional-rules-for-provisioning-user-accounts.md).
5454

@@ -89,7 +89,7 @@ This section guides you through the steps to configure the Azure AD provisioning
8989

9090
1. Under the **Mappings** section, select **Synchronize Azure Active Directory Users to Tailscale**.
9191

92-
1. Review the user attributes that are synchronized from Azure AD to Tailscale in the **Attribute-Mapping** section. The attributes selected as **Matching** properties are used to match the user accounts in Tailscale for update operations. If you choose to change the [matching target attribute](../app-provisioning/customize-application-attributes.md), you'll need to ensure that the Tailscale API supports filtering users based on that attribute. Select the **Save** button to commit any changes.
92+
1. Review the user attributes that are synchronized from Azure AD to Tailscale in the **Attribute-Mapping** section. The attributes selected as **Matching** properties are used to match the user accounts in Tailscale for update operations. If you choose to change the [matching target attribute](../app-provisioning/customize-application-attributes.md), you need to ensure that the Tailscale API supports filtering users based on that attribute. Select the **Save** button to commit any changes.
9393

9494
|Attribute|Type|Supported for filtering|Required by Tailscale|
9595
|---|---|---|---|
Lines changed: 145 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,145 @@
1+
---
2+
title: 'Tutorial: Configure Tanium SSO for automatic user provisioning with Azure Active Directory'
3+
description: Learn how to automatically provision and de-provision user accounts from Azure AD to Tanium SSO.
4+
services: active-directory
5+
author: twimmers
6+
writer: twimmers
7+
manager: jeedes
8+
ms.assetid: 967937de3-81c7-4c61-ae7e-7dad6c46411b
9+
ms.service: active-directory
10+
ms.subservice: saas-app-tutorial
11+
ms.workload: identity
12+
ms.topic: tutorial
13+
ms.date: 07/10/2023
14+
ms.author: thwimmer
15+
---
16+
17+
# Tutorial: Configure Tanium SSO for automatic user provisioning
18+
19+
This tutorial describes the steps you need to perform in both Tanium SSO and Azure Active Directory (Azure AD) to configure automatic user provisioning. When configured, Azure AD automatically provisions and de-provisions users and groups to [Tanium SSO](https://www.tanium.com/) using the Azure AD Provisioning service. These capabilities are supported only for Tanium Cloud customers. 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).
20+
21+
22+
## Supported capabilities
23+
> [!div class="checklist"]
24+
> * Create users in Tanium SSO.
25+
> * Remove users in Tanium SSO when they do not require access anymore.
26+
> * Keep user attributes synchronized between Azure AD and Tanium SSO.
27+
> * Provision groups and group memberships in Tanium SSO.
28+
> * [Single sign-on](tanium-cloud-sso-tutorial.md) to Tanium SSO (recommended).
29+
30+
## Prerequisites
31+
32+
The scenario outlined in this tutorial assumes that you already have the following prerequisites:
33+
34+
* [An Azure AD tenant](../develop/quickstart-create-new-tenant.md)
35+
* A user account in Azure AD with [permission](../roles/permissions-reference.md) to configure provisioning (for example, Application Administrator, Cloud Application administrator, Application Owner, or Global Administrator).
36+
* A user account in Tanium SSO with Admin permissions.
37+
38+
## Step 1. Plan your provisioning deployment
39+
40+
1. Learn about [how the provisioning service works](../app-provisioning/user-provisioning.md).
41+
1. Determine who will be in [scope for provisioning](../app-provisioning/define-conditional-rules-for-provisioning-user-accounts.md).
42+
1. Determine what data to [map between Azure AD and Tanium SSO](../app-provisioning/customize-application-attributes.md).
43+
44+
## Step 2. Enable SCIM Provisioning in the Tanium Cloud Management Portal (CMP)
45+
46+
* Follow the steps in the [Tanium Cloud Deployment Guide: Configure SCIM Provisioning](https://docs.tanium.com/cloud/cloud/configuring_identity_providers.html#configure_scim) to enable automatic user provisioniong in Tanium Cloud.
47+
* Retain the **Token** and **SCIM API URL** values for later use in configuring Tanium SSO. Copy the entire token string, formatted like `token-\<58 alphanumeric characters\>`.
48+
49+
## Step 3. Add Tanium SSO from the Azure AD application gallery
50+
51+
Add Tanium SSO from the Azure AD application gallery to start managing provisioning to Tanium SSO. If you have previously setup Tanium SSO for SSO you can use the same application. However, it's 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).
52+
53+
## Step 4. Define who will be in scope for provisioning
54+
55+
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).
56+
57+
* 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).
58+
59+
* If you need more roles, you can [update the application manifest](../develop/howto-add-app-roles-in-azure-ad-apps.md) to add new roles.
60+
61+
## Step 5. Configure automatic user provisioning to Tanium SSO
62+
63+
This section guides you through the steps to configure the Azure AD provisioning service to create, update, and disable users and/or groups in Tanium based on user and/or group assignments in Azure AD.
64+
65+
### To configure automatic user provisioning for Tanium SSO in Azure AD:
66+
67+
1. Sign in to the [Azure portal](https://portal.azure.com). Select **Enterprise Applications**, then select **All applications**.
68+
69+
![Screenshot of Enterprise applications blade.](common/enterprise-applications.png)
70+
71+
1. In the applications list, select **Tanium SSO**.
72+
73+
![Screenshot of the Tanium SSO link in the Applications list.](common/all-applications.png)
74+
75+
1. Select the **Provisioning** tab.
76+
77+
![Screenshot of Provisioning tab.](common/provisioning.png)
78+
79+
1. Set the **Provisioning Mode** to **Automatic**.
80+
81+
![Screenshot of Provisioning tab automatic.](common/provisioning-automatic.png)
82+
83+
1. Under the **Admin Credentials** section, input your Tanium SSO **Tenant URL** and **Secret Token** that you previously retrieved from the Tanium CMP. Click **Test Connection** to ensure Azure AD can connect to Tanium SSO. If the connection fails, ensure that you entered the complete token value, including the `token-` prefix.
84+
85+
![Screenshot of Token.](common/provisioning-testconnection-tenanturltoken.png)
86+
87+
1. In the **Notification Email** field, enter the email address of a person or group who should receive the provisioning error notifications and select the **Send an email notification when a failure occurs** check box.
88+
89+
![Screenshot of Notification Email.](common/provisioning-notification-email.png)
90+
91+
1. Select **Save**.
92+
93+
1. Under the **Mappings** section, select **Synchronize Azure Active Directory Users to Tanium SSO**.
94+
95+
1. Review the user attributes that are synchronized from Azure AD to Tanium SSO in the **Attribute-Mapping** section. The attributes selected as **Matching** properties are used to match the user accounts in Tanium SSO for update operations. If you choose to change the [matching target attribute](../app-provisioning/customize-application-attributes.md), you'll need to ensure that the Tanium SSO API supports filtering users based on that attribute. Select the **Save** button to commit any changes.
96+
97+
|Attribute|Type|Supported for filtering|Required by Tanium SSO|
98+
|---|---|---|---|
99+
|userName|String|&check;|&check;
100+
|active|Boolean||&check;
101+
|displayName|String||&check;
102+
|externalId|String||&check;
103+
104+
105+
1. Under the **Mappings** section, select **Synchronize Azure Active Directory Groups to Tanium SSO**.
106+
107+
1. Review the group attributes that are synchronized from Azure AD to Tanium SSO in the **Attribute-Mapping** section. The attributes selected as **Matching** properties are used to match the groups in Tanium SSO for update operations. Select the **Save** button to commit any changes.
108+
109+
|Attribute|Type|Supported for filtering|Required by Tanium SSO|
110+
|---|---|---|---|
111+
|displayName|String|&check;|&check;
112+
|externalId|String||&check;
113+
|members|Reference||
114+
115+
1. 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).
116+
117+
1. To enable the Azure AD provisioning service for Tanium SSO, change the **Provisioning Status** to **On** in the **Settings** section.
118+
119+
![Screenshot of Provisioning Status Toggled On.](common/provisioning-toggle-on.png)
120+
121+
1. Define the users and/or groups that you would like to provision to Tanium SSO by choosing the desired values in **Scope** in the **Settings** section.
122+
123+
![Screenshot of Provisioning Scope.](common/provisioning-scope.png)
124+
125+
1. When you're ready to provision, click **Save**.
126+
127+
![Screenshot of Saving Provisioning Configuration.](common/provisioning-configuration-save.png)
128+
129+
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.
130+
131+
## Step 6. Monitor your deployment
132+
Once you've configured provisioning, use the following resources to monitor your deployment:
133+
134+
* Use the [provisioning logs](../reports-monitoring/concept-provisioning-logs.md) to determine which users have been provisioned successfully or unsuccessfully
135+
* Check the [progress bar](../app-provisioning/application-provisioning-when-will-provisioning-finish-specific-user.md) to see the status of the provisioning cycle and how close it's to completion
136+
* If the provisioning configuration seems to be in an unhealthy state, the application goes into quarantine. Learn more about quarantine states [here](../app-provisioning/application-provisioning-quarantine-status.md).
137+
138+
## More resources
139+
140+
* [Managing user account provisioning for Enterprise Apps](../app-provisioning/configure-automatic-user-provisioning-portal.md)
141+
* [What is application access and single sign-on with Azure Active Directory?](../manage-apps/what-is-single-sign-on.md)
142+
143+
## Next steps
144+
145+
* [Learn how to review logs and get reports on provisioning activity](../app-provisioning/check-status-user-account-provisioning.md)

articles/active-directory/saas-apps/vmware-identity-service-provisioning-tutorial.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ ms.author: thwimmer
1616

1717
# Tutorial: Configure VMware Identity Service for automatic user provisioning
1818

19-
This tutorial describes the steps you need to perform in both VMware Identity Service and Azure Active Directory (Azure AD) to configure automatic user provisioning. When configured, Azure AD automatically provisions and de-provisions users and groups to [VMware Identity Service](http://www.vmware.com/) 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).
19+
This tutorial describes the steps you need to perform in both VMware Identity Service and Azure Active Directory (Azure AD) to configure automatic user provisioning. When configured, Azure AD automatically provisions and de-provisions users and groups to [VMware Identity Service](https://www.vmware.com/) 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).
2020

2121

2222
## Supported capabilities

0 commit comments

Comments
 (0)