1. Resources
  2. Detection rules
  3. Full Access or Send As Granted on Another Mailbox

Full Access or Send As Granted on Another Mailbox detection rules

An attacker with an Exchange admin role, or control of an account that has one, grants an account they hold Full Access or Send As on a target mailbox. They can then read it and send as its owner without the owner's password.

Platform
Microsoft Exchange
Severity
High
Log source
Microsoft 365 unified audit log (Exchange)
Last updated
Rule formats
Sigmaand queries for: SplunkMicrosoft SentinelIBM QRadar
What an attacker needs
An account that can modify recipients, by default a member of Organization Management or Recipient Management, and a second identity to receive the permission.
Impact
Durable access to the target's mail that survives the target's password reset, including reading reset links and approvals and sending mail as a trusted person.
Response
Remove the permission and block the delegate account itself, then contain the account that granted it and take away its Exchange administration roles.
Mitigation
Keep Organization Management, Recipient Management and Exchange Administrator small, and review delegates on executive, finance and administrator mailboxes on a schedule.
Operations
Add-MailboxPermissionAddFolderPermissionsModifyFolderPermissionsUpdateFolderPermissionsAdd-MailboxFolderPermissionSet-MailboxFolderPermissionAdd-RecipientPermission

How the attack works

Exchange lets one identity work in another identity's mailbox. Add-MailboxPermission with the FullAccess right lets the delegate open the mailbox and read and manage its contents. Add-RecipientPermission with SendAs (Exchange Online; on-premises the same right is the Send As extended right set with Add-ADPermission) lets the delegate send messages that appear to come directly from the mailbox. Neither needs the mailbox owner's password or MFA, and neither is visible to the owner. A narrower grant works the same way: Add-MailboxFolderPermission and Set-MailboxFolderPermission give a user rights on a single folder, such as the Inbox, without Full Access on the mailbox. One rule on this page matches these two cmdlets when the right allows reading the items in the folder. Another reads the mailbox audit records AddFolderPermissions and ModifyFolderPermissions, which a folder permission set from inside the mailbox writes, and a third the ChangePermission and ChangeOwner rights of Add-MailboxPermission.

Attackers add these permissions after they reach an account that can manage recipients, for example a member of Organization Management or Recipient Management, or an Exchange Administrator in Microsoft Entra ID. The target is usually an executive, finance or administrator mailbox. Exchange Online writes both cmdlets to the Microsoft 365 unified audit log with the mailbox in ObjectId and the delegate in Parameters.

What an attacker needs

  • An account or application whose management roles include these cmdlets. By default the members of Organization Management and Recipient Management can modify recipients.
  • A second identity under the attacker's control to receive the permission.

Impact

Durable access to the target's mail that survives the target's password reset: reading password reset links, approvals and incident response mail, and sending internal mail as a trusted person. On an administrator's mailbox this is a path to the accounts and systems that send it recovery or approval mail.

Detection rules

Change Permission or Change Owner Right Granted on a Mailbox

Detects Add-MailboxPermission in Exchange Online with the ChangePermission or ChangeOwner access right. Microsoft documents ChangePermission as the right to change the permissions on the mailbox and ChangeOwner as the right to change the owner of the mailbox. Neither opens the mailbox by itself, but a holder of ChangePermission can grant permissions on the mailbox, including Full Access for itself, at a later time, so the grant works as a quiet first step that the Full Access rule of this page does not see. The right is matched as text in the Parameters array. Microsoft documents that system accounts of the service run Add-MailboxPermission for the maintenance of system mailboxes, so callers that start with NT AUTHORITY or NT SERVICE are excluded. Requires Microsoft 365 audit logging and the Exchange records of the unified audit log in the SIEM.

LevelMediumStatusExperimentalLog sourceMicrosoft 365 unified audit log (Exchange)
title: Change Permission or Change Owner Right Granted on a Mailbox
id: c7f54cef-0b51-4717-b0be-29412bc012f3
status: experimental
description: >-
  Detects Add-MailboxPermission in Exchange Online with the ChangePermission
  or ChangeOwner access right. Microsoft documents ChangePermission as the
  right to change the permissions on the mailbox and ChangeOwner as the
  right to change the owner of the mailbox. Neither opens the mailbox by
  itself, but a holder of ChangePermission can grant permissions on the
  mailbox, including Full Access for itself, at a later time, so the grant
  works as a quiet first step that the Full Access rule of this page does
  not see. The right is matched as text in the Parameters array. Microsoft
  documents that system accounts of the service run Add-MailboxPermission
  for the maintenance of system mailboxes, so callers that start with NT
  AUTHORITY or NT SERVICE are excluded. Requires Microsoft 365 audit logging
  and the Exchange records of the unified audit log in the SIEM.
