Azure AD

LiveIdentity & Access

Azure AD connector — read-only, agentless

Audits your Azure AD (Microsoft Entra ID) directory — MFA coverage and Conditional Access, legacy-auth blocking, privileged-role sprawl (Global Admins, admins without MFA, PIM), over-privileged app identities, guests and external collaboration, Identity Protection risk (at-risk / compromised users), group hygiene, and audit-log retention. Identity-infrastructure posture, read-only — distinct from the Microsoft 365 file/content scan.

Ikonekta ang Azure AD ← Bumalik sa lahat ng mga connector

Ano ang aming siniscan

User, group, and role directory metadata — MFA-registration state, guest vs member, sign-in recency, and privileged-role assignments (never credentials)
Conditional Access, external-collaboration and authorization policies, Identity Protection risk state, app (service-principal) role holdings, and audit-log configuration

Read-only na pagsubaybay — walang pagbabago sa iyong Azure AD data maliban kung bubuksan mo ang auto-remediation at magbigay ng write access nang hiwalay.

Bago ka kumonekta

• A Microsoft 365 Global Administrator (or Privileged Role Administrator) who can grant admin consent for the read-only identity scopes
• An Entra app registration consent (the connector reads via Microsoft Graph); Entra ID P1/P2 unlocks the sign-in-log, PIM, and Identity Protection checks

Typical first scan: 2–5 minutes depending on directory size

Permissions na hinihiling

User.Read.AllRead the user directory (display name, sign-in state, guest vs member, MFA registration) to audit account and MFA hygiene — never mailbox, file, or credential contents.
Group.Read.AllRead groups, their membership type, visibility, and owners to find ownerless, public, and guest-bearing groups.
Policy.Read.AllRead Conditional Access, authorization (guest-invite), and authentication policies to audit MFA enforcement and legacy-auth blocking.
IdentityRiskyUser.Read.AllRead Identity Protection risk state (at-risk / confirmed-compromised users) to surface accounts that need attention. Requires Entra ID P2.
AuditLog.Read.AllRead sign-in and audit activity metadata that backs the MFA-coverage and sign-in-log posture checks (no message or file contents).
Directory.Read.AllRead privileged directory-role assignments (Global Administrator and other admin roles) to flag over-broad standing privilege and admins without MFA.
PrivilegedAccess.Read.AzureADRead Privileged Identity Management (PIM) eligible-role schedules to check whether just-in-time activation is in use. Requires Entra ID P2.

Security findings

22 detection rules ay tumatakbo sa bawat Azure AD scan. Bawat finding ay may kasamang plain-language explanation, ang evidence sa likod nito at mga hakbang sa remediation.

CRITICALOver permission
Excessive number of Global Administrators
CRITICALOver permission
Privileged admin account without MFA
CRITICALMisconfig
User with a confirmed account compromise
HIGHMisconfig
Users without multi-factor authentication registered
HIGHMisconfig
User has MFA explicitly disabled
HIGHMisconfig
Legacy (basic) authentication is still allowed
HIGHMisconfig
No Conditional Access policy requires MFA for all users
HIGHOver permission
Excessive number of Privileged Role Administrators
HIGHAI agent
Service principal holds an owner-equivalent directory role
HIGHExternal access
Guest (external) user holds a privileged role
HIGHMisconfig
User flagged at-risk by Identity Protection
MEDIUMMisconfig
No enforced Conditional Access policy exists
MEDIUMMisconfig
Privileged Identity Management is not enabled
MEDIUMExternal access
Guests are allowed to invite other guests
MEDIUMExternal access
Dynamic group silently includes guest members
MEDIUMMisconfig
Microsoft 365 group has public visibility
MEDIUMMisconfig
Audit-log retention is shorter than 30 days
MEDIUMMisconfig
Vendor AI-training data-contribution posture
LOWStale access
Guest account inactive for over 90 days
LOWMisconfig
Group has no owners
LOWMisconfig
No diagnostic settings export the logs
LOWMisconfig
Sign-in logs are unavailable

Paano ikonekta ang Azure AD

Hakbang 1
Mag-sign up o mag-log in sa 8200.dev
Hakbang 2
Pumunta sa Connectors → Azure AD
Hakbang 3
I-click ang Connect at mag-authorize sa pamamagitan ng Azure AD's consent screen
Hakbang 4
Ang 8200.dev ay nag-scan nang automatic — ang mga resulta ay lilitaw sa loob ng ilang minuto

Ikonekta ang iyong unang source sa loob ng ilang minuto — libre, read-only, walang sales call.

Ikonekta ang Azure AD Tingnan ang lahat ng 23 connectors →