When a client asks for Claude, we work alongside you
Refer the client to us and we handle the Claude setup and training while you stay their IT provider. Or, if you roll Claude out yourself, we train your staff or your clients' staff to use it. Either way, the tenant and the client relationship stay with you.
We reply to arrange a short call. You don't need to know which plan or setup you want before you get in touch.
Two ways to work with us
Refer the client and we do the Claude side for them. Or keep the rollout yourself and bring us in to train the people who will use it.
- Referral: we choose the plan with the client, set up their Claude organisation and train their people. Your part is one connector approval in their tenant, and we send you exact instructions for it.
- Training for your rollout: you set up Claude Team or Enterprise for a client, or for your own business, and we run hands-on training for the staff on the configuration you support.
What do we do for your client?
On a referral, we handle the Claude side: choosing the plan, setting up the client's Claude organisation, configuring it for their work and training their people.
Your client gets the help they asked for. We work inside Claude and with the client's staff. Tenant administration, devices, security and Microsoft licensing stay with you.
What is your part?
One approval. A Global Administrator grants consent for Claude's Microsoft 365 connector in the client's tenant, and can then restrict it to named users or groups.
- The connector registers as two enterprise applications in Microsoft Entra: M365 MCP Server for Claude and M365 MCP Client for Claude.
- Consent can be granted during the connection flow in Claude, or in the Entra admin centre using Anthropic's admin consent link.
- Setting “Assignment required” on both applications limits access to the users or groups you add, which suits a pilot.
- Permissions are delegated, so each user reaches only what they can already open. Write permissions, such as sending mail, are a separate approval.
- In Claude's organisation settings, the client can stop staff linking work accounts to personal Claude accounts. We set this up with them.
Anthropic's setup article and security guide are the reference. Our step-by-step version is written for the client and their administrator together.
If your client asks about data handling, is it safe to connect Claude to Microsoft 365? sets out what leaves the tenant, where Anthropic processes it and how that compares with Copilot. For the questions IT providers often raise about Claude, and what the documentation says on each, see your IT provider says it can't set up Claude.
Why refer rather than decline?
Your client gets Claude set up properly, and the relationship stays with you. We are a Claude implementation and training practice, so your managed service contract stays with you.
When a client hears that their IT provider can only help with Copilot, they may look for someone else to help with Claude. A referral keeps you involved in the decision, keeps your tenant documentation complete, and saves your team learning a product outside your focus.
Ger Perdisatt, who leads AI at Work, was COO of Microsoft Enterprise Western Europe. He understands how Microsoft-focused providers work and what you need to know before you approve a change in a client's tenant.
How a referral works
Five steps. You are involved in two of them: the introduction and the consent.
You introduce us
A short email introducing us to your client, copying the person who asked about Claude.
Why this step: Your client hears about us from the provider they already trust, and you know exactly who we are talking to.
We scope it with the client
We agree the first group, the tasks and the Claude plan with them.
Why this step: The client buys and owns the Claude licences, so those decisions sit with them. We keep you informed of the outcome.
We send you the consent steps
Written instructions for approving the Microsoft 365 connector and, if wanted, restricting it to the pilot group.
Why this step: You keep control of the tenant. The instructions let you complete the change in your usual change window without needing to research Claude yourself.
We configure Claude and train the group
Everything inside Claude: the connector settings, shared projects and instructions, and hands-on training.
Why this step: This is the part your client asked for help with. It sits outside your managed service, so your team's workload stays as it is.
We tell you what was set up
A short written record of the connector settings and permissions, for your documentation.
Why this step: When the client calls your helpdesk, your engineers can see how Claude was configured.
Rolling Claude out yourself? We train your staff, or your clients' staff
If you have set up Claude Team or Enterprise for a client, we run the training on your configuration. You keep the rollout, the tenant and the client.
Licences and logins are the start. People need practice on their own work to keep using Claude, and hands-on training on drafting, document review or reporting usually sits outside a managed service. We cover the work itself: the Microsoft 365 connector, projects, building and sharing skills, artifacts, and using Claude efficiently, which matters on Enterprise because every request is billed at Anthropic's API rates. Software teams can have a separate Claude Code session.
We can also train your own engineers, so they can answer first-line questions about Claude with confidence. What the sessions cover is set out on Claude training for teams, and Claude Team or Claude Enterprise explains how the two plans differ.
How training for your rollout works
Three steps. You decide who attends and how we are introduced.
You brief us on the rollout
Which Claude plan the client has, who has seats and which connectors you have approved. Then we agree with you who attends, the tasks they practise and how we are introduced.
Why this step: You have done the setup and the client relationship is yours, so the training matches the configuration you support and the client hears one consistent account of who does what.
We train the staff
Hands-on sessions on their own recurring work: the Microsoft 365 connector, projects, skills, artifacts and efficient use, with Claude Code for any developers.
Why this step: People keep using what they practised on real work, and they learn what to check before relying on an answer.
We report back to you
A short note of what was covered, any settings people asked about and any questions for you as the IT provider.
Why this step: Your helpdesk knows what the staff were shown, and setting changes still come through you.
Questions we are often asked
Do you need admin access to the client's tenant?
No. Tenant administration stays with you. Your administrator grants the connector consent, and we work inside the client's Claude organisation.
What permissions does the connector request?
Delegated Microsoft Graph permissions, which Microsoft lists on the consent screen. Claude acts with each user's own access, so SharePoint sharing settings and folder permissions still apply. Write permissions, such as sending mail or Teams messages, are approved separately.
Does it interfere with Copilot or other Microsoft services?
Claude's connector appears as its own enterprise applications in Microsoft Entra, separate from Copilot. Your existing Microsoft 365 configuration stays as it is.
Do Conditional Access and MFA still apply?
Anthropic's security guide says Conditional Access, group-based assignment and MFA policies are supported. It also notes that location and network restrictions are not, which is worth knowing if the client relies on them.
We roll out Claude ourselves. Can you train our clients' staff?
Yes. You keep the rollout, the tenant and the client relationship. We agree with you who attends, what they practise and how we are introduced, and we train them on the setup you have configured. We can also train your own team, so your engineers know Claude well enough to answer first-line questions.
Will you offer the client other IT services?
No. We are a Claude implementation and training practice. Managed IT, devices, security and licensing for Microsoft 365 stay with you.
Sources
Product details checked against Anthropic's documentation on 15 October 2026. Check the current pages before you rely on a detail.
Talk to us about Claude for your clients
Tell us a little about the client, what they asked for and whether you are referring them or rolling Claude out yourself. Your client may find our overview for businesses and ways to start useful.