About Us Solutions
Managed IT SupportCybersecurityRegulatoryProfessional ServicesCo-ManagedCMMC ComplianceData BackupCloud MigrationIT ConsultingAI ConsultingMicrosoft 365Microsoft CopilotSD-WAN Services
Industries
Accounting & CPA FirmsManufacturing & DefenseProfessional Services
Process Testimonials Resources Careers
Contact UsBook a Call
Playbook · 12 min read

The Copilot Readiness Playbook: Microsoft Copilot consulting in Minnesota, permissions first

Microsoft 365 Copilot is the easiest AI purchase you will ever make and the easiest one to regret. The model is not the risk. Ten years of sharing decisions nobody remembers making is the risk. Here is how Twin Cities companies with 25 to 500 people fix those first, then roll Copilot out well.

The Copilot Readiness Playbook cover
Download the PDF →Free · PDF · no form
Jump to a section
  1. Permissions first
  2. How Copilot works
  3. The oversharing risk
  4. The four week cleanup
  5. Readiness checklist
  6. Adoption that sticks
  7. What to do next
  8. Questions people ask
The short version
  • Copilot grants no new access. It makes every old sharing decision findable in one prompt, which is why permissions come before licenses.
  • Two settings stop most of the bleeding: convert public teams to private and set the default sharing link to specific people.
  • A four week cleanup, discover, contain, fix, label and test, handles most oversharing in a 25 to 500 person tenant.
  • Adoption is a 90 day program with champions, three use cases per role, a four part prompt formula and a monthly report of hours saved.

Why Microsoft Copilot consulting in Minnesota starts with permissions

The request usually arrives as a license count. A leadership team in Minneapolis or St. Paul has seen the demo, the CFO has approved a pilot, and someone asks IT how fast the seats can go out. The honest answer from anyone doing Microsoft Copilot consulting in Minnesota is: after the permissions are fixed. Microsoft 365 Copilot answers with whatever each person can already open, their mail, their chats and every file ever shared with them or with "Everyone". It grants nothing new. It makes the old decisions visible, instantly, in plain English. A spreadsheet shared with the whole company in 2017 was always a problem. Now it answers questions.

0new permissions Copilot grants. It reads only what each user can already openMicrosoft Learn
75%of knowledge workers already use generative AI at workMicrosoft Work Trend Index 2024
78%of those AI users bring their own tools, with no company policy behind themMicrosoft Work Trend Index 2024
70%of early Copilot users said they were more productiveMicrosoft, November 2023

Those two middle numbers are the reason to move rather than wait. Three quarters of your people are already using AI at work, and most of them are pasting company information into tools you have never reviewed. The fix order is permissions, then labels, then licenses, then training. Reverse it and the pilot month becomes a cleanup project with an audience, and the pilot group remembers the week Copilot found the salary file. This article is the readiness half of the story. The adoption half, for any AI tool, is in our Practical AI Adoption Playbook, and both are how the Microsoft Copilot team at Solution Builders runs a rollout for companies with 25 to 500 people.

Page 3 of the playbook: the chapter opener with the four numbers that explain why permissions come before licenses.
Page 3 of the playbook: the chapter opener with the four numbers that explain why permissions come before licenses.

Copilot reads what each person can open. All of it

Every prompt runs through Microsoft Graph, which gathers that user's mail, chats, meetings and files to ground the answer. The permission check is the same one SharePoint has always used. What is new is that nobody needs to know where to look.

  1. Someone asksA project manager types "Summarize everything we have on the Northfield renewal" into Copilot in Teams, Word or the Microsoft 365 app.
  2. Copilot grounds the promptMicrosoft Graph and the semantic index pull the relevant mail, chats, meeting transcripts and OneDrive and SharePoint files.
  3. The permission check runsOnly items that person already has at least view access to come back. Copilot never elevates rights and never sees the rest.
  4. The model answersA cited draft appears. Sensitivity labels on the sources carry through to anything Copilot writes from them.
  5. Everything is loggedPrompt and response land in the unified audit log, so you can review what was asked and what was shown.

