All articles

Wrike & Azure Active Directory User Provisioning

Table 49. Availability - Legacy plans


Overview

With SCIM protocol, admins can set up automatic user provisioning and deprovisioning for Wrike with Azure Active Directory (Azure AD).

Set up Wrike with the System for Cross Identity Management (SCIM) standard to automatically provision or deprovision users based on their status in Azure AD.

  • Automatic provisioning: Azure AD users are automatically provisioned for Wrike.

  • Synced user attributes: User attributes are automatically updated in Wrike when they're updated in Azure AD.

  • Automatic deactivation: Wrike users are automatically deactivated in Wrike when they're deactivated in Azure AD.

This page is about integrating Wrike with Azure AD SCIM. We have a separate page on setting up SSO to Wrike through Azure AD.

Note

Members added through SCIM are billable as soon as they're provisioned.

Set up Wrike with Azure AD SCIM

You must have permission to Configure advanced security settings in Wrike and be an Azure AD admin to set up Wrike with Azure AD SCIM. We recommend setting up SSO with Azure AD first.

Step 1: Add approved domains

Only users from approved domains will be automatically provisioned to Wrike.

Step 2: Find and note the SCIM URL

  1. Open your Wrike workspace.

  2. Click your profile picture in the view’s upper right-hand corner.

  3. Select Apps & Integrations.

  4. Click Azure AD in the list of apps and open the SCIM tab.

  5. Scroll to the bottom of the pop-up and copy the SCIM URL. You’ll be using it in a few steps.

  6. Close the Azure AD pop-up (but stay in Wrike) and move to Step 3.

Step 3: Obtain the OAUTH token

  1. Click API from the left-hand side of the Apps & Integrations page.

  2. Enter a name in the App name field (we suggest Azure AD SCIM).

  3. Click Create new.

  4. (Optional) Add an app description.

  5. Scroll to the bottom of the page and click Create v4 Token.

  6. Enter your password and click Obtain token.

  7. Copy the token and save it somewhere. You’ll need to enter this information in Azure AD.

    Important

    You’re only shown your token once, so make sure you save it prior to moving on to the next steps.

  8. Click Save.

Step 4: Finalize the setup from Azure AD

  1. Sign in to your Azure AD domain at <yourorganization>.Azure AD.com.

  2. Click Enterprise applications on the left.

  3. Find and select Wrike.

  4. Select Provisioning from the menu panel on the left.

  5. Under the Provisioning Mode menu, select Automatic.

  6. Scroll down to the Admin Credentials section.

  7. In the field next to Tenant URL, paste the base URL that you copied in Step 2.

  8. In the field next to Secret Token, paste the token you copied in Step 3.

  9. Click the Test connection button to confirm that all your settings are correct.

  10. If the test is successful, click the Save button at the top of the window. If not, double-check your settings or contact Wrike Support for help.

  11. Scroll down to the Settings section.

  12. Set the provisioning status to On.

  13. In the Scope drop-down menu, select which events you want to synchronize between Wrike and Azure: Sync only assigned users and groups or Sync all users and groups.

  14. Click Save at the top of the window to start the provisioning service.

Note

Make sure that all relevant users and groups are assigned to Wrike’s app.

Synced attributes

The following attributes are synced from Azure AD to Wrike:

  • Username

  • Given name

  • Family name

  • Primary email

  • Job title

  • Primary phone number

  • Organization name

  • Department

  • Wrike user type

    Note

    Specifying the Wrike user type (Regular, External, and Collaborator) is a custom attribute. By default, Regular users are created.

Troubleshooting

Missing attributes

If certain user attributes (e.g., phone number, department, or secondary emails) are filled in Wrike but missing in Azure AD, the information remains in Wrike even after user provisioning.

User provisioning/deprovisioning

If a user doesn't get provisioned or deprovisioned:

  • Check the System Log in the Azure AD administration portal to see if a SCIM provisioning attempt is listed there.

    • If there is no provisioning attempt listed, make sure that users are properly assigned to Wrike’s application in Azure AD.

    • If an error is listed, please contact our Support Team and provide error details.

Top