Microsoft Copilot at the Dealership: What to Lock Down Before You Turn It On

Microsoft 365 Copilot security comes down to permissions, because Copilot can show each employee anything that employee can already open in SharePoint, OneDrive, Teams, and Outlook, including pay plans and deal files. Lock that access down before you turn it on.

Last updated: October 15, 2026

The request usually shows up as one line in an email. “Can you get us Copilot licenses?”

We can. We have, when a dealer asked for them. Then we ask a question back, and it tends to slow the room down a little. Who in your store can open the payroll folder right now? Not who should. Who can.

Most dealers don’t know. That’s not a knock on anybody. I spent years on the sales floor and selling CRM to dealers before I came to Helion Technologies, and I can tell you nobody in a dealership ever woke up excited to audit SharePoint permissions. Folders get shared so a deal can close on a Saturday. Accounts get copied so a new hire can start Monday. It all works, so nobody looks at it again.

Copilot looks at it. Every time someone types a question.

So here’s where we stand on Copilot, what it actually does with your data, and the list we’d work through before a single license goes live. If you want the wider view of how we run AI for stores, our managed AI services for dealerships page covers it.

Should Your Dealership Even Use Copilot?

I’ll give you our honest answer first, because you’d find out anyway. Erik Nachbahr, who founded Helion Technologies, puts it in two sentences. “Should they even be using Microsoft Copilot? No. Can you use it? Yes.”

That’s the position. We don’t recommend it as a dealership’s first AI tool. Our preference is a governed AI platform that a store picks on purpose, through a small governance board, with single sign-on and the training switch turned off. I made the longer case for that in our post on AI governance for dealerships.

But plenty of stores already pay for Microsoft 365, the Copilot button is sitting right there in Outlook and Excel, and somebody in the building, usually the person who just watched a demo, wants to press it. If that’s you, we’d rather you turn it on well than turn it on fast.

Can you use it? Yes. Just not before the cleanup.

What Microsoft 365 Copilot Security Actually Depends On

Microsoft 365 Copilot is an assistant built into Word, Excel, Outlook, and Teams that answers questions using your company’s own email, files, chats, and meetings. Microsoft states that Copilot “only surfaces organizational data to which individual users have at least view permissions.” It inherits each user’s access. It doesn’t add any.

Microsoft also says prompts, responses, and the data Copilot pulls through Microsoft Graph “aren’t used to train foundation LLMs.” Both points are in Microsoft’s own data, privacy, and security documentation for Copilot, and they’re the two things a dealer principal usually asks about first.

Read the first one again, though. Copilot shows people what they can already open. In a lot of stores, that’s the problem, not the protection.

Before Copilot, a salesperson who technically had access to the accounting team’s site would never find the commission spreadsheet, because he’d have to know it existed, know where it lived, and go digging through folders he had no reason to open. Now he can ask. The permission was always there. Copilot just made it searchable in plain English.

Erik’s version of the point our security team keeps making is short. AI is “gonna see and give access to whatever data it gets access to.” Copilot is no exception.

Where Dealership Permissions Go Sideways

Dealerships start behind on this, and it isn’t because anyone was careless. A store runs on speed. Deals move between sales, F&I, the office, and the lender in a day, and the fastest way to get a file from one person to the next is usually to share it wider than it needs to be.

“In dealerships where their networks are less secure, and they tend to have issues with people having permissions to things they shouldn’t already,” Erik said, “when you add AI, now you’re spreading that even further.”

Here’s what that looks like inside Microsoft 365. None of these are exotic.

That last row deserves a minute. Erik described it on a DealersEdge webinar in October, and most stores will recognize it. “Accounts getting copied, somebody had one kind of permission, somebody got copied, now that person has the permission and now somebody has elevated access.” A porter cloned from a former office manager is a porter who can ask Copilot about the office manager’s files.

Then there’s admin access, which is a bigger version of the same problem. Copilot itself runs as the signed-in user, but agents, connectors, and add-on AI tools that plug into Microsoft 365 can carry their own access, and some get set up with far more than they need. “Oftentimes AI is connected in with some high level administrative access,” Erik said. “So all of that role-based security you have in place to control what types of things people are able to access, now they can access everything.” On that same webinar he told the story of a dealership IT person who asked for admin rights “to do this AI thing” and was about to launch a tool with network-wide administrative access. Erik’s reaction was the right one. “Whoa, what are you doing exactly?”

Copilot doesn’t create the mess. It reads it out loud.

The Lock-Down List, in the Order We’d Work It

Microsoft publishes its own guidance for a secure and governed Copilot foundation, built in three steps: remediate oversharing, set up guardrails, meet regulations. It’s good. It’s also written for an enterprise IT department, so here’s the dealership translation, roughly in the order we’d do it.

