1. Resources
  2. Detection rules
  3. Guest Account Promoted to Member

Guest Account Promoted to Member detection rules

An attacker with a user management role changes a guest account they control from Guest to Member. The account gains the default permissions of an employee and leaves the controls that are scoped to guests.

Platform
Microsoft Entra ID
Severity
Medium
Log source
Microsoft Entra ID audit logs
Last updated
MITRE ATT&CK technique
T1098Account Manipulation
Rule formats
Sigmaand queries for: SplunkMicrosoft Sentinel
What an attacker needs
An identity that can edit the properties of users, and a guest account the attacker controls or can sign in to.
Impact
The external account gets the default permissions of a member and falls out of everything that selects guests by user type, such as reviews of guest accounts.
Response
Set the user type of the account back to Guest and revoke its sessions, then remove the applications it registered and the guests it invited as a member.
Mitigation
Keep the roles that can edit users on a small number of accounts protected with phishing-resistant MFA, and alert on every change of user type.
Audit activity
Update user

How the attack works

Every user in Microsoft Entra ID has a user type, Member or Guest. The type describes the relationship of the person to the organization and decides the default permissions. A member can enumerate all users, groups and other directory objects, register applications and invite guests. A guest can read little more than its own profile and the objects it was given access to. Other controls key on the type as well: the guest user access restrictions, dynamic groups with a rule on user.userType, and reviews and reports that list guests.

The type is an ordinary property of the user object. Microsoft documents that it can be converted from Guest to Member and back by editing the user's profile, and says it should change only when the relationship of the person to the organization changes. An attacker who holds a role that can edit users converts an external account they control, for example one that was invited earlier or a compromised partner account. The account keeps its external identity and its sign-in, but the directory now treats it as an internal user.

Core Directory writes the change to the audit log as Update user in the category UserManagement. The modified properties name UserType with the old value Guest and the new value Member. Microsoft's security operations guide for user accounts lists this change as one to monitor and alert on.

What an attacker needs

  • A compromised identity that can edit the properties of users, such as an administrator who manages users, or an application with a Microsoft Graph permission to update users (User.ReadWrite.All, Directory.ReadWrite.All).
  • A guest account the attacker controls or can sign in to.

Impact

The external account receives the default permissions of a member: it can read the whole directory, register applications and invite further guests. It also falls out of everything that selects guests by user type, such as dynamic groups, guest access restrictions and reviews of guest accounts, so it can outlive the clean-up of external access. The change gives no role by itself, but it makes an external account look and behave like an employee.

Detection rules

User Type Changed Between Guest and Member

Detects an Update user event whose modified properties include UserType and carry both values, Guest and Member. Microsoft recommends alerting when a user type changes from Guest to Member. The property name is matched with its quotation marks, as it is written in the modified properties, so that other properties whose name only ends in UserType, such as TargetId.UserType, do not match. The rule does not read the direction. A member converted to a guest matches as well, and the old and the new value in the event tell which one it is.

LevelMediumStatusExperimentalLog sourceMicrosoft Entra ID audit logs
title: User Type Changed Between Guest and Member
id: f2ac8d34-ab45-44ce-a671-ab80f1e276d7
related:
  - id: 8dee7a0d-43fd-4b3c-8cd1-605e189d195e
    type: derived
status: experimental
description: >-
  Detects an Update user event whose modified properties include UserType
  and carry both values, Guest and Member. Microsoft recommends alerting when
  a user type changes from Guest to Member. The property name is matched with
  its quotation marks, as it is written in the modified properties, so that
  other properties whose name only ends in UserType, such as
  TargetId.UserType, do not match. The rule does not read the direction. A
  member converted to a guest matches as well, and the old and the new value
  in the event tell which one it is.
references:
  - https://learn.microsoft.com/en-us/entra/architecture/security-operations-user-accounts
  - https://learn.microsoft.com/en-us/entra/identity/monitoring-health/reference-audit-activities
  - https://learn.microsoft.com/en-us/entra/identity/monitoring-health/troubleshoot-audit-data-verified-domain
  - https://learn.microsoft.com/en-us/entra/external-id/user-properties
  - https://attack.mitre.org/techniques/T1098/
author: Forestall, based on work by MikeDuddington
date: 2026-11-14
tags:
  - attack.persistence
  - attack.privilege-escalation
  - attack.t1098
logsource:
  product: azure
  service: auditlogs
detection:
  selection:
    OperationName: Update user
    Category: UserManagement
    TargetResources|contains|all:
      - '"UserType"'
      - Guest
      - Member
  filter_failed:
    Result: failure
  condition: selection and not filter_failed
falsepositives:
  - Planned conversions, for example a contractor who becomes an employee or the accounts of an acquired company that are turned into members. Match the event to a change record.
  - A member converted to a guest. The rule matches both directions, so read the old and the new value before escalating.
level: medium

False positives

  • Planned conversions, for example a contractor who becomes an employee or the accounts of an acquired company that are turned into members. Match the event to a change record.
  • A member converted to a guest. The rule matches both directions, so read the old and the new value before escalating.

Triage

  • Identify the actor (InitiatedBy) and the account (TargetResources), and read the old and the new value of UserType to confirm the direction of the change.
  • Check whether the conversion was planned, for example a contractor who became an employee or accounts moved during a merger.
  • Find out where the account came from. Look for who invited it and when, and whether the actor of the change is the same identity.
  • Review what the account did after the change, such as directory reads, application registrations, invitations and new group memberships.
  • If the change was not authorized, set the user type back to Guest, revoke the account's sessions and review the actor's other changes.

Response

Once the attack is confirmed:

  1. Set the user type of the account back to Guest and revoke its sessions. Block sign-in for the account if nobody in the organization knows it.
  2. Remove what the account did as a member. Delete the applications it registered, remove the guests it invited and take it out of the groups it joined.
  3. Revoke the sessions and reset the credentials of the identity that changed the user type, and remove the role or Microsoft Graph permission it used.
  4. Assume the account read the directory while it was a member, and take the list of users, groups and applications into account when you judge what the attacker knows.
  5. Confirm that the account is back in the dynamic groups, Conditional Access policies and reviews that select guests, and look for other accounts with an external identity and the user type Member.

Mitigation

  • Keep the roles that can edit users on a small number of accounts protected with phishing-resistant MFA and Privileged Identity Management.
  • Review the applications that hold Microsoft Graph permissions to update users, and remove the permission where it is not needed.
  • In Conditional Access policies for external users, select every external user type, including B2B collaboration member users, so that a converted account stays in scope.
  • Review regularly the accounts that have an external identity but the user type Member, and confirm that each one is intended.
  • Alert on every change of user type and match it to a change record.

Frequently asked questions

Does the rule distinguish a promotion from a demotion?

No. It matches an `Update user` event whose modified properties contain UserType with both values, Guest and Member, so a member converted to a guest matches too. Read the old and the new value in the event before you escalate.

Does the member user type give the account any role?

No. The change gives no role by itself. It gives the default permissions of a member, which include reading all users, groups and other directory objects, registering applications and inviting guests. It also takes the account out of everything that selects guests by user type.

When is a conversion from Guest to Member legitimate?

Microsoft says the user type should change only when the relationship of the person to the organization changes. Typical cases are a contractor who becomes an employee and the accounts of an acquired company. Each one should match a change record.

Do Conditional Access policies for guests still apply to the converted account?

Only if they select the right user types. The account keeps its external identity, so a policy that includes every external user type, including B2B collaboration member users, keeps it in scope. A policy that selects only guest users no longer applies.

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.