Skip to content

Latest commit

 

History

History
76 lines (39 loc) · 3.68 KB

File metadata and controls

76 lines (39 loc) · 3.68 KB

Using your own Client ID / Application ID

Easiest Option:

Azure CLI

Note

You can use a custom client ID that belongs to Microsoft Azure CLI 04b07795-8ddb-461a-bbee-02f9e1bf7b46. This is intended for testing only and is not recommended by the maintainers of this repository, as it may violate Microsoft’s Terms of Service. Doing so can bypass the need for an IT Administrator to grant permissions to the application enabling a zero change setup in most tenants and is enterprise friendly. This effectively circumventing the standard consent process. Navigate to the Settings page, check the "Custom Client ID" checkbox, add the aformentioned Clinet Id, click save, and restart the application. See this article for more details on the well-known client ID. https://rakhesh.com/azure/well-known-client-ids/

image

This allows you to use your own enterprise application instead of the default one. Requires the checkbox to be selected and a valid Client ID.

  1. Create an Enterprise application in your Azure AD / Entra tenant:

    image

    image

  2. Select a tenant auth type:

    image

  3. Navigate to App Registrations and go to the Manage > Authentication page:

    image

  4. Select Desktop + Devices and check the following boxes. Add http://localhost as a custom redirect URI:

    image

  5. Add macOS redirect URIs:

    image

  6. Navigate to the API Permissions section and add the following permissions. You may need an admin to grant consent:

    image

  7. You or an admin will have to grant consent to your own application if not granted already:

    image

  8. Open the app and update the Client ID in the settings page, then restart the app:

    image

  9. Upon restart you'll see something similar to this:

    image

The app should now work as normal under your own identity and your own tenant's enterprise application.

Tip: You can also set your own Client ID in Constants.cs and rebuild the application from source. See Building from source.

Using your own Tenant ID / Directory ID

By default, the app signs in using the common Microsoft endpoint and takes the first tenant available. If your organization requires you to authenticate against a specific Azure AD / Entra tenant, you can configure a custom Tenant ID in the settings:

  1. Open the app and navigate to the Settings page.
  2. Check "Use custom Tenant ID / Directory ID (requires application restart)".
  3. Enter your Azure Tenant ID (e.g. 18405e16-1ba4aca2-...).
  4. Restart the application.

This is useful when your tenant admin has restricted sign-in to a specific directory, or when you want to ensure you are authenticating against the correct tenant.

image