Tutorial: Configure Cisco Webex for automatic user provisioning

The objective of this tutorial is to demonstrate the steps to be performed in Cisco Webex and Microsoft Entra ID to configure Microsoft Entra ID to automatically provision and deprovision users to Cisco Webex.

Note

This tutorial describes a connector built on top of the Microsoft Entra user 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.

This connector is currently in Preview. For more information about previews, see Universal License Terms For Online Services.

Prerequisites

The scenario outlined in this tutorial assumes that you already have the following prerequisites:

  • A Microsoft Entra tenant.
  • A Cisco Webex tenant.
  • A user account in Cisco Webex with Admin permissions.

Note

This integration is also available to use from Microsoft Entra US Government Cloud environment. You can find this application in the Microsoft Entra US Government Cloud Application Gallery and configure it in the same way as you do from public cloud.

Before configuring Cisco Webex for automatic user provisioning with Microsoft Entra ID, you need to add Cisco Webex from the Microsoft Entra application gallery to your list of managed SaaS applications.

To add Cisco Webex from the Microsoft Entra application gallery, perform the following steps:

  1. Sign in to the Microsoft Entra admin center as at least a Cloud Application Administrator.

  2. Browse to Identity > Applications > Enterprise applications > New application.

  3. In the Add from the gallery section, type Cisco Webex, select Cisco Webex from result panel then click Add button to add the application.

    Screenshot shows the Cisco Webex in the results list.

Assigning users to Cisco Webex

Microsoft Entra ID 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 groups that have been "assigned" to an application in Microsoft Entra ID are synchronized.

Before configuring and enabling automatic user provisioning, you should decide which users in Microsoft Entra ID need access to Cisco Webex. Once decided, you can assign these users to Cisco Webex by following the instructions here:

Important tips for assigning users to Cisco Webex

  • It is recommended that a single Microsoft Entra user is assigned to Cisco Webex to test the automatic user provisioning configuration. Additional users may be assigned later.

  • When assigning a user to Cisco Webex, you must select any valid application-specific role (if available) in the assignment dialog. Users with the Default Access role are excluded from provisioning.

Configuring automatic user provisioning to Cisco Webex

This section guides you through the steps to configure the Microsoft Entra provisioning service to create, update, and disable users in Cisco Webex based on user assignments in Microsoft Entra ID.

To configure automatic user provisioning for Cisco Webex in Microsoft Entra ID:

  1. Sign in to the Microsoft Entra admin center as at least a Cloud Application Administrator.

  2. Browse to Identity > Applications > Enterprise applications > Cisco Webex.

    Screenshot shows the Enterprise applications blade.

  3. In the applications list, select Cisco Webex.

    Screenshot shows the Cisco Webex link in the Applications list.

  4. Select the Provisioning tab.

    Screenshot of a menu. Under Manage, Provisioning is highlighted.

  5. Set the Provisioning Mode to Automatic.

    Screenshot of the Provisioning mode list box, with Automatic highlighted.

  6. Under the Admin Credentials section, input the Tenant URL, and Secret Token of your Cisco Webex account.

    Screenshot of the Admin Credentials section. The Tenant U R L and Secret token boxes are highlighted but are empty.

  7. In the Tenant URL field, enter a value in the form of https://api.ciscospark.com/v1/scim/[OrgId]. To obtain [OrgId], sign into your Cisco Webex Control Hub. Click on your organization name on the bottom left and copy the value from Organization ID.

    • To obtain the value for Secret Token, navigate to this URL. From the webex sign in page that appears, sign in with the full Cisco Webex admin account for your organization. An error page appears saying that the site can't be reached, but this is normal.

      Screenshot of a webpage displaying an error message. The message says that the site cannot be reached and includes a few troubleshooting tips.

    • Copy the value of the generated bearer token from the URL as highlighted below. This token is valid for 365 days.

      Screenshot showing a long U R L. Part of the address is indecipherable but is highlighted and labeled Bearer token.

  8. Upon populating the fields shown in Step 5, click Test Connection to ensure Microsoft Entra ID can connect to Cisco Webex. If the connection fails, ensure your Cisco Webex account has Admin permissions and try again.

    Screenshot shows the Tenant URL and Token.

  9. In the Notification Email field, enter the email address of a person or group who should receive the provisioning error notifications and check the checkbox - Send an email notification when a failure occurs.

    Screenshot shows the Notification Email.

  10. Click Save.

  11. Under the Mappings section, select Synchronize Microsoft Entra users to Cisco Webex.

  12. Review the user attributes that are synchronized from Microsoft Entra ID to Cisco Webex in the Attribute-Mapping section. The attributes selected as Matching properties are used to match the user accounts in Cisco Webex for update operations. If you choose to change the matching target attribute, you need to ensure that the Cisco Webex API supports filtering users based on that attribute. Select the Save button to commit any changes.

    Attribute Type Supported for filtering Required by Cisco Webex
    userName String
    name.givenName String
    name.familyName String
    active Boolean
    displayName String
    externalId String
  13. Under the Mappings section, select Synchronize Microsoft Entra groups to Cisco Webex.

  14. Review the group attributes that are synchronized from Microsoft Entra ID to Cisco Webex in the Attribute-Mapping section. The attributes selected as Matching properties are used to match the groups in Cisco Webex for update operations. Select the Save button to commit any changes.

    Attribute Type Supported for filtering Required by Cisco Webex
    displayName String
    members Reference
    externalId String
  15. To configure scoping filters, refer to the following instructions provided in the Scoping filter tutorial.

  16. To enable the Microsoft Entra provisioning service for Cisco Webex, change the Provisioning Status to On in the Settings section.

    Screenshot shows the Provisioning Status Toggled On.

  17. Define the users and/or groups that you would like to provision to Cisco Webex by choosing the desired values in Scope in the Settings section.

    Screenshot shows the Provisioning Scope.

  18. When you are ready to provision, click Save.

    Screenshot shows to Save Provisioning Configuration.

This operation starts the initial synchronization of all users and/or groups defined in Scope in the Settings section. The initial sync takes longer to perform than subsequent syncs, which occur approximately every 40 minutes as long as the Microsoft Entra provisioning service is running. You can use the Synchronization Details section to monitor progress and follow links to provisioning activity report, which describes all actions performed by the Microsoft Entra provisioning service on Cisco Webex.

For more information on how to read the Microsoft Entra provisioning logs, see Reporting on automatic user account provisioning.

Connector limitations

  • Cisco Webex is currently in Cisco's Early Field Testing (EFT) phase. For more information, please contact Cisco's support team.
  • For more information on Cisco Webex configuration, refer to the Cisco documentation here.

Change log

  • 02/07/2023 - Added support for Group Provisioning.

Additional resources

Next steps