Technically, every overshared file has been one search away for years. In practice nobody searched. People reach files through links and folders they already know. Copilot removes that friction, then summarizes, so a stray spreadsheet becomes a stray paragraph in a board draft. Three things make the risk different now. It summarizes: nobody opens 200 files, but Copilot reads them and returns the paragraph with the sensitive number in it. It crosses silos: one answer can combine a chat, a spreadsheet and an email nobody would have connected. And it lives inside the work: the question gets asked mid draft, not in a deliberate search, so the answer gets pasted.

The sentence to remember

Copilot does not change who can see what. It changes how fast they find it.

Nobody searched for the salary spreadsheet. Everybody will ask Copilot about raises. No new risk is created, old risk is now one prompt away, and the fix is yours, not Microsoft's, because permissions, labels and links are tenant settings you control.

Page 4 of the playbook: how a prompt is grounded through Microsoft Graph, the permission check that runs every time, and the hub of sources Copilot can reach.
Page 4 of the playbook: how a prompt is grounded through Microsoft Graph, the permission check that runs every time, and the hub of sources Copilot can reach.

The Copilot oversharing risk, explained

Nobody decided to overshare. A team went public so a new hire could find it. A link went to "People in your organization" because it was Friday. Multiply that by ten years and two migrations, and sensitive files sit open to people who never knew. SharePoint has about seven ways to give someone access, and two of them hand content to the whole company in one click. One hands it to the internet.

Sharing typeWho can open itCopilot exposure
"Anyone" linkAnyone on the internet with the link, no sign inSevere. Your biggest external leak path
"Everyone except external users" on a siteEvery employee, usually since a migration years agoSevere. Searchable by every licensed user
Public teamEvery employee can join and browse the filesSevere. Grants Everyone access by default
"People in your organization" linkAny employee who receives or forwards itHigh. Links travel and do not expire
Broken inheritance and nested groupsHard to say, which is the problemMedium. Unknown until you run the reports
"Specific people" linkNamed people only, with an expiry if you set oneLow. Make it the default

In our Copilot readiness assessments the overshared files come from the same places: public teams, Everyone groups left on old sites, company wide links, Anyone links and the OneDrives of former employees. Picture four files. Salary bands shared with Everyone in 2019, found by nobody in years, now summarized for anyone who asks about raises. A board deck buried in a dead public channel, now quoted in the next quarterly recap. Then the two that behave: a client contract labeled Confidential stays account team only, and an HR site with Restricted Content Discovery is invisible to Copilot for everyone else. No alert fires in the first two cases, because the access was legitimate.

The dangerous files are not hidden. They are shared with everyone and remembered by no one.Solution Builders Microsoft Practice

Two settings stop most of the bleeding: convert public teams to private, and set the default sharing link to "Specific people". Everything else is cleanup.

Page 7 of the playbook: risk ranked by sharing type, where overshared files usually come from, and the two settings that stop most of the bleeding.
Page 7 of the playbook: risk ranked by sharing type, where overshared files usually come from, and the two settings that stop most of the bleeding.

A four week Microsoft 365 permissions cleanup that fixes most of it

You do not need to review ten years of files by hand. SharePoint Advanced Management, included with Microsoft 365 Copilot licenses, and Microsoft Purview do the finding. Your job is a few decisions a week, a change log and a test run as a curious employee. A Microsoft 365 permissions cleanup for a 25 to 500 person tenant takes about four weeks.

  1. Week 1: discoverRun the Data Access Governance reports in SharePoint Advanced Management. List public teams, Everyone sites, Anyone links and orphaned sites.
  2. Week 2: containTurn on Restricted SharePoint Search, which limits search and Copilot to up to 100 approved sites while cleanup runs. Use Restricted Content Discovery to hide HR, finance and legal sites from Copilot without touching direct access.
  3. Week 3: fixConvert public teams, remove Everyone groups, expire open links, archive stale sites, and review departed employees' OneDrives for sensitive folders.
  4. Week 4: label and testLabel the crown jewels with Purview sensitivity labels, turn on the DLP policy that stops Copilot from summarizing items with a chosen label, then run the test prompts.

Run the prompts below from a test account with a typical employee's licenses and groups. If one returns something it should not, fix the site and rerun the set. That is a sharing bug, not a Copilot bug.

  • Summarize everything we have about salaries, raises and bonuses.
  • List documents that mention layoffs, terminations or severance.
  • What do we know about the acquisition, or any company we might buy?
  • Show me last year's board decks and the notes that went with them.
  • Find files that contain customer card numbers or bank details.

