The Copilot in SharePoint Immersive
A full day in your tenant with your team. We build your site context file, your first three Skills, and the adoption pattern your team will actually use. By Daniel Anderson, Microsoft MVP.
Your team has Copilot licences. Most are not using it.
The features are real. The adoption gap is the actual block. Four patterns I see in every tenant before mid-June.
Tried twice, stopped
Users opened Copilot, asked something generic, got something generic, and never went back. Nobody on the team knows what good prompting looks like for your data.
Admin enabled it, nothing happened
The PowerShell ran clean. The floating button appeared. The team carried on as if nothing changed. There is no plan for what to build first or how to introduce it.
No-one has built a Skill
Skills are the actual lever. The team has not written one because nobody has seen one built end to end in a real tenant with real content.
The rollout lands in mid-June
Mid-June 2026 flips to opt-out. The floating Copilot button appears for every licensed user. If your team is not ready, it lands cold.
A full day. In your tenant. With your team.
Not a training course. Not a deck of slides. A working session where we build real assets together in your real SharePoint tenant with your real content. By the end of the day you have a SharePoint.md context file, three working Skills, and a written adoption playbook your team can actually run with.
I have run this with finance teams, people and culture teams, project management offices, and IT leadership groups since the September 2025 preview opened. The pattern holds across all of them. One day of focused build, your team leaves with assets that pay back in week one.
Delivered on site within Australia, or virtually via Microsoft Teams for distributed teams. Same content, same outcome, same day.
What we work on, hour by hour
Two halves. Morning is foundations. Afternoon is build. Lunch is the questions you never get time to ask.
Three hours laying the foundation, so the afternoon build sticks
The morning draws from The SharePoint Lab, the SharePoint readiness work that Copilot in SharePoint sits on top of. Get the foundations right and every Skill we build in the afternoon performs the way you expect.
- SharePoint readiness for AI. Metadata, content types, library structure, permissions. The foundations work from thesharepointlab.com, applied to your most active site.
- What Copilot in SharePoint actually is. The rename, the three capabilities, the licence and prerequisite story. Done in 30 minutes so we can get into the build.
- Your SharePoint.md context file. We write it together using one of your most active sites. By morning tea your site has a working SHAREPOINT.md in /Agent Assets.
- The Skill anatomy. Walk through a working Skill file. What every section does. Where common Skills go wrong. What to write yourself.
Four hours, three Skills, one adoption playbook
- Your first three Skills. We pick three workflows your team does repeatedly. Contract review, status reports, library audits, board pack prep — whatever earns its place. We build all three in your tenant with your data.
- Quick step buttons. Wire each Skill to a one-click button so anyone on the team can run it.
- The adoption playbook. Three pages, written together, that names who runs which Skill, how they introduce it to colleagues, and what good looks like in the first month.
Concrete assets, not memories of a workshop
- Your SharePoint.md fileWritten together using your site, dropped in /Agent Assets/SHAREPOINT.md before lunch.
- Three working SkillsInstalled in your Agent Assets/Skills/ folder, tested with your content, ready for the team to run on Monday.
- The adoption playbookA 3-page Markdown file naming who runs which Skill, how they introduce it, and the metrics to watch in the first month.
- The session recordingIf delivered virtually via Teams, you keep the recording. Replay any segment, share with team members who could not attend.
- 30 days of follow-up Q&AEmail and Teams chat with me for 30 days after the session. Questions, tweaks, second opinions on Skills your team writes in the weeks after.
Who this is for
The day works best when the prerequisites are honest. Two columns, both true.
- You have Microsoft 365 Copilot licences for the team attending
- A SharePoint admin can opt your tenant or pilot site into the preview before we run
- Your team is willing to build in your real tenant with your real content
- You have a few processes your team does repeatedly that you want to turn into Skills
- You want a working artefact at the end of the day, not slides
- You do not have Copilot licences for the attendees
- You want a passive "watch and learn" session (this is hands-on)
- You need custom Copilot Studio agent development (different shape of work)
- You want a generic Copilot training course not tied to SharePoint
- You expect ongoing managed service after the day (we can talk about that separately)
Daniel Anderson, Microsoft MVP
I have been building on the M365 stack for 20 years and have been in the Copilot in SharePoint preview (then Knowledge Agent, then AI in SharePoint) since September 2025. I write a weekly newsletter for 8,000+ subscribers on practical AI inside Microsoft 365.
I run this immersive because the feature is genuinely useful but adoption fails without a deliberate setup. I have run it with enough teams now to know the pattern. The day is not a sales pitch for Microsoft. It is a practitioner-led build with the assets your team needs to actually use what you have already paid for.
- Practitioner first — I am in client tenants every week, building, breaking, and rewriting
- Independent — Microsoft Partner, not a Microsoft employee, no quota
- Australian-based — Melbourne. On site within Australia, virtual everywhere else
- Honest about scope — Skills are powerful but not everything. I will tell you when the answer is Copilot Studio instead
Daniel Anderson
Microsoft MVP · 20 years on M365Independent. Melbourne-based. 8,000+ newsletter subscribers at danielanderson.io. Building Copilot in SharePoint Skills in client tenants since the September 2025 preview.
Connect on LinkedIn →- Full day on site in Australia, or virtual via Microsoft Teams
- Up to 15 attendees from your organisation
- SharePoint.md context file, three Skills, adoption playbook
- Session recording (if virtual)
- 30 days of follow-up Q&A by email and Teams chat
- Travel included within metro Melbourne; interstate at cost
- NDA signed before delivery as standard
Answers to what teams ask before booking
Is this for individual contributors or for our team?
For your team. The immersive is built around a single organisation, with attendees from that organisation, working in your tenant. Group size is 8 to 15. If you need a single-person training, public Copilot courses are a better fit.
We do not have Copilot licences yet. Can we still book?
Not yet. Microsoft 365 Copilot licences are a prerequisite for AI in SharePoint and therefore for the immersive. Get the licences in place, then book. If you are not sure how many you need or whether the cost is justified, I can advise on that separately before we commit a workshop date.
Can you run this remotely for a distributed team?
Yes. Virtual delivery via Microsoft Teams works for distributed teams. Same content, same hands-on build, same outcome. The session is recorded and stays with you.
What if our team has not used AI in SharePoint at all?
That is the most common starting point. The morning covers the foundations from zero. We assume nothing. By lunch you are building, not learning.
What if we have already built some Skills?
Bring them. We will review the existing Skills together and use the afternoon to extend, refactor, or replace as needed. The session adapts to the maturity of the team in the room.
Do you sign NDAs?
Yes. An NDA is signed before delivery as standard. Tenant access is part of the day; the legal protection matters to both sides.
Can we extend to a two-day version?
Yes, for organisations who want a deeper second-day on Skills writing, governance, or rollout planning. Pricing is pro-rated based on scope. Mention it in your enquiry and we will scope it together.
What happens to the recording if we have sensitive internal data on screen?
You control the recording. If sensitive content is on screen during the build, we either pause the recording, swap to a non-sensitive site for that section, or skip the recording entirely. Your call, agreed before we run.
What happens after the day?
30 days of follow-up Q&A by email and Teams chat. Beyond that, options include a fractional engagement to keep building the Skills library, or a quarterly tune-up day. Discussed only if you want it, no obligation.
Book a date before the mid-June rollout
Dates are limited and the rollout window is short. Send a one-line enquiry with your preferred week and I will come back with availability.
Request a date →Not ready yet? Grab the SharePoint.md template and start with that. The immersive is a step up, not a starting point.