Tutorial: Configure Coda for automatic user provisioning

This tutorial describes the steps you need to perform in both Coda and Microsoft Entra ID to configure automatic user provisioning. When configured, Microsoft Entra ID automatically provisions and de-provisions users to Coda 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.

Capabilities Supported

• Create users in Coda
• Remove users in Coda when they do not require access anymore
• Keep user attributes synchronized between Microsoft Entra ID and Coda
• Single sign-on to Coda (recommended)

Prerequisites

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

• A Microsoft Entra tenant
• A user account in Microsoft Entra ID with permission to configure provisioning (e.g. Application Administrator, Cloud Application administrator, Application Owner, or Global Administrator).
• A Coda Enterprise administrator account.

Step 1: Plan your provisioning deployment

1. Learn about how the provisioning service works.
2. Determine who will be in scope for provisioning.
3. Determine what data to map between Microsoft Entra ID and Coda.

Step 2: Configure Coda to support provisioning with Microsoft Entra ID

1. Open your Organization Admin Console by selecting Organization Settings under the ... menu below your workspace.

   

2. Ensure Provision with SCIM is enabled.

3. Note the SCIM Base URL and SCIM Bearer Token. If there is no Bearer Token, click Generate New Token.

Step 3: Add Coda from the Microsoft Entra application gallery

Add Coda from the Microsoft Entra application gallery to start managing provisioning to Coda. If you have previously setup Coda 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.

Step 4: Define who will be in scope for provisioning

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. If you choose to scope who will be provisioned to your app based on assignment, you can use the following steps 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.

• 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.

• 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.

Step 5: Configure automatic user provisioning to Coda

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

To configure automatic user provisioning for Coda 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

   

3. In the applications list, select Coda.

   

4. Select the Provisioning tab.

   

5. Set the Provisioning Mode to Automatic.

   

6. Under the Admin Credentials section, input your Coda Tenant URL and Secret Token retrieved earlier in Step 2. Click Test Connection to ensure Microsoft Entra ID can connect to Coda. If the connection fails, ensure your Coda account has Admin permissions and try again.

   

7. 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.

   

8. Select Save.

9. Under the Mappings section, select Synchronize Microsoft Entra users to Coda.

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

    Attribute	Type
    userName	String
    active	Boolean
    name.givenName	String
    name.familyName	String

11. To configure scoping filters, refer to the following instructions provided in the Scoping filter tutorial.

12. To enable the Microsoft Entra provisioning service for Coda, change the Provisioning Status to On in the Settings section.

    

13. Define the users that you would like to provision to Coda by choosing the desired values in Scope in the Settings section.

    

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

    

This operation starts the initial synchronization cycle of all users 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

Once you've configured provisioning, use the following resources to monitor your deployment:

1. Use the provisioning logs to determine which users have been provisioned successfully or unsuccessfully
2. Check the progress bar to see the status of the provisioning cycle and how close it is to completion
3. If the provisioning configuration seems to be in an unhealthy state, the application will go into quarantine. Learn more about quarantine states here.

Additional resources

• Managing user account provisioning for Enterprise Apps
• What is application access and single sign-on with Microsoft Entra ID?

Next steps

• Learn how to review logs and get reports on provisioning activity