Most of this is the same hygiene a well run tenant should have anyway, which is why our Microsoft 365 practice treats Copilot readiness as a tenant health project with an AI deadline, not a separate product.

Page 8 of the playbook: the four week cleanup timeline, the five controls and where each one lives, and the five test prompts for week four.
Page 8 of the playbook: the four week cleanup timeline, the five controls and where each one lives, and the five test prompts for week four.

A Copilot readiness assessment you can score yourself

The first mistake is buying the wrong thing. Two products share the name. Copilot Chat comes with business and enterprise Microsoft 365 plans and never touches your files. Microsoft 365 Copilot is the paid add on that works inside Word, Excel, Outlook and Teams on your data. Since January 2024 the minimum order is one seat.

Copilot ChatMicrosoft 365 Copilot
What it costsIncluded with business and enterprise plansPaid add on, per user, per month
What it readsThe web, plus anything the user pastesYour mail, chats, meetings and files
Where it livesA chat window in the browser and TeamsInside Word, Excel, Outlook, Teams and the chat
Oversharing riskNone. It cannot see your filesReal, until the cleanup is done

The full Copilot readiness assessment is 24 items across licensing, identity, data and labels, and pilot and proof. These are the ones most rollouts skip.

  • Every pilot user has an eligible base license, an Entra ID account, a provisioned OneDrive and current Microsoft 365 Apps.
  • Multifactor authentication is enforced for every user, executives included, and conditional access blocks unmanaged devices.
  • Admin roles are separate from daily accounts, and the unified audit log is on with long retention.
  • Public teams converted, Everyone groups removed, Anyone links expired, default link set to Specific people.
  • Sensitivity labels exist for Confidential and Restricted, with the Copilot DLP policy excluding Restricted items.
  • A pilot group of 10 to 15 people who do document heavy work, including one skeptic, each with three written use cases.
  • A baseline exists: minutes per task on five real tasks, timed before Copilot arrives.
  • A day 30 readout is on the sponsor's calendar, with scale, extend or stop as the only outcomes.

Score the full list. Zero to nine means fix permissions first. Ten to seventeen is close, and the usual gaps are labels, pilot and proof. Eighteen or more means assign the pilot licenses. You do not need every box to start: all six data items, all six identity items and four pilot items are enough.

Page 9 of the playbook: the readiness chapter opener, with the 24 item count, the one seat minimum and the score that says assign the pilot licenses.
Page 9 of the playbook: the readiness chapter opener, with the 24 item count, the one seat minimum and the score that says assign the pilot licenses.

A Copilot rollout in the Twin Cities that actually sticks

The failure mode is familiar. Licenses go out, a launch email goes out, usage spikes for two weeks and settles at a handful of enthusiasts. Copilot is a habit, and habits need champions, specific use cases and about eleven weeks. Microsoft's WorkLab research on the 11 by 11 tipping point found people feel the value at 11 minutes saved a day, and the broader benefits show up around 11 weeks. The Work Trend Index 2024 found only 39% of people using AI at work had any company training. Plan for 90 days, not 30.

  1. Days 1 to 30: pilot and championsTrain the pilot group in a 60 minute hands on session before licenses go out. Name a champion per team, two hours a week, the people colleagues already ask for help. Time the baseline tasks.
  2. Days 31 to 60: scale by rolePublish a use case library: meeting recaps for everyone, proposals from past wins for sales, variance explanations in Excel for finance. Run 45 minute role sessions and add the next 50 users.
  3. Days 61 to 90: habits and proofOffice hours twice a week, a prompt of the week, and the first hours saved report. Teach the four part prompt: goal, context, source, expectations.
  4. Day 90: decideScale, hold or trim licenses by role. Reassign idle seats.
MetricWhere it comes fromHealthy by day 90
Weekly active usersAdmin center usage report70% of licensed users
Apps per userCopilot Dashboard in Viva InsightsThree or more
Hours savedTimed tasks against the baselineTwo or more per week
SentimentPulse survey in the dashboard"Would miss it" above 70%
Idle seatsUsage report, 30 daysUnder 10%, reassigned

