First determine whether bobschecter.onmicrosoft.com is a removable guest organization or the home tenant that owns the old work account, because the removal and escalation paths differ.
1. Remove the legacy organization if it is attached to Teams Personal
In Teams signed in with the Microsoft 365 Family account:
- Select Settings → Accounts and orgs.
- Find the old
bobschecter.onmicrosoft.com organization.
- If Leave is available, select it.
- In the browser window that opens, find the organization again, select Leave, and confirm.
- Allow several hours for the change, then sign out of Teams and sign back in.
This removes the personal account’s association with that organization; it does not cancel Microsoft 365 Family. ^1^
2. If the tenant is not removable
Open the Microsoft Entra My Account Organizations page using the affected identity and inspect how the tenant is classified:
- Other organizations you collaborate with: Select Leave. If Microsoft says permission is required, the tenant’s administrator or privacy contact must remove the guest account.
- Home organization: There is no self-service Leave option because that tenant owns the organizational account. Only an administrator can remove or manage it. ^2^
If this is an old tenant that you still administer, do not delete or alter the identity until any required tenant data and services have been handled. If you cannot access the tenant as its administrator, this becomes tenant-access recovery rather than Teams troubleshooting.
The injected ******@outlook.com address may be an alias of the personal Microsoft account, but its appearance alone does not establish that. Check the aliases attached to the Microsoft 365 Family account:
- Sign in to Microsoft account → Your info → Edit account info.
- Review the primary alias and every additional email alias.
- If the phantom Outlook.com address appears there, it belongs to the same personal Microsoft account; aliases share that account’s subscriptions, settings, contacts, storage, and password.
- If an obsolete alias should be removed, select Remove next to it. Before doing so, ensure another working address is configured and that removing it will not disrupt sign-in or email use. ^3^
Microsoft personal and organizational identities cannot be merged. If the same address is attached to both, changing the personal account’s primary alias can reduce ambiguous sign-in selection. ^4^
4. Isolate which identity creates the attendee
For one test meeting:
- Open the meeting link in an InPrivate/Incognito browser window.
- Decline opening the desktop app.
- Join without signing in and enter the intended display name.
- Compare the attendee shown to what appears when joining through the signed-in Teams client.
If the phantom address appears only in the signed-in client, the behavior is associated with the selected Teams identity or organization. Joining signed out is also a practical temporary workaround while the account associations are corrected. ^5^
Identity-focused escalation
If the Outlook.com address is not listed as an alias, or it remains after the legacy organization has been removed and the change has propagated, contact Microsoft Support from the affected personal Microsoft account. Describe the issue as:
Microsoft account identity/alias and Teams attendee mapping issue involving a Microsoft 365 Family account and a legacy Microsoft Entra tenant.
Include the meeting timestamp, organizer domain, displayed phantom address, whether it occurs in newly created meetings, and the result of the signed-out InPrivate test. Do not post meeting links, tenant IDs, or unredacted addresses publicly.
References
- Leave a work or school organization in Microsoft Teams for personal use | Microsoft Support
- Leave an organization where you have a guest account
- Change the email address for your Microsoft account
- Email address linked to personal and business account - Microsoft Q&A
- Issues Connecting in Microsoft Teams Due to Account Conflicts - Microsoft Q&A