Adding Copilot and AI features to model-driven apps

Model-driven apps can include a Copilot pane that answers questions about your data and helps users fill in forms. Turning it on is quick; making it useful and safe takes a little more care.

Turn it on

Copilot for model-driven apps is controlled per environment in the Power Platform admin center, under the environment's feature settings. Your admin can enable it there. App makers can then control behaviour for individual apps in the app's settings in the designer.

What users get

• Ask questions about data — for example, "Show accounts in London with open opportunities".
• Summaries of a record, so users can catch up on a case or account quickly.
• Form fill assistance, which suggests values based on context such as an email the user pasted.

Make answers accurate

Copilot relies on your metadata. A few small changes make a big difference:

1. Describe tables and columns. Write plain descriptions — "Date the customer signed the contract" — instead of leaving them blank.
2. Use clear display names. Contract Signed On is easier to understand than new_csdate.
3. Clean up unused columns. Fewer, clearer columns mean fewer wrong guesses.

Governance

Copilot respects Dataverse security: users only see rows and columns they already have access to. Still, agree on a few rules before rollout:

• Which environments allow Copilot (start with test, then production).
• Whether data may be processed outside your geography — this is an admin setting.
• How users can report a wrong or unhelpful answer.

Rollout checklist