Your Copilot Licence Is Collecting Dust. Here's Why.

Accenture just deployed Microsoft Copilot to all 743,000 of its employees. That is a large number. It tells you nothing about whether those employees are actually using it.

I have seen this at scale closer to home. Copilot licences sitting unused at BFSI and aviation clients three months after purchase. The tool works. The rollout did not. Procurement happened. Training did not.

A licence gives access. It does not give capability.

Deploying a licence takes a procurement sign-off and an IT ticket. What it does not do is change how people write emails, run meetings, or process documents. The tool is in their hands. The habit is not. Accenture's 743,000-seat deployment is a supply decision, not a demand decision.

Large-scale rollouts are not inherently wrong. But if you do not build the capability alongside the access, you end up with expensive shelf-ware and a team that has already decided the tool is not useful — before anyone showed them how to use it properly.

What employees actually ask first

When I run Copilot sessions at enterprises, the first question is never about features. It is always some version of: "Will this read my personal emails?" Privacy anxiety is real, especially among teams already aware of conversations around data handling and the RBI circular. Trust has to be built before productivity can follow.

Most employees also conflate Copilot with public ChatGPT. They assume their prompts are going somewhere public. They are not — Copilot runs within your Microsoft 365 tenant. But if your rollout skips this explanation, people will limit their usage out of caution, and you will read that as low adoption.

The prompt is the real skill gap

At Kotak and at BIAL, the pattern was identical. An AI tool was live. Adoption metrics were flat. When I asked employees why they were not using it, the answer was almost always the same: "I am not sure what to type."

Copilot does not fail because of the model. It fails because people type three words and expect a finished report. Prompting is a learnable skill, and most organisations are not teaching it. Vague prompt: "Summarise the meeting." Structured prompt using the CRAFT framework — role, request, context, format, tone — produces output your team can actually use. The difference is not subtle.

What a real rollout looks like

Start with 20 to 30 power users, not the whole organisation at once. Map one genuinely painful workflow per team before training begins. Measure time saved on real tasks, not satisfaction scores. Put a local champion in each team — someone who is not from IT, who can answer "how does this apply to my actual work?" without escalating to the helpdesk.

In Indian GCC and enterprise environments there is an added layer. Many employees still use WhatsApp as their primary work communication tool. Copilot lives inside Outlook, Teams, and Word. The behaviour shift required is larger than in a Microsoft-native organisation. Your training has to account for that, not assume it away.

If your organisation has Copilot licences and flat adoption, the training design is almost certainly the issue — not the tool. Our 20-hour Copilot 365 programme is built specifically for enterprise teams in India. Or book a 30-minute call and we can look at your specific situation together.