Connector setup
Microsoft connector (app-only mode)
Use client credentials for tenant ingestion, map required Graph application permissions, and verify stable background sync.
Updated May 5, 2026 | 10 min
When to use app-only mode
Use app-only mode when you need scheduled ingestion independent of an individual delegated refresh token lifecycle.
This mode is generally best for long-running production setups where customer consent and secrets are managed through a service principal governance process.
Microsoft-side preparation
- Create or select a Microsoft Entra app registration for ITDR ingestion.
- Create a client secret and store the secret value securely.
- Capture Tenant ID (Directory ID), Client ID (Application ID), and secret value for ITDR connector setup.
- Grant Graph application permissions required for your target telemetry and containment workflows, then click Admin consent.
Information to collect before opening ITDR
| Customer value | Where to find it | ITDR field |
|---|---|---|
| Microsoft tenant ID | Microsoft Entra admin center -> Overview -> Tenant ID | Microsoft tenant ID |
| Application/client ID | App registrations -> selected app -> Overview -> Application (client) ID | Client ID |
| Client secret value | App registrations -> Certificates & secrets -> New client secret -> Value | Client secret |
| Secret expiration date | Certificates & secrets -> Expires column | Operational note / rotation calendar |
| Admin consent status | API permissions -> Status column | Validation reference |
Permission baseline
ITDR app-only tokens use Microsoft Graph `.default`. Effective permissions are whatever application permissions are granted to the app registration.
Base ingestion
Identity Risk dashboards
Risk enrichment
Containment actions
Workload automation actions
ITDR setup steps
- Open Connectors and choose the app-only connector creation path.
- Provide Microsoft tenant ID, client ID, and client secret.
- Save connector. ITDR validates by requesting a token with scope `https://graph.microsoft.com/.default` and testing organization/user reads.
- After creation, run Sync now and review token lanes, warning buckets, and recent run history.
Validation checklist
- Connector sync status should move from authorized_app_only to healthy or synced_with_warnings after imports run.
- Graph preview should load organization and sample users.
- Secure Score route should return data when security permissions and tenant provisioning are in place.
- Incident response capability panels should not report missing required scopes for planned actions.
Common failure patterns
- Error: Connector already exists for this Microsoft tenant. Action: reuse existing connector or remove old active connector for that tenant ID.
- Error: failed to validate credentials. Action: recheck tenant ID/client ID/secret and verify client secret has not expired.
- Error: missing required scope for action. Action: add that Graph application permission in Entra and re-consent.
Customer handoff template
Use this checklist when a customer admin prepares the connector details before entering them into ITDR.
Tenant ID: <directory tenant id> Client ID: <application client id> Client secret value: <secret value, share only through approved secret channel> Secret expires: <date> Admin consent granted by: <admin name/email> Permissions granted: <paste permission list or screenshot reference>