Posture setup

Posture credentials setup

Prepare Azure or Microsoft 365 posture credentials and map each input field required by the Posture connector form.

Updated September 11, 2026 | 9 min

App-only Microsoft connector In-app posture setup page

Auth mode and baseline

If the tenant uses the auto-managed Microsoft connector, stop here: it provisions the Microsoft 365 posture connector itself, shares the per-tenant app credential, rotates it, and queues the first scan. Nothing on this page is needed for Microsoft 365 posture in that case. This page is for delegated and app-only Microsoft connectors, and for Azure subscription posture.
Manually created posture connectors support client-secret authentication only.
Required in all providers: client_id, tenant_guid, client_secret.
Connector creation queues an initial posture scan immediately.
Credentials are encrypted at rest through the posture credential protection service.

Field mapping for the ITDR form

ITDR field	Customer source	Required for
Client ID	Microsoft Entra app registration -> Application (client) ID	Azure and Microsoft 365 posture
Tenant GUID	Microsoft Entra ID -> Overview -> Tenant ID	Azure and Microsoft 365 posture
Client secret	App registration -> Certificates & secrets -> secret value	Azure and Microsoft 365 posture
Subscription IDs	Azure portal -> Subscriptions -> Subscription ID	Azure posture only
Tenant domain	Primary verified Microsoft tenant domain	Recommended for Microsoft 365 posture
Notes	Permissions granted, owner, rotation date, onboarding context	Recommended for customer handoff

Azure posture connector

Connector provider: Azure posture.

Required fields: Client ID, Tenant GUID, Client secret, and one or more Subscription IDs.

Optional fields: tenant domain and implementation notes.

Microsoft 365 posture connector

Connector provider: Microsoft 365 posture.

Required fields: Client ID, Tenant GUID, Client secret.

Recommended fields: primary tenant domain and notes explaining granted permissions.

Setup flow in ITDR

Open Posture in ITDR and use Add connector.
Choose provider (Azure posture or Microsoft 365 posture).
Enter required credential fields and save.
Wait for connector_setup run to start, then review findings and run summary.
Use posture remediation and risk-acceptance workflows after first findings import.

Detailed permission matrices for posture providers depend on which posture checks are enabled. Use the provider documentation linked in the in-app setup page for the latest required grant sets.

Validation checklist

Connector status should move from pending_setup to active after successful run.
Runs tab should show new run records with trigger `connector_setup` or `manual`.
Findings should populate by severity and provider.
Export (JSON/CSV) and run artifacts should download successfully for completed runs.

Setup worksheet

Have the customer prepare these values before opening the posture connector form.

Provider: Azure posture or Microsoft 365 posture
Client ID: <application client id>
Tenant GUID: <directory tenant id>
Client secret: <secret value, share only through approved secret channel>
Subscription IDs: <comma-separated subscription ids, Azure posture only>
Tenant domain: <example.onmicrosoft.com or primary verified domain>
Secret expires: <date>
Permissions/roles granted: <reader/security reader/global reader/etc. based on customer policy>