Microsoft 365 tenant
Also known as: M365 tenant, Office 365 tenant, Microsoft tenant
A Microsoft 365 tenant is the dedicated instance of Microsoft's cloud services that belongs to one organization.
It contains the company's users, groups, mailboxes, SharePoint sites, Teams, licences, security settings, and domains. Each tenant has a default address ending in onmicrosoft.com, plus any custom domains the business adds. While a tenant is created in minutes, its settings shape the company's security and collaboration for years, and merging or splitting tenants later is complex.
Microsoft 365 tenant, explained at three levels
At home
A tenant is like a private apartment in a huge building. Microsoft owns the building and runs the plumbing, power and security desk, while each company rents its own unit with its own locks. Everything inside, the furniture, the mail and the people with keys, belongs to that company alone, and neighbours can't wander in, even though they share the same building.
At work
A Microsoft 365 tenant is a company's own private section of Microsoft's cloud. It is created when the business signs up, and it holds every user account, mailbox, Teams team, SharePoint site, licence and security setting. Everything the company does in Microsoft 365 happens inside it, so how the tenant is configured decides how well the company's email and files are protected.
At home
A tenant is your organization's own private space inside Microsoft's shared cloud. When a company signs up for Microsoft 365, Microsoft creates a tenant with a unique ID and a default domain ending in onmicrosoft.com. Every user, mailbox, Teams team, SharePoint site and security setting for that company lives inside it, logically separated from other customers. Adding the company's own domain then lets email addresses use the real business name.
At work
A tenant's data location is set at creation based on the country chosen, which for Canadian customers means data at rest in Canadian data centres for core services. Administration is split across portals: the Microsoft 365 admin centre for users and licences, Entra for identity, Exchange for mail, SharePoint and Teams for collaboration, Intune for devices and Defender for security. Settings apply tenant-wide unless scoped to groups.
At home
Free trials, personal sign-ups with a work email, or a well-meaning relative setting up Teams can each create a separate, unmanaged tenant. Small businesses then end up with several, each holding some accounts, files and forgotten admins. Nobody watches the extra ones, which makes them easy targets and confusing when people sign in. In my view, consolidating those into one tenant early avoids confusion and closes security gaps.
At work
Secure the tenant with baseline policies such as Microsoft's security defaults or Conditional Access, keep global administrators to two to four named people plus break-glass accounts, and enable unified audit logging. Review guest access, external sharing and app consent settings, and manage licences against actual users. Document tenant ownership, including the billing account and domain registrar. MSPs should use granular delegated admin privileges with time-limited, least-privilege roles rather than permanent global access.
Real-world examples
At home
Carlos joined a small company and noticed his first email address ended in onmicrosoft.com. IT later switched it to the company's own domain in the same tenant.
At work
Nadia's Toronto MSP onboarded a new client with three accidental Microsoft 365 tenants from old trials. She consolidated everything into one tenant with Canadian data residency.
Common confusions
- A tenant is the same as a domain name. — A tenant can hold several domains. The domain is just an address, while the tenant holds all users, data, and settings.
- Microsoft secures everything in the tenant automatically. — Microsoft secures the cloud platform, but each business must configure its own accounts, sharing, and security settings.
For analysts
In mergers or rebrands, I'd assess tenant implications early. Combining tenants affects email, Teams, files, and licences, and it takes careful planning.
History & origin
Microsoft launched Office 365 in 2011, building on earlier hosted services such as Business Productivity Online Suite. Each subscribing organization received its own tenant in Microsoft's multi-tenant cloud. Office 365 became Microsoft 365 for most plans in 2020. Microsoft opened Canadian data centres in Toronto and Quebec City in 2016, letting Canadian tenants store core data in Canada. As businesses merged and split, 'tenant-to-tenant' migrations became a specialty, and Microsoft added features for multi-tenant organizations in 2023. In my view, setting up a tenant properly on day one saves small businesses enormous pain later.