references:
  - https://learn.microsoft.com/en-us/powershell/module/exchangepowershell/add-mailboxpermission
  - https://learn.microsoft.com/en-us/powershell/module/exchangepowershell/get-mailboxpermission
  - https://learn.microsoft.com/en-us/purview/audit-log-activities#exchange-mailbox-activities
  - https://attack.mitre.org/techniques/T1098/002/
author: Forestall
date: 2026-11-18
tags:
  - attack.persistence
  - attack.privilege-escalation
  - attack.t1098.002
logsource:
  product: m365
  service: exchange
detection:
  selection:
    Operation: Add-MailboxPermission
    Parameters|contains:
      - ChangePermission
      - ChangeOwner
  filter_system:
    UserId|startswith:
      - NT AUTHORITY
      - NT SERVICE
  condition: selection and not filter_system
falsepositives:
  - Migration and provisioning tools that set mailbox permissions in bulk. Confirm the tool and allow-list its account in UserId after review.
  - Grants of these rights are rare in Exchange Online. Treat a grant to a user account, or by an administrator outside a change, as needing a request.
level: medium

False positives

  • Migration and provisioning tools that set mailbox permissions in bulk. Confirm the tool and allow-list its account in UserId after review.
  • Grants of these rights are rare in Exchange Online. Treat a grant to a user account, or by an administrator outside a change, as needing a request.

Full Access Granted on a Mailbox

Detects Add-MailboxPermission with the FullAccess right in Exchange Online, which lets the delegate open another mailbox and read and manage its contents. Microsoft documents that system accounts of the service (NT AUTHORITY\SYSTEM and NT SERVICE accounts) run this cmdlet for maintenance of system mailboxes; they are excluded. Requires Microsoft 365 audit logging and the Exchange records of the unified audit log in the SIEM.

LevelMediumStatusExperimentalLog sourceMicrosoft 365 unified audit log (Exchange)
title: Full Access Granted on a Mailbox
id: c8cc0d71-b555-4bd2-86db-330284c91c10
status: experimental
description: >-
  Detects Add-MailboxPermission with the FullAccess right in Exchange Online,
  which lets the delegate open another mailbox and read and manage its
  contents. Microsoft documents that system accounts of the service (NT
  AUTHORITY\SYSTEM and NT SERVICE accounts) run this cmdlet for maintenance of
  system mailboxes; they are excluded. Requires Microsoft 365 audit logging and
  the Exchange records of the unified audit log in the SIEM.
references:
  - https://attack.mitre.org/techniques/T1098/002/
  - https://learn.microsoft.com/en-us/purview/audit-log-activities#exchange-mailbox-activities
author: Forestall
date: 2026-11-11
tags:
  - attack.persistence
  - attack.privilege-escalation
  - attack.t1098.002
logsource:
  product: m365
  service: exchange
detection:
  selection:
    Operation: Add-MailboxPermission
    Parameters|contains: FullAccess
  filter_system:
    UserId|startswith:
      - NT AUTHORITY
      - NT SERVICE
  condition: selection and not filter_system
falsepositives:
  - Shared mailbox onboarding, executive assistant delegation and mailbox migrations. Allow-list the provisioning accounts in UserId, and keep alerting on grants over administrator, finance and executive mailboxes.
level: medium

False positives

  • Shared mailbox onboarding, executive assistant delegation and mailbox migrations. Allow-list the provisioning accounts in UserId, and keep alerting on grants over administrator, finance and executive mailboxes.

Mailbox Folder Permission Added or Changed From a Mail Client

