For years, teams have learned ERP systems by remembering where things are. Which menu to open. Which button to click. Which process comes next. Copilot is changing that.
Instead of navigating through Dynamics 365 step by step, users will increasingly ask questions, generate content and complete tasks with AI support. The system is becoming more conversational, and that changes how people interact with it every day. That is exciting, but it also creates a different kind of challenge. Switching Copilot on is the easy part. Helping people use it well takes more thought.
Before you read on: Take our free 5-minute ERP readiness assessment to spot risks early, benchmark your implementation and get practical next steps to improve delivery.
How Copilot changes how work gets done
Most ERP projects ask teams to learn a new system. Copilot asks them to work differently inside that system. Instead of clicking through familiar menus, users may ask questions in plain English. They might create reports in seconds or let AI draft responses they would previously have written themselves.
That is a much bigger shift than adding another feature.
Some people will embrace it immediately. Others will hesitate because they are unsure when they should trust the output or when they should ignore it. Neither response is unusual. People need time to build confidence before new habits start to stick.
What to do now to get your teams ready
1. Give teams guidance before they invent their own
One thing tends to happen when organisations roll out new technology without much direction. People make it up as they go. One manager writes detailed prompts. Another asks vague questions. Someone copies prompts from LinkedIn. Someone else decides Copilot is unreliable after one poor result and stops using it altogether.
After a few weeks, every team has its own way of working. A little guidance early on prevents a lot of inconsistency later. Show people what good looks like. Explain where Copilot adds value and where human judgement still matters. Give examples they can actually relate to instead of expecting everyone to figure it out themselves.
2. Training needs to happen while teams work
Think back to the last training session you attended. How much of it could you repeat three weeks later? That is the challenge. Even well-delivered classroom training fades surprisingly quickly once people go back to answering emails and dealing with customers. By the time someone finally needs to complete a task, the session is often a distant memory.
That is why support inside the flow of work makes such a difference. With ClickLearn, users can access guidance while they are using Dynamics 365 instead of relying on notes or memory. They get help at the point they need it, which makes learning feel far more natural.
3. Expect confidence to rise and fall
People rarely move from uncertainty to confidence in a straight line. The first few days often bring curiosity because everything feels new. Then reality sets in. Users hit situations they have not seen before. They question themselves. Some stop using Copilot altogether because it feels quicker to return to the methods they already know.
That dip catches plenty of organisations off guard. It does not mean the rollout has failed. It simply means people still need support while new habits are forming. Managers who recognise that early can step in before confidence turns into frustration.
4. Governance is about giving teams confidence
When governance comes up, people often think about policies and permissions. Those things matter, but they are only part of the picture.
Good governance also gives people confidence to use Copilot properly. Users should know which tasks suit AI, where sensitive information needs extra care and when they are expected to check the output before acting on it. Clear guidance removes uncertainty, and people are far more likely to use new tools when they understand the boundaries.
5. Business readiness starts before Copilot goes live
It is easy to treat Copilot like another feature release. In practice, it asks people to rethink the way they approach everyday work. That means preparing your teams before access is switched on, giving them support while they learn and reinforcing good habits once they start using it. The organisations that get the most value from Copilot are usually the ones that spend as much time preparing people as they do preparing the technology.
How BR One helps organisations prepare for Copilot
We help organisations prepare their teams for changes like Copilot before those changes reach the business. That means helping leaders think through governance, supporting managers, building practical adoption plans and creating role-based guidance that reflects how teams actually work.
Alongside our business readiness services, we use ClickLearn to provide scalable learning content and in-app support that helps users build confidence as they use Dynamics 365. The aim is simple. Help people feel comfortable using Copilot from day one instead of expecting them to work it out for themselves.
If your organisation is planning to introduce Copilot into Dynamics 365, get in touch with our team for personalised advice.