Articles on: Team Workspaces

How to configure Curiosity for an O365 Tenant

If your Microsoft Office 365 Tenant requires administrative approval for your users to connect external apps to their account, you might need to pre-authorize the Curiosity applications on your Azure portal.

Attempt to connect all relevant integrations to an account on your tenant
Review the permissions using an administrator account on your tenant
Test the connection on the desktop app

⚠️ You can find more information on how to proceed with Microsoft.

1. Review that users can ask to connect apps on your tenant

The first step is to make sure your tenant users can request to connect apps on your organization. To do so, log into your Azure Portal and navigate to Users > User settings. Ensure the option App registrations is set to Yes. Remember to save any changes you made.

User Settings page

Next, navigate to Enterprise applications, then Consent and permissions. Ensure your tenant is configured to Allow user consent for apps.

If your tenant is configured for Allow user consent for apps from verified publishers, for selected permissions, you'll need to add all the permissions required by each Curiosity app to your list of Low impact permissions, or to perform step 3 for all the Curiosity apps.

If your tenant is configured to Do not allow user consent, you will need to perform step 3 for all the Curiosity apps.

Consent and Permissions page

Now, navigate to Enterprise applications, then User settings, and make sure the option Admin consent requests is set to Yes. If you needed to change it to Yes, you'll also need to add a user, group or role to approve requests. Remember to save your changes.

Enterprise Applications page

2. Check if you need to configure your tenant

Now download the Curiosity app and attempt to connect to the relevant Office365 apps using a normal user account within your tenant. It's important that this account has no administrator rights.

This step is required so that all Curiosity applications are added to the Enterprise Applications list on your tenant.

You can safely ignore any errors at this stage.

You only need to proceed to the next steps for the apps that show Need admin approval or Approval required at this step.

If you see this screen, continue

Further changes are only required for apps where you see this consent screen

3. Authorize the Curiosity apps on your tenant (only if required)

💡 This step is only required for apps where your non-administrator user was shown the Approval required screen above.

Log in to your Azure Portal using your tenant administrator account (or an account with the relevant permissions). Navigate to the Enterprise applications blade, and search for Curiosity in the list. If you do not see the Curiosity apps in this list, you might need to repeat Step 1.

You should find the following apps on your application list:
Curiosity for Teams (77217ab8-1b40-49a7-9608-d1a6b78ec8a9 )
Curiosity for OneDrive (c9c36707-2796-478f-a3b3-f5962a251509)
Curiosity for SharePoint (12715a9d-ca11-4492-9d50-101b52b501d4)
Curiosity for Outlook Calendar (6aea9756-715a-48ab-a12b-e869bf54c48b)
Curiosity for Outlook (ea89a0a7-89ac-43a6-a255-de2fd5ed3ad7)

Please make sure the apps match the unique application identifiers listed above before proceeding. If not, stop and let us know:

Next, open each of the apps on the list for which you had to request admin consent in Step 3 above, navigate to Permissions under the Security sub-group, and click on the option Grant admin consent for [your tenant name], as shown below:

Grant admin consent

A popup should open, requesting you to review the permissions required by the app.

Click Accept to continue.

After that, return to the Permissions list. It should show all the permissions added to the app under your tenant as Granted through Admin consent and granted by An administrator. It might take a few instants for the list to be updated - refresh the page if nothing is showing after a few moments.

⚠️ Repeat this step for each of the Curiosity apps listed above that required admin consent earlier.

4. Test the desktop app connections using a non-administrator account

Now try to connect all the relevant apps to the Curiosity desktop app using a non-administrator account. To do so:
Open the Curiosity app
In the left bar hover over Apps and click + (Connect more apps)
Click Connect for each app you want to connect

Curiosity connect apps interface

You should now be able to connect all the apps without needing to request admin approval. These prompts will have an Accept button for the user to agree with the permissions, as shown below.

This is the message your user account should see

If any apps are still showing the Approval required consent screen, you might need to wait a few hours until the permissions propagate correctly on your tenant. Please reach out to your Azure support if this is still the case after a few hours.

Invalid consent prompt for non-admin user

Updated on: 04/02/2024

Was this article helpful?

Share your feedback


Thank you!