System Prompt for Microsoft Copilot Studio

Microsoft Copilot Studio (formerly Power Virtual Agents) lets enterprises build custom Copilots that integrate with Microsoft 365, SharePoint, Dataverse, and the rest of the Microsoft ecosystem. The system instructions field is where you shape your bot's behavior. This guide is the practical version — what works, what does not, and templates for the most common use cases.

The free system prompt generator produces output that copy-pastes cleanly into Copilot Studio's instructions field.

Where the System Prompt Lives in Copilot Studio

In Copilot Studio, the equivalent of a system prompt is the "Instructions" field in the Copilot's General settings. This field accepts free-form text that becomes part of every conversation. Microsoft also auto-generates some baseline instructions based on the Copilot's name, description, and selected capabilities — your custom instructions are layered on top.

You can also add per-topic instructions inside specific topic flows, but the General Instructions are the main lever for overall behavior.

Microsoft 365 Integration Use Case

The most common Copilot Studio use case is an internal helper that knows about the company's SharePoint, Teams channels, and document libraries. System prompt template:

"You are [Company Name]'s internal AI helper. You answer questions about company policies, procedures, and knowledge based on documents in our SharePoint and Teams libraries. You search the knowledge sources first before answering. If you cannot find an answer in the sources, say so clearly — never invent information. Direct sensitive questions (HR, legal, IT security) to the appropriate team. Maintain a professional but friendly tone. Keep responses under 150 words unless the user asks for more detail."

Sales Bot Use Case

For a customer-facing Copilot Studio sales bot connected to your CRM:

"You are [Brand Name]'s sales assistant. You help prospects understand our products, answer pricing questions, and book demos with the sales team. You only discuss [Brand Name] products — politely redirect off-topic conversations. You never discount prices or make promises about discounts. You always offer to connect interested prospects with a human sales rep. You collect lead information (name, company, email) when the prospect is ready to talk to sales."

Sell Custom Apparel — We Handle Printing & Free Shipping

Internal Helper Use Case

For an internal Copilot Studio helper for a specific department (HR, IT, finance):

"You are [Department]'s AI assistant for [Company]. You help employees with [department-specific tasks: filing expenses, requesting time off, finding policies]. You only handle [department] tasks — direct other questions to the appropriate department. You authenticate the user based on their Microsoft 365 sign-in. You never share another employee's information. Escalate complex cases to a human [department] team member."

Common Copilot Studio Mistakes

• Vague instructions — "Be helpful" produces a generic bot. Be specific.
• Skipping the knowledge source setup — instructions tell the bot WHAT to do, knowledge sources tell it WHAT to know. Both matter.
• No escalation path — every internal helper should know when to hand off to a human
• Ignoring topic flows — for high-traffic queries, build a topic flow with deterministic logic instead of relying on the AI alone

Testing in Copilot Studio

Copilot Studio has a built-in test pane that lets you run conversations against your bot before publishing. Use it. Build a test set of 20-30 representative conversations covering: common questions, edge cases, off-topic queries, and adversarial inputs. Run them after every change to the instructions or topics.