Detects the Exchange mailbox activities AddFolderPermissions and ModifyFolderPermissions. Microsoft documents them as a folder permission that was added or changed, and explains that folder permissions control which users in the organization can access the folders of a mailbox and the messages in them. Its mailbox auditing page states that these values are included in the UpdateFolderPermissions mailbox action, which is audited by default for owners, delegates and admins, so the rule accepts that name as well. These are mailbox audit records, not the Add-MailboxFolderPermission and Set-MailboxFolderPermission cmdlets that the folder rule of this page reads, so they cover a permission set from inside the mailbox, for example by an attacker who holds the owner's session and shares the Inbox with an account they control. The rule matches the operation only. Microsoft's schema places the folder in Item.ParentFolder (Path, Name) and the grantee and the rights in its MemberUpn and MemberRights properties, which are not mapped here, so read them in the event. Requires Microsoft 365 audit logging and the Exchange records of the unified audit log in the SIEM.

LevelLowStatusExperimentalLog sourceMicrosoft 365 unified audit log (Exchange)
title: Mailbox Folder Permission Added or Changed From a Mail Client
id: 6f1cbc83-888d-430a-b26e-952b65ddd2a0
status: experimental
description: >-
  Detects the Exchange mailbox activities AddFolderPermissions and
  ModifyFolderPermissions. Microsoft documents them as a folder permission
  that was added or changed, and explains that folder permissions control
  which users in the organization can access the folders of a mailbox and
  the messages in them. Its mailbox auditing page states that these values
  are included in the UpdateFolderPermissions mailbox action, which is
  audited by default for owners, delegates and admins, so the rule accepts
  that name as well. These are mailbox audit records, not the
  Add-MailboxFolderPermission and Set-MailboxFolderPermission cmdlets that
  the folder rule of this page reads, so they cover a permission set from
  inside the mailbox, for example by an attacker who holds the owner's
  session and shares the Inbox with an account they control. The rule
  matches the operation only. Microsoft's
  schema places the folder in Item.ParentFolder (Path, Name) and the grantee
  and the rights in its MemberUpn and MemberRights properties, which are not
  mapped here, so read them in the event. Requires Microsoft 365 audit
  logging and the Exchange records of the unified audit log in the SIEM.
references:
  - https://learn.microsoft.com/en-us/purview/audit-log-activities#exchange-mailbox-activities
  - https://learn.microsoft.com/en-us/purview/audit-mailboxes
  - https://learn.microsoft.com/en-us/office/office-365-management-api/office-365-management-activity-api-schema#exchange-mailbox-schema
  - https://attack.mitre.org/techniques/T1098/002/
author: Forestall
date: 2026-11-18
tags:
  - attack.persistence
  - attack.privilege-escalation
  - attack.t1098.002
logsource:
  product: m365
  service: exchange
detection:
  selection:
    Operation:
      - AddFolderPermissions
      - ModifyFolderPermissions
      - UpdateFolderPermissions
  condition: selection
falsepositives:
  - Users who share their calendar or a folder with colleagues in Outlook, which is common. Escalate permissions on the Inbox or on the root of the mailbox, grants to the Default or Anonymous user, and changes made from an unusual client address.
level: low

False positives

  • Users who share their calendar or a folder with colleagues in Outlook, which is common. Escalate permissions on the Inbox or on the root of the mailbox, grants to the Default or Anonymous user, and changes made from an unusual client address.

Read Access Granted on a Mailbox Folder

Detects Add-MailboxFolderPermission and Set-MailboxFolderPermission in Exchange Online with an access right that lets the grantee read the items in the folder: the roles Owner, PublishingEditor, Editor, PublishingAuthor, Author, NonEditingAuthor and Reviewer, or the individual permission ReadItems. A permission on the Inbox or on the root of the mailbox gives another user standing access to mail without Full Access on the mailbox. The right is matched as text in the Parameters array and the folder is not tested, so calendar permissions set by administrators match as well. Permissions changed in an Outlook client are recorded as mailbox audit actions and are not read by this rule. Requires Microsoft 365 audit logging and the Exchange records of the unified audit log in the SIEM.

LevelLowStatusExperimentalLog sourceMicrosoft 365 unified audit log (Exchange)
title: Read Access Granted on a Mailbox Folder
id: 34dfd398-67ba-4f81-9c0f-763708dc2939
status: experimental
description: >-
  Detects Add-MailboxFolderPermission and Set-MailboxFolderPermission in
  Exchange Online with an access right that lets the grantee read the items in
  the folder: the roles Owner, PublishingEditor, Editor, PublishingAuthor,
  Author, NonEditingAuthor and Reviewer, or the individual permission
  ReadItems. A permission on the Inbox or on the root of the mailbox gives
  another user standing access to mail without Full Access on the mailbox. The
  right is matched as text in the Parameters array and the folder is not
  tested, so calendar permissions set by administrators match as well.
  Permissions changed in an Outlook client are recorded as mailbox audit
  actions and are not read by this rule. Requires Microsoft 365 audit logging
  and the Exchange records of the unified audit log in the SIEM.
