User showing as Unknown User in Teams

Fixing “Unknown User” in Teams After Account Reactivation

The user mailbox converted to a shared mailbox when he left the organization. It appears that after reactivating a disabled account, we need to manually convert it to a regular mailbox, as this process isn’t automatic.

When a reactivated user appears as “Unknown User” in Microsoft Teams, try these solutions:

Common Causes & Solutions

1. Teams License Not Assigned

Solution:

1. Open Microsoft 365 Admin Center → Users → Active Users
2. Select the affected user
3. Under Licenses and Apps, assign a Teams-enabled license (e.g., Microsoft 365 E3/E5)
4. Save changes and wait 15-30 minutes

2. Azure AD Sync Delay

Solution: Force Azure AD sync

Start-ADSyncSyncCycle -PolicyType Delta

Wait 15 minutes after running this PowerShell command on your Azure Connect server.

3. Cached Data in Teams

Client solution:

1. Close Teams completely
2. Delete cache folder:
   • Windows: %appdata%\Microsoft\Teams
   • macOS: ~/Library/Application Support/Microsoft/Teams
3. Restart Teams

Admin solution (PowerShell):

Connect-MicrosoftTeams
Remove-CsUser -Identity "user@domain.com" -Confirm:$false
Grant-CsTeamsLicensing -Identity "user@domain.com"

4. Missing SIP Address

Solution:

1. Check Azure AD → Users → User profile
2. Verify these fields are populated:
   • UserPrincipalName
   • Mail
   • SIP Proxy Address (should look like: sip:user@domain.com)
3. If missing, add SIP address via Exchange Admin Center → Recipients → Edit user → Email Addresses

5. Backend Service Delay

Solution: Wait 4-6 hours. If still unresolved:

1. Check Service Health in M365 Admin Center
2. File support ticket via Microsoft 365 Admin Center

Prevention Tips

• Always reapply licenses after reactivating accounts
• Regularly verify Azure AD sync status with: Get-ADSyncConnectorRunStatus
• Audit SIP addresses during account reactivation

Advanced Troubleshooting

1. Run Teams Connectivity Test: https://aka.ms/TeamsTest
2. In Teams client, type: /diag then run user-specific tests
3. Check hybrid configuration sync status if using on-prem AD