Before you switch Copilot on, spend a week in your data. Here's what I'd check.

If you're about to switch Copilot on, spend a week in your data first.

None of what follows is exciting. That's rather the point.

Start with your description fields. Copilot can only summarise what's actually there, so if half your cases have a subject line and nothing else, people get summaries that tell them nothing and stop opening them by week two.

Then your duplicates. The model has no idea which account record is the real one. It'll pick one anyway and sound completely sure about it.

Have a look at your column names too. Anything still called new_field1 needs renaming, or at least a description, because that text is what the model reads when it's working out what a field means.

Same with the ten years of closed records nobody ever archived. Leave that lot in and you'll get answers pulled from deals that died in 2018.

Watch for free text where a choice column should be. "In Progress", "in progress" and "InProg" are three different things to anything reading them.

And read a sample of your notes and attachments before you make them a knowledge source. A surprising amount of what's in there is people venting about customers.

Nobody signs off a budget for any of this. It isn't the AI project anyone pictured. But it's most of the difference between a pilot that gets extended and one that dies quietly in month three.

What's the worst data you've had to switch AI on top of?

#Dynamics365 #PowerPlatform #MicrosoftCopilot #Dataverse #DataQuality #AIDeveloper