Skip to content

Connecting

Nemu-x edited this page Jul 14, 2026 · 1 revision

Connecting

Open the Connect tab. You need a Tenant ID and Client ID from your app registration; app-only mode also needs a Client secret.

App-only (client credentials)

Acts as the application, tenant-wide, using the Application permissions you granted.

  1. Pick App-only (client secret).
  2. Enter Tenant ID, Client ID, Client secret.
  3. Connect — the app runs a self-test (GET /organization) and lands on the Dashboard.

Best for automation-style admin work where you act on any user/resource in the tenant.

Delegated (device code)

Acts as you (the signed-in admin), limited to your own rights.

  1. Pick Delegated (device code) — no secret needed.
  2. Connect — a code appears. Open https://microsoft.com/devicelogin, enter it, and sign in.
  3. Once you approve, the app connects.

Requires Allow public client flows = Yes and Delegated permissions on the registration. Best when you don't want the app to have standing tenant-wide access.

Profiles

Tick Remember this profile to save it. Non-secret fields (name, tenant/client id, mode) are stored in a small config file; the client secret is stored only in your OS keychain (Windows Credential Manager / macOS Keychain / Linux Secret Service) — never in plain text. Reconnect later with one click from the profile list.

Domain autocomplete (optional)

Tick Load tenant domains on connect to fetch your verified domains — UPN fields then offer name@yourdomain suggestions as you type.

Read-only mode

Before poking around a production tenant, enable Settings → Read-only. Every write and destructive action is blocked until you turn it off — safe for exploring.

Clone this wiki locally