Summary

  • 2 minutes

Relecloud's new AI consulting division needed a Microsoft 365 tenant whose identity—domain, branding, and defaults—matched the relecloud-ai.com brand before the first new hire ever signs in. This module sets up exactly that: a verified custom domain, consistent branding across two distinct portals, and tenant-wide defaults configured deliberately instead of left at whatever Microsoft shipped, with the least-privileged administrator role assigned to every task along the way.

What you learned

  • A Microsoft 365 tenant is a dedicated, isolated instance of Microsoft Entra ID plus the Microsoft 365 services layered on it, automatically provisioned when an organization signs up for a subscription.
  • Assigning the least-privileged role, such as Domain Name Administrator instead of Global Administrator, limits standing access to only what a task requires.
  • Adding and verifying a custom domain uses Domain Connect automatically when a registrar supports it, or manual TXT and DNS record verification when it doesn't—and a domain can only later be removed once it's no longer the default domain and has no references.
  • Branding requirements route to one of two portals: the Microsoft 365 admin center organization theme for the signed-in navigation experience, or Microsoft Entra company branding for the sign-in screen—and the organization theme remains a documented exception that still requires Global Administrator.
  • Org settings routes tenant-wide defaults across three tabs—Security & privacy, Organization profile, and Services—covering everything from password expiration and pronoun availability to company and contact information, data location, release and notification preferences, and per-workload defaults like Calendar external sharing, with some areas, such as People settings, offering their own delegated administrator role.

Learn more