Skip to main content

Managing Caddi Azure Applications Without User Requests

Allow Caddi application usage in restricted environments.

When to use this guide


Use this guide if you are an administrator in your organization’s Azure tenant and your policies restrict users from requesting third-party Entra ID applications. It is intended for organizations that prefer to use Caddi-managed applications rather than configuring a custom Enterprise Application connection.

If your organization allows users to request or directly use third-party Entra ID applications, the steps below are optional. However, completing them in advance can streamline user onboarding.

Prerequisites

Before getting started, you will need your Azure Tenant ID.

To locate your Tenant ID:

  1. Sign in to the Azure portal using an account associated with the relevant tenant.

  2. Use the search bar at the top of the page to navigate to Entra ID.

  3. On the Overview page, locate the Tenant ID.

You can also refer to Microsoft’s documentation here.

Approving Caddi Applications

To approve a Caddi application for your organization, you must generate a consent URL and open it in your browser. This will display the admin consent screen for the application. Granting consent makes the application available to users in your tenant.

This process must be completed individually for each application.

Consent URL Format

https://login.microsoftonline.com/{tenant-id}/adminconsent?client_id={application-client-id}
  • Replace {tenant-id} with your Azure Tenant ID.

  • Replace {application-client-id} with the corresponding application ID from the list below.

Example
If your Tenant ID is example-tenant-id and you want to approve the Caddi Outlook application, use:

https://login.microsoftonline.com/example-tenant-id/adminconsent?client_id=95d49b73-1cec-440d-ac29-42f4a8dd54ab

Caddi Microsoft Entra Application Client IDs

  • OneDrive: 605cbd78-cfb0-4810-8279-80cf4d152cee

  • OneNote: 92f31f6a-683a-45eb-af4e-912bb9c9b107

  • Outlook: 95d49b73-1cec-440d-ac29-42f4a8dd54ab

  • SharePoint: 9c1aebc5-480e-4032-a9f7-cf065e5e5ae2

  • Teams: b7dbe4f6-55e6-426c-a515-128280f0d225

Did this answer your question?