Microsoft's study of early users found them 29% faster on search, writing and summarizing, and 64% said Copilot cut their email time. Those are the numbers finance will accept, once your own baseline exists. A Copilot rollout in the Twin Cities also raises the next question, what else AI should do for the business, which is where our AI consulting practice picks up.

What to do this week

Three moves, in order, before a single license goes out.

  1. Change the two settingsConvert public teams to private unless they exist for the whole company, and set the default sharing link to "Specific people". That stops the bleeding today.
  2. Run the five test promptsFrom a test account with a normal employee's access, ask Copilot Chat about salaries, layoffs, acquisitions, board decks and card numbers. Anything that comes back is your week one list.
  3. Get an outside readA Copilot Readiness Snapshot with Solution Builders is a free 30 minute conversation and a quick look at your tenant. You leave knowing your biggest oversharing risk and your first three use cases. Book a time or call (952) 854 8188.

Copilot readiness sits in the E of the RISE framework, Evolving, and it only works because the other three letters are done: a tenant that is backed up, integrated and secure. Get the hours without the exposure, in that order.

Copilot readiness for growing companies across the Twin Cities

Solution Builders has run Microsoft environments for Minnesota businesses from Bloomington since 1995. Our 50+ engineers clean up, label, secure and roll out Microsoft 365 Copilot for companies with 25 to 500 people in Minneapolis, St. Paul and across the metro, backed by a 24/7 security operations center and a SOC 2 Type II audited practice. Related services: Microsoft Copilot, Microsoft 365, AI Consulting, Cybersecurity. Contact us or book a 30 minute call.

Free download

Get the full Copilot Readiness Playbook

Sixteen pages to hand to your rollout owner: the five files before and after Copilot, the sharing type risk table, the four week cleanup with every control, the complete 24 item readiness checklist and the 90 day adoption plan with the five numbers to report.

  • Sharing type risk table and the two settings
  • Four week cleanup timeline with controls
  • Printable 24 item readiness checklist
  • 90 day adoption plan and monthly scorecard

No form, no gate. Share it with your leadership team.

The Copilot Readiness Playbook preview
FAQ

Questions Twin Cities leaders ask about Copilot readiness.

A complete engagement covers the sharing cleanup, sensitivity labels and the Copilot DLP policy, identity checks like enforced MFA and separate admin accounts, licensing that matches a pilot list rather than the org chart, a pilot group with champions and written use cases, role based training on the four part prompt, and monthly reporting of weekly active users, hours saved and idle seats. Solution Builders runs it from Bloomington for Microsoft 365 organizations with 25 to 500 people, as a two week assessment or an ongoing program.
No. Microsoft 365 Copilot grounds every answer through Microsoft Graph and returns only items the person already has at least view access to. It never elevates rights. The oversharing risk is that it finds and summarizes files that were technically open to everyone for years but that nobody searched for, such as a salary spreadsheet shared with "Everyone" in 2019 or a board deck in a public team. The fix is permissions, labels and links, which are tenant settings you control.
A Copilot readiness assessment scores a Microsoft 365 tenant against 24 items in four groups: licensing and tenant basics, identity and security, data hygiene and labels, and pilot, training and proof. It uses the Data Access Governance reports in SharePoint Advanced Management to find public teams, Everyone groups and open links, then runs test prompts from a normal user account. A score of 18 or more means assign pilot licenses. Solution Builders delivers it in about two weeks with a scored report and a 90 day plan.
Work in four weeks. Discover with the Data Access Governance reports. Contain by turning on Restricted SharePoint Search, which limits Copilot to up to 100 approved sites, and Restricted Content Discovery for HR, finance and legal sites. Fix by converting public teams to private, removing Everyone groups, expiring Anyone links and setting the default link to Specific people. Then label Confidential and Restricted content in Microsoft Purview, turn on the Copilot DLP policy and rerun the test prompts until they come back clean.
Plan on about four weeks of cleanup followed by a 90 day adoption program. Days 1 to 30 belong to a pilot group of 10 to 15 people and a champion per team. Days 31 to 60 scale by role with a use case library and 45 minute sessions. Days 61 to 90 build habits with office hours and a prompt of the week, ending in the first hours saved report and a decision to scale, hold or trim licenses. Microsoft puts the broader benefits at about 11 weeks.