Microsoft Copilot
Glossary
Microsoft 365 tenant
A Microsoft 365 tenant is the dedicated, isolated instance of Microsoft cloud services that an organization gets when it subscribes to Microsoft 365, and the top-level boundary for its identities, data and configuration.
Also known as: M365 tenant, Microsoft cloud tenant, Office 365 tenant
What a tenant contains
Every user, group, Team, SharePoint site, OneDrive, mailbox, Power Platform environment and policy belongs to exactly one tenant. The tenant has its own Microsoft Entra ID directory, its own domain names and its own admin roles. Nothing inside it can see across the boundary unless someone configures external sharing, guest access or cross-tenant access.
Many large organizations run more than one tenant, after an acquisition or to separate regions or business units. Each one is governed separately, so a policy set in one tenant does nothing in the next.
Why the tenant is the unit of governance
Security baselines, compliance controls, sharing settings and lifecycle policies are set and measured per tenant. That is why administrators reason about risk one tenant at a time, and why the first governance question is always the same: what exists in this tenant, who owns it, and who can reach it.
The question has grown with AI. Microsoft 365 Copilot and the agents built in Copilot Studio work inside the tenant boundary and with the permissions it holds, so a tenant that is overshared or full of ownerless workspaces is a tenant whose AI can surface more than it should.
Where Rencore fits
Rencore connects to your tenant through Microsoft Graph and builds one inventory of what it contains: Teams, SharePoint sites, OneDrive, Microsoft 365 groups, users and guests, Entra ID applications, Copilot and Copilot Studio agents, and Power Platform resources. Policies then check that inventory continuously for missing owners, inactive workspaces and broad sharing, and automations fix what they find.
