M365 Family personalized email alias fails - domain backend not synced with family plan members

JIHAD MERAASHLI 20 Reputation points
2026-06-21T03:50:12.9833333+00:00

Environment:

  • Microsoft 365 Family (paid, active)
  • Custom domain: meraachli.com (registered via GoDaddy, DNS/MX/SPF correctly pointed to Outlook)
  • My own personalized email ******@meraachli.com works perfectly
  • All family members have valid Outlook.com primary accounts and are correctly added to the M365 Family plan (5/5 slots used)

The problem:

Every family member gets "There was a problem adding your alias" when attempting to set up a personalized email address under my domain through the Outlook Premium flow.

I have identified what I believe is the root cause. In my Outlook Personalized Email settings at:

outlook.live.com/mail/options/premium/features

Under Personalized email address → Members, my domain shows as successfully connected (green tick), but no family members appear — only myself as Domain Administrator. This is despite all 5 members being correctly listed under my M365 Family subscription at account.microsoft.com.

The M365 Family plan and the domain provisioning backend appear to be completely out of sync for my account. Family members cannot provision aliases because the domain backend does not recognise them as eligible.


What I have already ruled out:

  • DNS/MX/SPF misconfiguration (all correct, my own mailbox works)
  • Ghost/pending aliases on family member accounts (checked account.live.com/names/Manage on each — all clean)
  • Account username conflict (tested with a brand new neutral Outlook.com account added to the family plan — same error)
  • GoDaddy-side issue (domain is only registered there, email is fully Microsoft-hosted)

What I am looking for:

Is there a way to manually trigger a sync between the M365 Family plan membership and the domain personalized email provisioning backend? Or does this require backend intervention from Microsoft's side?

I have two open support cases (7102291891 and 7102810309) where Microsoft has acknowledged backend review is needed but frontline support has been unable to route to the correct team after 7 weeks.

Any help from MVPs or Microsoft engineers here would be genuinely appreciated. Happy to provide screenshots or additional details.

Outlook | Web | Outlook.com | Email
0 comments No comments

Answer accepted by question author
EmilyS726 269K Reputation points Independent Advisor
2026-06-21T05:41:32.3566667+00:00

GoDaddy is a reseller for Microsoft’s commercial products. When you got your custom domain from them your account is being seen as a work or school by Microsoft. Microsoft keeps commercial and consumer products separate. You cannot use a commercial account to sign up for family plan. It’s guaranteed to run into issues. .

Microsoft explains it here: https://support.microsoft.com/office/add-or-remove-an-email-alias-in-outlook-com-459b1989-356d-40fa-a689-8f285b13f1f2

image

can you tell me if you can sign into https://account.live.com right now? If so go to Your info -> sign in preferences you want to give you account an outlook.com alias by using add > create new option and remove the custom domain one.

Was this answer helpful?

1 person found this answer helpful.
0 comments No comments

1 additional answer

Sort by: Oldest
  1. JIHAD MERAASHLI 20 Reputation points
    2026-06-21T05:45:05.0466667+00:00

    Hi Emily, thank you for the quick response.

    I don't believe this is a commercial/work account issue. My domain was connected directly through Outlook.com's consumer personalized email flow (not through GoDaddy's Microsoft reseller path), and my account shows all the hallmarks of a standard consumer M365 Family subscription — 1TB OneDrive storage, ******@meraachli.com working correctly as a consumer personalized email, and the domain showing as connected with a green tick under the consumer Outlook Premium settings page at outlook.live.com/mail/options/premium/features.

    The specific issue I'm seeing is that under Personalized email address → Members on that page, my domain shows as successfully connected, but no family members appear there at all — only myself as Domain Administrator. This is despite all 5 family members being correctly listed under my M365 Family subscription at account.microsoft.com.

    I have tested with a brand new neutral Outlook.com account (no meraachli in the username) added to the family plan and the alias provisioning error persists, so it doesn't appear to be an alias conflict issue either.

    My domain setup dates back to around 2016-2017, which predates the November 2023 cutoff for new personalized email connections. I'm wondering whether this could be a backend sync issue specific to grandfathered pre-2023 domain setups, where the domain provisioning system isn't correctly linking to the M365 Family plan membership.

    Happy to share screenshots if that helps. Any further guidance would be appreciated.

    Was this answer helpful?


Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.