references:
  - https://attack.mitre.org/techniques/T1098/002/
  - https://learn.microsoft.com/en-us/powershell/module/exchangepowershell/add-mailboxfolderpermission
  - https://learn.microsoft.com/en-us/powershell/module/exchangepowershell/set-mailboxfolderpermission
  - https://learn.microsoft.com/en-us/purview/audit-log-activities#exchange-admin-activities
author: Forestall
date: 2026-11-16
tags:
  - attack.persistence
  - attack.privilege-escalation
  - attack.t1098.002
logsource:
  product: m365
  service: exchange
detection:
  selection:
    Operation:
      - Add-MailboxFolderPermission
      - Set-MailboxFolderPermission
    Parameters|contains:
      - Owner
      - Editor
      - Author
      - Reviewer
      - ReadItems
  condition: selection
falsepositives:
  - Calendar delegation and shared folder setup by administrators and provisioning scripts. Read the folder in the Identity parameter and the grantee in User, and keep alerting on the Inbox, on the root of the mailbox and on grants to the Default or Anonymous user.
  - The text match also hits the individual permission FolderOwner, which does not allow reading items, and mailbox or user names that contain one of the words.
level: low

False positives

  • Calendar delegation and shared folder setup by administrators and provisioning scripts. Read the folder in the Identity parameter and the grantee in User, and keep alerting on the Inbox, on the root of the mailbox and on grants to the Default or Anonymous user.
  • The text match also hits the individual permission FolderOwner, which does not allow reading items, and mailbox or user names that contain one of the words.

Send As Granted on a Mailbox or Group

Detects Add-RecipientPermission in Exchange Online. The cmdlet grants the SendAs right, the only access right it accepts, which lets the trustee send messages that appear to come directly from the target mailbox, mail user or group. Requires Microsoft 365 audit logging and the Exchange records of the unified audit log in the SIEM.

LevelMediumStatusExperimentalLog sourceMicrosoft 365 unified audit log (Exchange)
title: Send As Granted on a Mailbox or Group
id: f9a1dad4-fcf4-461d-8678-941cd0d05965
status: experimental
description: >-
  Detects Add-RecipientPermission in Exchange Online. The cmdlet grants the
  SendAs right, the only access right it accepts, which lets the trustee send
  messages that appear to come directly from the target mailbox, mail user or
  group. Requires Microsoft 365 audit logging and the Exchange records of the
  unified audit log in the SIEM.
references:
  - https://attack.mitre.org/techniques/T1098/002/
  - https://learn.microsoft.com/en-us/powershell/module/exchangepowershell/add-recipientpermission
author: Forestall
date: 2026-11-11
tags:
  - attack.persistence
  - attack.privilege-escalation
  - attack.t1098.002
logsource:
  product: m365
  service: exchange
detection:
  selection:
    Operation: Add-RecipientPermission
  condition: selection
falsepositives:
  - Shared mailbox and distribution group onboarding. Allow-list the provisioning accounts in UserId after review, and keep alerting on grants over administrator, finance and executive mailboxes.
level: medium

False positives

  • Shared mailbox and distribution group onboarding. Allow-list the provisioning accounts in UserId after review, and keep alerting on grants over administrator, finance and executive mailboxes.

Detection logic

Patterns that need more than one event, a baseline or knowledge of your own environment. Each is a hypothesis to build and tune in your SIEM, not a ready rule.

Full Access granted, then the new delegate syncs or reads the mailbox

Detection hypothesisSequence of eventsJoins two logs

