How to Fix Azure AD Error: Invited User Already Exists
Question details
The user is unable to invite a new user to Azure Active Directory because the system reports the user already exists, despite the user not being visible in the directory.
- Product
- Azure Active Directory
- Device & OS
- not provided
- Scenario
- Inviting a new guest or user into a hybrid Azure Active Directory environment.
- Observed behavior
- Azure AD throws an error stating 'Invited User Already Exists as an Object ID', preventing the invitation from being successfully sent.
Ensure you have administrative privileges for your on-premises Active Directory and access to the Azure AD Connect synchronization server.
Remove Duplicate Secondary Email Addresses in On-Premises AD
Identify and remove duplicate email addresses from on-premises domain controllers to prevent synchronization conflicts in Azure AD.
In a hybrid Active Directory environment, this error is typically caused by another on-premises user account holding the invitee's email address as a secondary email or proxy address. Clearing this duplicate resolves the conflict.
Log in to your on-premises domain controller with administrator credentials and open Active Directory Users and Computers (ADUC). Search the directory for the email address you are trying to invite.
Open the properties of the conflicting user account. Navigate to the Attribute Editor or email properties and remove the duplicate secondary email address (or proxyAddress) from the incorrect user.
Open Azure AD Connect or the Synchronization Service Manager on your sync server. Force a Delta synchronization to push the changes to the cloud immediately.
Wait for the synchronization cycle to complete, then log back into the Azure portal and attempt to send the Azure AD guest invitation again.
Resolve Duplicate Mailbox Objects in Hybrid Exchange
Clear duplicate Exchange GUIDs or mailbox objects that might be causing directory synchronization errors.
Switch to WPS Office for a Hassle-Free Experience
Managing Microsoft accounts, Azure AD syncs, and backend IT issues can be time-consuming. If your team needs a highly compatible, easy-to-deploy office suite without the heavy administrative burden of enterprise cloud management, WPS Office is the perfect alternative.
- 1. Download the installer: Visit the official WPS Office website and click the Free Download button.
- 2. Install the suite: Run the downloaded setup file and follow the on-screen instructions to install the application.
- 3. Start working instantly: Open WPS Writer, Spreadsheet, or Presentation and start editing your existing Microsoft Office files immediately.
Frequently Asked Questions
Why does Azure AD say a user exists when they are not in the directory?
This usually happens in hybrid environments where an on-premises Active Directory user shares a secondary email address or proxy address with the user you are trying to invite. This backend conflict prevents the object from being properly created.
How do I force an Azure AD Connect synchronization?
You can force a sync by opening PowerShell as an administrator on your Azure AD Connect server and running the command `Start-ADSyncSyncCycle -PolicyType Delta`. This pushes recent on-premises changes to Azure AD.
Can I invite a guest user if their email is used as an alias by another employee?
No, Azure AD requires unique email addresses and proxy addresses across the entire tenant. You must remove the email alias from the existing employee's on-premises account and sync the changes before inviting the new user.
