@Sympatico.ca email - Cannot change Primary Username

Question

I have a Microsoft account that uses an old Sympatico.ca email as the primary username. When I try to change the primary username, I see the message: “Your organization’s policies prevent you from changing your primary username.” I am not part of any organization. This happens because Sympatico.ca accounts were historically placed in a legacy Microsoft‑managed tenant when Bell/Sympatico email was hosted by Microsoft, and my account is still stuck there.

When I contacted support previously, the case was escalated to a supervisor who advised me to contact Bell. Bell cannot assist because they do not administer this legacy Microsoft tenant. I was advised by CoPilot A! that the Identity Management/Identity Engineering team must perform a tenant release, but after several attempts my ticket was closed before that could happen. I have not been able to get the issue escalated to the correct team after another attempt.

How can I get my previous ticket reopened and escalated to the appropriate team so the required tenant release can be completed?

Answer 1

As an FYI, AI, including Copilot, is known to hallucinate.

Tenant release happens all the time - for business tenents, because either someone created a Microsoft 365 business tenant then then sold or let the domain expire and the new owner wants to use Microsoft 365. Occasionally someone in a company created a tenant and left the company but did not give anyone admin rights.

In order to transfer, they need to prove they have control over the domain. That will not work for you - but someone at Bell could have Microsoft do it to release all Sympatico addresses. (That would make a lot of people happy.)

If you don't have purchases on the account (other than subscriptions) or are not using it for gaming, you could make a new account - moving OneDrive is fairly easy. Purchases and games cannot be moved.

Answer 2

Sympatico.ca addresses are a legacy domain that were historically managed by Bell through Microsoft’s hosted email platform.

That is correct. I don't recall the dates they used outlook.com, but a few ISPs moved mail to outlook.com sometime around 2010 - 2013 period. I think don't think any stayed more than a few years.

I've asked Microsoft about "fixing" this problem (you are not the first person who wanted to change their primary from one of the ISP domains), they told me they cannot remove addresses from the tenant. If you use web mail, you can send mail from an alias, but not in the Outlook or 3rd party apps.

Microsoft Support has handled this exact issue for other Sympatico users by performing a tenant release (also called a domain de‑association) on Microsoft’s side.

Did AI tell you this? If you have links where people said they were able to do this, I will give them to my contacts and ask about it.

Answer 3

When the account was created by a 3rd party, then primary address cannot be change. You can add aliases but not change the default. Sorry.

The Copilot information is for business accounts, not consumers. Bell would need to contact them and have the domain removed. However, people still using the accounts to receive mail sent to Sympatico addresses would no longer receive mail if the domain is removed.

Answer 4

I contacted support again and the agent closed the chat without resolution.

Answer 5

Reopening and escalating a closed support ticket is not possible directly; a new support request must be submitted and clearly framed so it is routed to the correct team.

For this scenario, the only supported path is to open a fresh account/identity support case with Microsoft and provide complete tenant‑identity details so it can be escalated to the internal identity/tenant team. To maximize the chance of correct routing and faster resolution:

1. Collect and document all relevant information
   • The Sympatico.ca primary sign‑in address.
   • Confirmation that this is a personal Microsoft account, not a work/school account.
   • Exact error text: “Your organization’s policies prevent you from changing your primary username.”
   • A short explanation that Sympatico.ca mailboxes were historically hosted in a Microsoft‑managed tenant and that this account is still bound to that legacy tenant, preventing primary alias changes.
   • Any previous support case numbers that were closed.
2. Submit a new support request through the Microsoft account help channel
   • Go to the general Microsoft account help entry point and start from there: Account & Billing Help.
   • When prompted for the problem description, explicitly state that this is a Microsoft account sign‑in/alias problem caused by the account being stuck in a legacy Microsoft‑managed tenant and that a “tenant release” is required.
   • Include the previous case IDs in the description and state that the earlier cases were closed before the tenant release could be executed.
3. Clearly request escalation in the case description
   • In the problem text, include wording such as:
     • “This is a personal Microsoft account with a Sympatico.ca sign‑in address that resides in a legacy Microsoft‑managed tenant. Changing the primary alias fails with ‘Your organization’s policies prevent you from changing your primary username.’ This requires internal escalation to the identity/tenant engineering team for a tenant release. Please escalate accordingly and do not route me back to Bell, as Bell does not administer this legacy tenant.”
   • Re‑emphasize that Bell/Sympatico is no longer the tenant administrator and cannot change policies or release the account.
4. Respond quickly to any verification or follow‑up
   • If support requests additional verification or clarification, respond promptly and restate that the goal is a tenant release so that the primary alias can be changed like a normal personal Microsoft account.
5. If the new case is misrouted or closed again
   • Use the same support entry point to open another case, referencing both the original and the most recent case numbers.
   • In the new description, explicitly note that previous cases were incorrectly routed (for example, to the ISP) and that this must be handled as a Microsoft‑managed legacy tenant identity issue.

There is no self‑service way to perform a tenant release; only Microsoft internal support/engineering can do it. The practical way to get this done is to:

• Always start from the Microsoft account support channel (not the ISP).
• Provide complete identity details and prior case IDs.
• Explicitly request escalation to the internal identity/tenant team for a tenant release in the case description.

---

References:

• Outlook.com email account appears as "outlook_[long series of letters and numbers]@outlook.com" in Outlook for Windows
• Fixes or workarounds for recent issues on Outlook.com
• How to fix "This username has been turned off" error
• Tenant access recovery
• Mailbox not provisioned in Azure AD Connect for Office 365
• Outlook.com email account appears as "outlook_[long series of letters and numbers]@outlook.com" in Outlook for Windows [WORKAROUND]
• How to add an existing outlook.com account to my existing microsoft account? - Microsoft Q&A
• MSN email issues - Microsoft Q&A