A delegate added for an assistant or a shared mailbox opens it over the following days, a few folders at a time. An attacker who granted Full Access to an account they control reads the target mailbox at once, often with a client that syncs whole folders. MailItemsAccessed records who read which mailbox, as which logon type, and whether a folder was synced or single messages were opened, so the grant can be followed to its use.

  1. Unified audit log, Exchange admin records: Add-MailboxPermission with FullAccess in Parameters. Take the mailbox from ObjectId and the delegate from the User value in Parameters.
  2. Exchange mailbox records within 24 hours: MailItemsAccessed whose MailboxOwnerUPN is that mailbox and whose UserId is the delegate. Microsoft documents LogonType 2 for a delegate, and notes that an admin with Full Access is also logged as a delegate.
  3. Read MailAccessType in OperationProperties. Microsoft states that a Sync record stands for a whole folder that was downloaded, so treat every item in it as read. For Bind records, add up OperationCount.
  4. Alert on any Sync record, or when the Bind count passes a starting value such as 100 messages, and raise the priority when ClientIPAddress or ClientInfoString is new for the delegate.

EventsAdd-MailboxPermissionMailItemsAccessed

LimitsAn assistant who sets up a manager's mailbox in desktop Outlook also syncs it on the first day. Microsoft enables MailItemsAccessed by default only for users with an Office 365 or Microsoft 365 E3 or E5 license, and a grant through a group or a delegate that never reads the mailbox is not followed. The 24 hours and the count are starting points.

Triage

  • Read ObjectId (the mailbox) and the User or Trustee value in Parameters (the delegate), and UserId (who granted it). A grant to the granting account itself is the pattern to look for.
  • Match the grant to a request. Shared mailbox onboarding and executive assistant delegation are normal; a grant on an administrator or finance mailbox outside a change is not.
  • Look at what the delegate did next in the mailbox audit records, and whether the granting account showed risky sign-ins.
  • Remove unexplained permissions and treat the granting account as compromised until shown otherwise.

Response

Once the attack is confirmed:

  1. Block the delegate account, not only the permission. Disable it, or revoke its sessions and reset its credentials, because it is the identity the attacker reads the mailbox with.
  2. Contain the account that granted the permission. Revoke its sessions, reset its credentials and remove it from Organization Management, Recipient Management or the Exchange Administrator role until the grant is explained.
  3. List every mailbox on which the same delegate holds Full Access or Send As, and every grant made by the same administrator in that period, and remove the unexplained ones together.
  4. Check the target mailbox for what the delegate left behind, such as inbox rules, forwarding and messages sent as the owner. Tell the recipients of those messages that they did not come from the owner.
  5. Replace what the mailbox exposed, such as password reset links, approvals and credentials sent by mail. For an administrator's mailbox, review the accounts and systems that send it recovery or approval mail.

Mitigation

  • Keep Organization Management, Recipient Management and the Exchange Administrator role small, and assign them through just-in-time elevation.
  • Give privileged accounts no mailbox where you can, and never deliver password reset or approval mail for administrators to a mailbox that others can open.
  • Review mailbox and Send As permissions on executive, finance and administrator mailboxes on a schedule, and remove delegates nobody can explain.
  • Keep mailbox auditing on, so delegate activity (FolderBind, SendAs, MailItemsAccessed) is recorded afterwards.

Frequently asked questions

Will the mailbox owner notice that someone else has access?

No. Neither Full Access nor Send As is visible to the owner, and neither needs the owner's password or MFA. Administrators can see the grant in the unified audit log, with the mailbox in ObjectId and the delegate in Parameters, and in a review of mailbox permissions.

Which records show what the delegate did in the mailbox?

With mailbox auditing on, delegate activity is recorded afterwards in the mailbox audit records, for example FolderBind, SendAs and MailItemsAccessed. The rules on this page see only the grant. What was read or sent has to come from those records, and the detection logic on this page joins the grant with the MailItemsAccessed records of the new delegate.

Why are callers that start with NT AUTHORITY or NT SERVICE excluded from the Full Access rule?

Microsoft documents that system accounts of the service run `Add-MailboxPermission` for the maintenance of system mailboxes. Those events are not administrator actions, so the rule leaves them out. Every other caller is matched, including provisioning accounts that you may want to allow-list after review.

Does the Send As rule cover Exchange Server on premises?

No. The rule matches `Add-RecipientPermission` in the Exchange Online records of the unified audit log. On premises the same right is the Send As extended right, set with `Add-ADPermission`, and this rule does not see it.

References

We respect your privacy

We use cookies to keep this site secure and working properly. With your permission, we also use optional cookies to understand usage and improve the experience. Cookie Policy

You can change your choice at any time.