Why a Synchronized Azure AD User Appears as a Guest in Microsoft 365
Question details
The user needs to determine why a synchronized Microsoft 365 account appears as Guest in Azure Active Directory and shows multiple sources of authority, and whether the UserType value should be changed.

- Product
- Microsoft Azure Active Directory / Microsoft 365
- Device & OS
- not provided
- Scenario
- An administrator is reviewing Azure AD users after synchronization and finds one synchronized user listed as Guest rather than Member.
- Observed behavior
- The synchronized Azure AD user appears as Guest and displays multiple sources of authority, unlike other synchronized users.
Before making any change, open the Microsoft Entra admin center and compare the user's cloud object with the on-premises Active Directory account. Verify that you have Global Administrator or Hybrid Identity Administrator permissions and know the current Azure AD Connect synchronization configuration.
Verify the user's on-premises account and Azure AD Connect synchronization rules
Use this solution first to confirm whether the Guest designation reflects a real external or partner relationship before you change any directory value.
The Guest UserType may be synchronized from an on-premises partner account. Azure AD Connect can populate UserType based on source attributes, and changing it only to alter the display can cause incorrect access or licensing behavior.
Sign in to the Microsoft Entra admin center, go to Identity > Users > All users, and select the synchronized account that appears as Guest.
Open Active Directory Users and Computers or your local directory tool, locate the matching on-premises user, and inspect the account type, company, and partner or external attributes.
In the Azure AD Connect server, open Synchronization Rules Editor and review the inbound and outbound rules for UserType and sourceAnchor to see why the account is projected as Guest.
If the account genuinely belongs to a partner or external user, keep UserType as Guest. Only consider changing it through Microsoft Graph PowerShell when the person's actual relationship to the organization has changed.

Update UserType with Microsoft Graph PowerShell only after verification
Use this only if you have confirmed that the person's actual relationship to the organization has changed and the Guest value is no longer correct.
Use WPS Office for Daily Document Work While Resolving Azure AD Guest Issues
When Azure AD or Microsoft 365 user administration takes time, WPS Office gives your team a free, lightweight Office alternative for creating and editing documents. It opens and saves Microsoft Word, Excel, and PowerPoint formats with a familiar ribbon UI, so you can continue document work without extra Microsoft 365 licenses and migrate files seamlessly.

Frequently Asked Questions
Why does a synchronized Azure AD user show as Guest instead of Member?
The UserType can be synchronized from the on-premises account when the source object represents a partner or external user. Check Active Directory attributes and Azure AD Connect synchronization rules before changing the value.
Can I change UserType just to make the user appear as Member in the list?
No. Microsoft recommends that UserType reflect the person's actual relationship to the organization. Changing it only to alter the display can create incorrect access, licensing, and collaboration behavior.
Where can I review the synchronization rules for UserType?
Open the Azure AD Connect server, launch Synchronization Rules Editor, and inspect the inbound and outbound attribute flow rules for UserType and sourceAnchor. In the Microsoft Entra admin center you can view the current value under Identity > Users > All users.
What should I check before changing a synchronized guest account?
Compare the cloud object with the on-premises Active Directory account, confirm the user's real relationship to the organization, and verify your Global Administrator or Hybrid Identity Administrator permissions.
Does changing Azure AD UserType affect Office access?
Yes, it can affect guest access, Teams collaboration, SharePoint sharing, and licensing. Only update it after confirming the user's role.




