Skip to content
StrikeOps

Administrator Accounts Used for Email and Daily Work

MediumTypical severity Cloud and Microsoft 365CWE-250ATT&CK T1078.004

01Description

Accounts holding privileged Entra ID or Microsoft 365 administrator roles were also the users' everyday accounts, licensed with an Exchange Online mailbox and Microsoft 365 apps and used for email, Teams and web browsing.

02Impact

Phishing, malicious attachments and session token theft are aimed at mailboxes and browsers. When the same account holds an administrator role, a successful phish gives the attacker administrative control rather than a single user's data, and malicious inbox rules or OAuth grants on that account carry administrative weight.

03Severity

Typically

Medium

Typically Medium. Medium by default. High where Global Administrators read email and browse with their privileged account, as one phishing email or malicious attachment then reaches a tenant-wide admin.

04How to verify

  1. 1List members of privileged roles in the Entra admin center (Roles and administrators) or with Get-MgDirectoryRoleMember for each activated role.
  2. 2For each privileged account, check assigned licenses (Get-MgUserLicenseDetail or the user's Licenses blade) for Exchange Online and Microsoft 365 apps.
  3. 3Check the sign-in logs to see whether these accounts sign in to Outlook, Teams and other user applications rather than only admin portals.

Testing note: only test systems you are authorized to test, within the agreed scope and rules of engagement. Verification steps are written for professional testers and avoid destructive techniques.

05Remediation

  1. 1Create separate, cloud-only administrator accounts for each administrator, on the onmicrosoft.com domain or a dedicated admin naming convention, and remove admin roles from daily-use accounts.
  2. 2Do not assign mailbox or productivity licenses to administrator accounts; use only the licenses needed for security features such as Entra ID P1 or P2.
  3. 3Require phishing-resistant MFA for all administrator roles through Conditional Access.
  4. 4Where possible, restrict administrator sign-ins to managed, compliant devices.

06References

Draft findings like this from your own evidence

Book a demo
Book a demo