01
Create a read-only credential
Create the credential in Microsoft Azure / Entra ID with the minimum read scope, paste it into devguard, and the connection is live. The integration page in the product spells out the exact permissions.
Through Microsoft Graph, devguard verifies your Azure and Entra ID tenant is reachable and that security defaults, Microsoft's baseline MFA posture, are switched on.
3 read-only checks, run on a schedule. Each failure becomes a finding linked to a control — every check is listed, none are “coming soon”.
Connectivity check: fails if the client-credentials token cannot read the tenant organization object from Microsoft Graph.
tenant-reachable
Fails if the tenant does not enforce Entra ID security defaults. Tenants using an equivalent Conditional Access MFA policy instead will report this false — review Conditional Access if so.
security-defaults-enabled
Fails if non-admin users are allowed to register applications (allowedToCreateApps is true), a common privilege-escalation and consent-phishing vector.
authorization-policy-hardened
Bring your current platform's test list — we'll map it against these checks, gap by gap
Setup is minutes, not a migration project — and every step stays on your side
Create the credential in Microsoft Azure / Entra ID with the minimum read scope, paste it into devguard, and the connection is live. The integration page in the product spells out the exact permissions.
The first run starts right after connecting, then repeats on a schedule. Results are timestamped, so your evidence has a history, not a snapshot.
Passing results attach as evidence to the controls they support; failures become findings you triage. When the audit comes, the proof is already connected.
Open any page for its full check register.
You create and scope every credential yourself, and you can revoke it at any time. Checks only read; results and evidence are stored in Switzerland and stay exportable.
Yes. The checks authenticate with a credential you create and scope yourself, and only ever read configuration. devguard holds no write access to Microsoft Azure / Entra ID and remediates nothing silently.
A failed check becomes a finding linked to the control it supports, with the evidence attached. You decide the treatment — nothing pages your engineers and nothing is auto-remediated.
Checks run from Swiss infrastructure, and results and evidence are stored in Switzerland. Everything is exportable — your evidence stays yours.
An app registration with read-only Graph application permissions (Policy.Read.All and Directory.Read.All are typical). devguard authenticates with client credentials and never asks for write scopes.
20 minutes on how you run certification today. Bring your current test or control list and we'll map it against these checks — honestly, gap by gap.