1. Name the people, not the department. Decide who gets a license and why. A short list of named people, approved by whoever owns AI decisions at the store, beats “all managers.” If you don’t have that person or group yet, start there. Our dealership AI use policy template gives you the written rules to hang it on.
2. Clean up the accounts. Turn off everyone who’s gone. Stop copying accounts for new hires and build them from a role instead. Pull admin rights off everyday logins, give the people who need admin a separate account for it, and require multifactor sign-in on every account Copilot will touch.
3. Run Microsoft’s oversharing reports. SharePoint Advanced Management comes with Copilot licenses, and its Content Management Assessment flags sites with oversized audiences, “Everyone except external users” access, broken permission inheritance, and no owner. Microsoft Purview’s data risk assessments find overshared sites that hold sensitive data. Run both before anyone types a prompt.
4. While you fix the worst sites, hide them. Restricted Content Discovery keeps a SharePoint site out of Copilot’s reach without changing anyone’s access to it. Accounting, HR, and F&I are the usual first three. It’s a bandage, and Microsoft treats it as one.
5. Fix the actual access. Site access reviews put each site’s owner in charge of who’s in it, down to the file. Remove company-wide sharing links, shut off “Anyone” links at the tenant level, and repair folders whose permissions broke away from their parent.
6. Label what Copilot should never read. Sensitivity labels on credit applications, payroll, and HR files, then a Purview data loss prevention policy for Copilot that keeps labeled files and emails out of its answers. A second policy can stop Copilot from responding to prompts that contain things like Social Security numbers.
7. Agents and connectors get a short leash. In the Microsoft 365 admin center, an admin chooses which agents the store allows at all. Nothing gets connected with admin rights because it’s quicker.
8. Turn on the record. Microsoft Purview can audit Copilot activity, keep or delete Copilot conversations under a retention policy, and search them later if a lawyer or a regulator asks.

Steps 2 and 3 do most of the work. They’re also the ones stores skip, because they don’t feel like AI, they don’t come with a demo, and nobody gets a new button to click at the end when they’re done.

One honest note on cost and time. How long this takes depends entirely on how a store’s Microsoft 365 was built and how many people have touched it since. A single rooftop with tidy sites is a different job from a group that’s been adding stores and copying accounts for ten years. Some of the Purview tools above also depend on which Microsoft 365 plan you’re on, and that’s worth checking before anyone promises a date.

Do the boring part first.

How This Lines Up With the FTC Safeguards Rule

None of this is new as a requirement. The Safeguards Rule already asks a dealership to implement and periodically review access controls that “limit authorized users’ access only to customer information that they need to perform their duties and functions.” That’s 16 CFR 314.4(c)(1), word for word.

A store that already meets that line is most of the way to a safe Copilot rollout. A store that doesn’t has a Safeguards gap today, with or without AI, and Copilot just makes the gap easier to use. Our FTC Safeguards Rule checklist walks through the rest of the rule, and if you’re wondering what happens when customer data lands in public AI tools instead, we covered that in public AI and customer PII.

Fix access for the rule, and Copilot gets safer as a side effect.

What Dealers Say When We Bring This Up

“It’s Microsoft. Isn’t it already secure?”

Microsoft’s side is. Encryption, tenant isolation, the training commitments, all of it. The permissions inside your tenant are yours, and Microsoft says so in plain words. They can’t know that your F&I folder shouldn’t be open to the service department.

“We’ll only give it to the managers.”

Managers usually carry the broadest access in the building, because they’ve been there longest and picked up permissions with every promotion, every covered vacation, and every project nobody cleaned up afterward. That’s exactly the group whose permissions you want to look at first, not the group you skip.

“Our IT guy set up SharePoint. We’re fine.”

He probably set it up to work, and it does. Built to work and built to be searched by AI are two different standards, and the second one didn’t exist when most stores built their sites. A second look isn’t a verdict on him. Plenty of stores bring us in on a co-managed basis for exactly this kind of project, and their IT person stays in charge.

Different objection, same answer. Look first.

Straight Answers on Copilot at the Store

Fix the Access, Then Flip the Switch

Cox Automotive’s AI Readiness in Auto Retail study, which surveyed 537 franchise dealership leaders in 2025, found 60% had concerns about data and algorithms. They’re right to. We support 2,000-plus dealerships and about 35,000 dealership employees, and the AI rollouts that go well start with the same unglamorous step. Know who can open what. That’s where the peace of mind comes from.

Whenever something isn’t going the way I want, I ask myself what I’m not doing. With Copilot, the answer is almost never the AI. It’s the permissions nobody has looked at since the store went to Microsoft 365. Looking at them every day is the job of managed Microsoft 365.

If you want an outside read on yours, start with our complimentary IT and cybersecurity assessment. If AI is the bigger question, our AI readiness assessment for dealerships looks at the AI tools your staff already uses, the customer data they can reach, and your Microsoft 365 permissions, in one written report.

Copilot is the last switch you flip, not the first.