Claude is the AI your staff are probably already asking for – or already using on personal accounts. This page covers what the business plans actually give you, what they cost in Australia, and how to deploy Claude inside the guardrails of the Microsoft 365 you already run: SSO, domain capture, conditional access, and honest answers about data.
The single biggest risk isn't Claude – it's staff using AI on personal accounts you can't see, configure or audit. Claude's commercial plans exist to fix exactly that, and on them your business data is not used to train Anthropic's models by default.
Seats under your business, central billing and admin, Claude's add-ins for Excel, PowerPoint and Word, and connectors into your workplace tools. Everyone works under the company account instead of a scatter of personal ones.
~US$25–30 /seat/month (≈A$38–45) · 5-seat minimum
Everything in Team plus the governance layer: audit logs of user actions and data access, SCIM provisioning from your identity provider, custom data retention controls and a compliance API. If you answer to APRA, AHPRA, legal privilege or a board, this is usually your tier.
By quote from Anthropic · we scope which tier fits in the assessment
PLAN DETAILS AND PRICES AS AT AUGUST 2026 · THEY MOVE · WE CONFIRM CURRENT TERMS DURING THE ASSESSMENT
Copilot inherits your tenant's permissions natively – that's its home advantage. A third-party tool like Claude doesn't, and pretending otherwise is how data walks out the door. The honest fix is a set of controls around the tool, all of them things your Microsoft 365 environment can enforce. None of them are on by default.
Staff sign in to Claude with their work identity, and accounts created under your domain belong to the business. Personal-account use for work stops being invisible and starts being preventable.
The approved tool is reachable from managed, compliant devices under the conditions you set – the same Entra conditional access discipline we apply to every other business app.
Sensitivity labels and DLP govern your documents inside Microsoft 365 – they don't reach inside a third-party AI chat. So the data rules live in policy, training and what the tool can connect to. We say plainly what each control does and doesn't cover.
Enterprise audit logs show who did what in Claude; tenant sign-in and network telemetry show what other AI is still being used around it. What you can see, you can manage.
Evisent uses Claude in production daily: staff seats under our domain with single sign-on, scoped read-only connections into our own business systems, and guardrails on what it can touch. The largest build we've published runs Claude inside a client's own Microsoft 365 tenant, drafting a monthly report that used to take a senior project manager 3 hours in about 30 minutes.
That matters for a simple reason: the advice on this page isn't a reseller's brochure. We're vendor-neutral, we take no commissions on licences, and if Copilot – or no AI at all – fits your business better, that's what the assessment will say. Our Copilot vs Claude comparison is written the same way.
The AI-Ready 365 assessment maps your shadow AI exposure, the controls you need, the right Claude tier and the licence maths – then quotes the rollout at a fixed price.