A Microsoft 365 tenancy (usually called a Microsoft 365 tenant) is your organisation’s dedicated Microsoft cloud environment.
Think of it as a secure digital boundary that contains your organisation’s Microsoft 365 users, identities, devices, applications, settings and data.
In practical terms
For an organisation such as Cumberland Council, the tenant can include:
- Microsoft Entra ID: user accounts, groups, authentication and access controls
- Exchange Online: email, calendars and mailboxes
- Microsoft Teams: teams, channels, chats and meetings
- SharePoint Online: intranet sites, document libraries and organisational content
- OneDrive for Business: users' personal work files
- Microsoft 365 Groups: membership and permissions underpinning services such as Teams
- Microsoft Intune: device and application management, where used
- Microsoft Purview: retention, information protection, eDiscovery and compliance controls
- Security and configuration: Conditional Access, MFA, policies, application registrations and other tenant-wide settings
An easy analogy
Imagine Microsoft 365 as a huge office building operated by Microsoft.
Your tenant is your organisation's secured suite within that building. Microsoft provides the building and infrastructure, but your organisation controls who gets into its suite, what they can access and how its information is managed.
Why this matters for a tenancy migration
A Microsoft 365 tenancy migration isn't simply copying files from one place to another. You're effectively moving people and services from one secured Microsoft 365 environment to another.
For example:
Old tenant → users, mailboxes, Teams, OneDrive, SharePoint, applications and devices → new tenant
Some workloads contain dependencies that can't simply be copied. User identities, permissions, Teams membership, SharePoint links, applications, devices and security policies may all need to be mapped, migrated, recreated or reconfigured in the destination tenant.
That's why discovery work is so important in a tenancy migration: you need to understand what exists in the source tenant, who or what depends on it, and what needs to exist in the destination before you move it.
For your tenancy migration work, a useful distinction is: the tenant is the environment; tenancy migration is the programme of moving the organisation and its Microsoft 365 services from one tenant environment to another.