Microsoft 365 Domain Setup in Tooting | PC Macgicians

A custom domain cannot simply be added to a new Microsoft 365 tenant while it is still attached to another one. The safe starting point is to identify the tenant that owns it, recover the appropriate administrator access and map every place where the domain is used. We help Tooting customers establish that position before any subscription, identity, DNS or mail-routing change is attempted.

Find the current tenant and administrator

We record the domain, registrar and DNS host, then establish which Microsoft 365 tenant currently recognises the domain. The required access is an authorised administrator account for that organisation, not a shared user’s password. If ownership or administrator access is disputed, the next step must follow Microsoft’s supported recovery or support process before configuration work continues.

Inventory every domain dependency

Users, administrator sign-ins, aliases, contacts, shared and resource mailboxes, distribution lists, Microsoft 365 groups and Teams-connected groups can all refer to the domain. We inventory those references and their owners before deciding what must move. This avoids treating a domain-release message as a DNS-only fault when active identities still depend on it.

Plan mail flow and DNS

The current MX records and other mail-related DNS entries are recorded alongside the intended destination. Changing a domain in Microsoft 365 and changing public mail routing are separate controlled actions. The sequence depends on where mail is hosted, which addresses must continue receiving and who can approve the change; uninterrupted mail is not promised before that scope is known.

Move or remove dependencies carefully

Microsoft requires the old domain to stop being the default and to be removed from affected accounts and groups before it can be released. Replacement sign-ins and addresses are agreed first, including an administrator on another domain where required. We verify access and mail flow at each agreed stage rather than deleting identities or repeatedly changing DNS to clear an error.

Support near Tooting

Tooting SW17 is served from Putney, approximately 18-25 minutes away according to the repository service data. Tenant, admin-centre and DNS checks can normally begin remotely with an authorised contact. An onsite visit or Putney workshop appointment is useful when local Outlook profiles, archived mail or several approved devices must be checked as part of the change.

Evidence and related support

Current Microsoft domain-removal guidance lists the users, mailboxes, contacts, groups, teams, aliases and administrator sign-ins that can block removal. No completed Tooting tenant transfer is claimed here. For send-and-receive faults on an existing account, compare email setup in Tooting; broader moves are covered by cloud migration in Tooting. The main Microsoft 365 service and Tooting coverage explain the other support routes.

Based in Putney (SW15), supporting Tooting — 18–25 minutes away.