Others

How to Convert an Azure AD B2B Guest User to an Internal Member

Adam Davis Oct 10, 2026 869 views

Question details

IT administrators encounter synchronization, sign-in, and Teams access issues when attempting to change a Microsoft Entra (Azure AD) guest account into an internal member.

How to Convert an Azure AD B2B Guest User to an Internal Member

Product: Azure Active Directory (Microsoft Entra)
Device & OS: not provided
Scenario: Modifying an external guest user profile's UserType and related identity properties to convert them into a fully internal member account.
Observed behavior: The conversion results in inconsistent sign-in behavior, broken identity synchronization, and an inability to add the converted user to Microsoft Teams shared channels.

Before you start

Before modifying identity properties, ensure you have the necessary Global Administrator or Privileged Role Administrator rights and back up the current state of the user's attributes.

Solution 1Recommended

Review Sync Errors and Refresh Teams Memberships

Check for conflicting identity attributes and refresh the user's session and permissions in Microsoft Teams to resolve access issues.

Because direct changes to user properties may not preserve all backend account relationships, manually clearing out old identity tokens and refreshing group memberships is often required.

Check Identity Attributes

Log in to the Microsoft Entra admin center and review the converted user's profile for synchronization errors, ensuring the mail nickname and email addresses are consistent.

Verify Shared-Channel Permissions

Confirm that the newly converted internal member has the appropriate organizational permissions required for shared channel access.

Re-add the User to Teams

Remove the user from the affected Microsoft Teams groups and channels, wait for the directory to sync, and then re-add them to refresh their access token.

Review Sync Errors and Refresh Teams Memberships

Synchronization Delay: Changes to Azure AD user types can take up to 24 hours to fully propagate across all Microsoft 365 services, including Microsoft Teams.

Solution 2

Troubleshoot Using PowerShell or Microsoft Graph

Use advanced administrative tools to manage properties when standard admin center modifications produce inconsistent results.

Solution 3

Escalate Complex Conversions to Support

Contact Microsoft Support if identity relationships remain broken and synchronization errors persist after manually updating attributes.

Free Microsoft Office alternative

Looking for a Lightweight Alternative to Complex Office Suites?

Managing enterprise identities like Azure AD B2B can be highly complex and time-consuming. If your team simply needs a reliable, free, and easy-to-use office suite for document creation without the overhead of enterprise identity management, WPS Office is an excellent choice.

1. Visit WPS Office: Go to the official WPS website to download the free installation package.
2. Install the Software: Run the lightweight installer on your PC, Mac, or mobile device.
3. Open Your Files: Instantly open, edit, and share your existing Microsoft Office documents without complex account setups.

Highly compatible with Microsoft Office formats (Word, Excel, PowerPoint).Free and lightweight, avoiding complex enterprise IT management overhead.Familiar user interface requiring zero learning curve for new team members.Built-in seamless document sharing and local collaboration features.

microsoft office alternative - wps office

Frequently Asked Questions

Why can't I add a converted internal member to a Teams shared channel?

When a guest account is converted to an internal member, the backend identity relationships often break or experience sync delays. Removing and re-adding the user to the team usually refreshes the permissions.

Can I change an Azure AD guest to a member using PowerShell?

Yes, you can change the UserType property from Guest to Member using PowerShell or Microsoft Graph. However, simply modifying the property may not automatically preserve all previous access rights, leading to inconsistent sign-in behaviors.

How long does it take for UserType changes to reflect in Microsoft Teams?

Changes to identity properties in Azure AD (Microsoft Entra) can take up to 24 hours to fully synchronize with Microsoft Teams and other Microsoft 365 services.

Office Quick Solutions