You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* A user account in 15Five with Admin permissions.
40
40
41
+
> [!NOTE]
42
+
> This integration is also available to use from Azure AD US Government Cloud environment. You can find this application in the Azure AD US Government Cloud Application Gallery and configure it in the same way as you do from public cloud.
43
+
41
44
## Step 1. Plan your provisioning deployment
42
45
1. Learn about [how the provisioning service works](../app-provisioning/user-provisioning.md).
43
46
2. Determine who will be in [scope for provisioning](../app-provisioning/define-conditional-rules-for-provisioning-user-accounts.md).
Copy file name to clipboardExpand all lines: articles/active-directory/saas-apps/4me-provisioning-tutorial.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,6 +30,9 @@ The scenario outlined in this tutorial assumes that you already have the followi
30
30
*[A 4me tenant](https://www.4me.com/trial/)
31
31
* A user account in 4me with Admin permissions.
32
32
33
+
> [!NOTE]
34
+
> This integration is also available to use from Azure AD US Government Cloud environment. You can find this application in the Azure AD US Government Cloud Application Gallery and configure it in the same way as you do from public cloud.
35
+
33
36
## Add 4me from the gallery
34
37
35
38
Before configuring 4me for automatic user provisioning with Azure AD, you need to add 4me from the Azure AD application gallery to your list of managed SaaS applications.
Copy file name to clipboardExpand all lines: articles/active-directory/saas-apps/8x8-provisioning-tutorial.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,6 +34,9 @@ The scenario outlined in this tutorial assumes that you already have the followi
34
34
* An 8x8 user account with administrator permission in [Admin Console](https://vo-cm.8x8.com).
35
35
*[Single Sign-On with Azure AD](./8x8virtualoffice-tutorial.md) has already been configured.
36
36
37
+
> [!NOTE]
38
+
> This integration is also available to use from Azure AD US Government Cloud environment. You can find this application in the Azure AD US Government Cloud Application Gallery and configure it in the same way as you do from public cloud.
39
+
37
40
## Step 1. Plan your provisioning deployment
38
41
1. Learn about [how the provisioning service works](../app-provisioning/user-provisioning.md).
39
42
2. Determine who will be in [scope for provisioning](../app-provisioning/define-conditional-rules-for-provisioning-user-accounts.md).
title: 'Tutorial: User provisioning for Asana - Azure AD'
3
-
description: Learn how to configure Azure Active Directory to automatically provision and de-provision user accounts to Asana.
2
+
title: 'Tutorial: Configure Asana for automatic user provisioning with Azure Active Directory | Microsoft Docs'
3
+
description: Learn how to automatically provision and de-provision user accounts from Azure AD to Asana.
4
4
services: active-directory
5
-
author: ArvindHarinder1
6
-
manager: CelesteDG
5
+
author: twimmers
6
+
writer: twimmers
7
+
manager: beatrizd
8
+
9
+
ms.assetid: 274810a2-bd74-4500-95f1-c720abf23541
7
10
ms.service: active-directory
8
11
ms.subservice: saas-app-tutorial
9
12
ms.workload: identity
10
13
ms.topic: tutorial
11
14
ms.date: 03/27/2019
12
-
ms.author: arvinh
13
-
ms.reviewer: celested
15
+
ms.author: thwimmer
14
16
---
15
17
16
18
# Tutorial: Configure Asana for automatic user provisioning
17
19
18
-
The objective of this tutorial is to show you the steps you need to perform in Asana and Azure Active Directory (Azure AD) to automatically provision and de-provision user accounts from Azure AD to Asana.
20
+
This tutorial describes the steps you need to do in both Asana and Azure Active Directory (Azure AD) to configure automatic user provisioning. When configured, Azure AD automatically provisions and de-provisions users and groups to [Asana](https://www.asana.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).
21
+
22
+
23
+
## Capabilities Supported
24
+
> [!div class="checklist"]
25
+
> * Create users in Asana.
26
+
> * Remove users in Asana when they do not require access anymore.
27
+
> * Keep user attributes synchronized between Azure AD and Asana.
28
+
> * Provision groups and group memberships in Asana.
29
+
> *[Single sign-on](asana-tutorial.md) to Asana(recommended).
19
30
20
31
## Prerequisites
21
32
22
-
The scenario outlined in this tutorial assumes that you already have the following items:
33
+
The scenario outlined in this tutorial assumes that you already have the following prerequisites:
23
34
24
35
* An Azure AD tenant
25
36
* An Asana tenant with an [Enterprise](https://www.asana.com/pricing) plan or better enabled
@@ -28,69 +39,123 @@ The scenario outlined in this tutorial assumes that you already have the followi
28
39
> [!NOTE]
29
40
> Azure AD provisioning integration relies on the [Asana API](https://asana.com/developers/api-reference/users), which is available to Asana.
30
41
31
-
## Assign users to Asana
42
+
## Step 1. Plan your provisioning deployment
43
+
1. Learn about [how the provisioning service works](../app-provisioning/user-provisioning.md).
44
+
1. Determine who will be in [scope for provisioning](../app-provisioning/define-conditional-rules-for-provisioning-user-accounts.md).
45
+
1. Determine what data to [map between Azure AD and Asana](../app-provisioning/customize-application-attributes.md).
46
+
47
+
## Step 2. Configure Asana to support provisioning with Azure AD
48
+
> [!TIP]
49
+
> To enable SAML-based single sign-on for Asana, follow the instructions provided in the Azure portal. Single sign-on can be configured independently of automatic provisioning, although these two features complement each other.
50
+
51
+
### Generate Secret Token in Asana
52
+
53
+
* Sign in to [Asana](https://app.asana.com/) by using your admin account.
54
+
* Select the profile photo from the top bar, and select your current organization-name settings.
55
+
* Go to the **Service Accounts** tab.
56
+
* Select **Add Service Account**.
57
+
* Update **Name** and **About** and the profile photo as needed. Copy the token in **Token**, and select it in Save Changes.
32
58
33
-
Azure AD uses a concept called *assignments* to determine which users should receive access to selected apps. In the context of automatic user account provisioning, only the users assigned to an application in Azure AD are synchronized.
59
+
## Step 3. Add Asana from the Azure AD application gallery
34
60
35
-
Before you configure and enable the provisioning service, you must decide which users in Azure AD need access to your Asana app. Then you can assign these users to your Asana app by following the instructions here:
61
+
Add Asana from the Azure AD application gallery to start managing provisioning to Asana. If you have previously setup Asana 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).
36
62
37
-
[Assign a user to an enterprise app](../manage-apps/assign-user-or-group-access-portal.md)
63
+
## Step 4. Define who will be in scope for provisioning
38
64
39
-
### Important tips for assigning users to Asana
65
+
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).
40
66
41
-
We recommend that you assign a single Azure AD user to Asana to test the provisioning configuration. Additional users can be assigned later.
67
+
* When assigning users and groups to Asana, you must select a role other than **Default Access**. Users with the Default Access role are excluded from provisioning and will be marked as not effectively entitled in the provisioning logs. If the only role available on the application is the default access role, you can [update the application manifest](../develop/howto-add-app-roles-in-azure-ad-apps.md) to add more roles.
42
68
43
-
## Configure user provisioning to Asana
69
+
* 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).
44
70
45
-
This section guides you through connecting your Azure AD to Asana user account provisioning API. You also configure the provisioning service to create, update, and disable assigned user accounts in Asana based on user assignments in Azure AD.
46
71
47
-
> [!TIP]
48
-
> To enable SAML-based single sign-on for Asana, follow the instructions provided in the [Azure portal](https://portal.azure.com). Single sign-on can be configured independently of automatic provisioning, although these two features complement each other.
72
+
## Step 5. Configure automatic user provisioning to Asana
49
73
50
-
### To configure automatic user account provisioning to Asana in Azure AD
74
+
This section guides you through the steps to configure the Azure AD provisioning service to create, update, and disable users and groups in Asana based on user and/or group assignments in Azure AD.
51
75
52
-
1. In the [Azure portal](https://portal.azure.com), browse to the **Azure Active Directory** > **Enterprise Apps** > **All applications** section.
76
+
### To configure automatic user provisioning for Asana in Azure AD:
53
77
54
-
1.If you already configured Asana for single sign-on, search for your instance of Asana by using the search field. Otherwise, select **Add** and search for **Asana** in the application gallery. Select **Asana** from the search results, and add it to your list of applications.
78
+
1.Sign in to the [Azure portal](https://portal.azure.com). Select **Enterprise Applications**, then select **All applications**.
55
79
56
-
1. Select your instance of Asana, and then select the **Provisioning** tab.
1. In the **Admin Credentials** section, input your Asana Tenant URL and Secret Token provided by Asana. Click**Test Connection** to ensure Azure AD can connect to Asana. If the connection fails, contact Asana to check your account setup.
71
95
72
-
e. Update **Name** and **About** and the profile photo as needed. Copy the token in **Token**, and select it in **Save Changes**.
1. In the Azure portal, select **Test Connection**to ensure that Azure AD can connect to your Asana app. If the connection fails, ensure that your Asana account has admin permissions, and try the **Test Connection** step again.
98
+
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.
75
99
76
-
1. Enter the email address of a person or group that you want to receive provisioning error notifications in **Notification Email**. Select the check box underneath.
1.Under the **Mappings** section, select **Synchronize Azure Active Directory Users to Asana**.
104
+
1.In the **Mappings** section, select **Synchronize Azure Active Directory Users to Asana**.
81
105
82
-
1.In the **Attribute Mappings** section, review the user attributes to be synchronized from Azure AD to Asana. The attributes selected as **Matching** properties are used to match the user accounts in Asana for update operations. Select **Save**to commit any changes. For more information, see [Customize user provision attribute mappings](../app-provisioning/customize-application-attributes.md).
106
+
1.Review the user attributes that are synchronized from Azure AD to Asana in the **Attribute-Mapping** section. The attributes selected as **Matching** properties are used to match the user accounts in Asana 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 Asana API supports filtering users based on that attribute. Select the **Save** button to commit any changes.
83
107
84
-
1. To enable the Azure AD provisioning service for Asana, in the **Settings** section, change **Provisioning Status** to **On**.
108
+
|Attribute|Type|Supported for filtering|Required by Asana|
Now the initial synchronization starts for any users assigned to Asana in the **Users** section. The initial sync takes longer to perform than subsequent syncs, which occur approximately every 40 minutes as long as the service is running. Use the **Synchronization Details** section to monitor progress and follow links to provisioning activity logs. The audit logs describe all actions performed by the provisioning service on your Asana app.
118
+
1. Under the **Mappings** section, select **Synchronize Azure Active Directory Groups to Asana**.
119
+
120
+
1. Review the group attributes that are synchronized from Azure AD to Asana in the **Attribute-Mapping** section. The attributes selected as **Matching** properties are used to match the groups in Asana for update operations. Select the **Save** button to commit any changes.
121
+
122
+
|Attribute|Type|Supported for filtering|Required by Asana|
123
+
|---|---|---|---|
124
+
|displayName|String|✓|✓
125
+
|members|Reference|||
126
+
127
+
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).
128
+
129
+
1. To enable the Azure AD provisioning service for Asana, change the **Provisioning Status** to **On** in the **Settings** section.
89
130
90
-
For more information on how to read the Azure AD provisioning logs, see [Report on automatic user account provisioning](../app-provisioning/check-status-user-account-provisioning.md).
131
+
91
132
92
-
## Additional resources
133
+
1. Define the users and groups that you would like to provision to Asana by choosing the appropriate values in **Scope** in the **Settings** section.
93
134
94
-
*[Manage user account provisioning for Enterprise Apps](../app-provisioning/configure-automatic-user-provisioning-portal.md)
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 execute than next cycles, which occur approximately every 40 minutes as long as the Azure AD provisioning service is running.
142
+
143
+
## Step 6. Monitor your deployment
144
+
Once you've configured provisioning, use the following resources to monitor your deployment:
145
+
146
+
* Use the [provisioning logs](../reports-monitoring/concept-provisioning-logs.md) to determine which users have been provisioned successfully or unsuccessfully
147
+
* 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
148
+
* If the provisioning configuration seems to be in an unhealthy state, the application will go into quarantine. Learn more about quarantine states [here](../app-provisioning/application-provisioning-quarantine-status.md).
149
+
150
+
## Change log
151
+
152
+
* 11/06/2021 - Dropped support for **externalId, name.givenName and name.familyName**. Added support for **preferredLanguage , title and urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:department**. And enabled **Group Provisioning**.
153
+
154
+
## More resources
155
+
156
+
*[Managing user account provisioning for Enterprise Apps](../app-provisioning/configure-automatic-user-provisioning-portal.md)
95
157
*[What is application access and single sign-on with Azure Active Directory?](../manage-apps/what-is-single-sign-on.md)
96
-
*[Configure single sign-on](asana-tutorial.md)
158
+
159
+
## Next steps
160
+
161
+
*[Learn how to review logs and get reports on provisioning activity](../app-provisioning/check-status-user-account-provisioning.md)
* A user account in Atlassian Cloud with Admin permissions.
37
37
38
+
> [!NOTE]
39
+
> This integration is also available to use from Azure AD US Government Cloud environment. You can find this application in the Azure AD US Government Cloud Application Gallery and configure it in the same way as you do from public cloud.
40
+
38
41
## Step 1. Plan your provisioning deployment
39
42
1. Learn about [how the provisioning service works](../app-provisioning/user-provisioning.md).
40
43
2. Determine who will be in [scope for provisioning](../app-provisioning/define-conditional-rules-for-provisioning-user-accounts.md).
Copy file name to clipboardExpand all lines: articles/active-directory/saas-apps/blink-provisioning-tutorial.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,6 +30,9 @@ The scenario outlined in this tutorial assumes that you already have the followi
30
30
*[A Blink tenant](https://joinblink.com/pricing)
31
31
* A user account in Blink with Admin permissions.
32
32
33
+
> [!NOTE]
34
+
> This integration is also available to use from Azure AD US Government Cloud environment. You can find this application in the Azure AD US Government Cloud Application Gallery and configure it in the same way as you do from public cloud.
35
+
33
36
## Assigning users to Blink
34
37
35
38
Azure Active Directory uses a concept called *assignments* to determine which users should receive access to selected apps. In the context of automatic user provisioning, only the users and/or group members that have been assigned to an application in Azure AD are synchronized.
* A user account in Cisco Webex with Admin permissions.
32
32
33
+
> [!NOTE]
34
+
> This integration is also available to use from Azure AD US Government Cloud environment. You can find this application in the Azure AD US Government Cloud Application Gallery and configure it in the same way as you do from public cloud.
35
+
33
36
## Adding Cisco Webex from the gallery
34
37
35
38
Before configuring Cisco Webex for automatic user provisioning with Azure AD, you need to add Cisco Webex from the Azure AD application gallery to your list of managed SaaS applications.
0 commit comments