← All articles
Your Microsoft account manager has suggested upgrading to Copilot Premium or Agent 365. The demo looked impressive. But there's a question that rarely gets asked in the upgrade conversation: is your tenant actually ready for this?
Copilot and autonomous agents operate as the signed-in user. They can read files, send emails, create calendar events, and take actions across your tenant — automatically, at scale, based on what they're configured to do. The governance controls adequate for a standard Microsoft 365 deployment may not be adequate for one where AI agents are acting on behalf of your users.
Hard blockers — fix these before any Copilot Premium upgrade
DLP policies must cover Copilot interactions
Without DLP policies extended to cover Copilot, sensitive data that would normally be restricted can be retrieved and summarised by Copilot and shared in the response. This is not a Copilot failure — it's a governance gap that Copilot exposes.
Sensitivity labels must be published and applied
Copilot uses sensitivity labels to understand what content it can reference and share. Without labels, Copilot has no mechanism to restrict what it surfaces. A document labelled Highly Confidential should not be summarised in a response to a general query — but without labels, Copilot cannot make that distinction.
Conditional Access must be enforced
Copilot and agents operate under the user's identity. If a user's identity is compromised, an attacker with access to that account can use Copilot to query your organisation's data at scale. Conditional Access with MFA as a hard requirement is the primary control against compromised identity access to Copilot capabilities.
MFA must be enforced for all users
An agent acting as a user without MFA is an agent whose identity can be stolen with a password alone. The risk profile of a compromised account is dramatically higher when that account has access to AI capabilities that can act autonomously.
Important — address before deploying agents at scale
Purview audit logging must be active
When something goes wrong, you need an audit trail. Purview audit logging records Copilot interactions: who queried what, which data was accessed, what was generated. Without this, you have no visibility into what your AI deployment is actually doing.
SharePoint external sharing must be controlled
Copilot can surface SharePoint content in its responses. If external sharing is unrestricted, the boundary between internal and external accessible content is blurred — and Copilot's content retrieval operates within that blurred boundary.
Insider Risk Management for Agent 365 and E7
Insider Risk Management can apply adaptive protection to users showing risky behaviour. When agents operate as users, the ability to detect anomalous access patterns becomes more important. An agent operating as a user already exhibiting risky behaviour is a compound risk.
The upgrade conversation is commercial, not technical. Microsoft's upgrade path won't tell you whether your governance is ready — it won't. Fix the hard blockers first. The sequence matters: deploying Copilot on top of ungoverned data and unprotected identities makes the existing governance gaps more consequential.
See your Copilot upgrade readiness
M365Clarity checks every governance prerequisite for your next Copilot tier and shows exactly what needs to be in place — including which are hard blockers.
Run a free scan →