Forum Discussion
Company-Wide Copilot Prompt Library (Enterprise)
Question Regarding Organizational Prompt Import Fields
I'm working on importing prompts into the Microsoft 365 Copilot Organizational Prompts library using the CSV import process.
According to the documentation, each prompt can include the following fields:
- Title
- Display Prompt
- Prompt
- Language
- Task Type
- Department
- Supported Apps
- Description
My question is:
Which of these fields accept administrator-defined free-form text, and which fields must use predefined Microsoft-supported values when importing prompts via CSV?
For example, the documentation appears to indicate that:
- Language uses supported locale values (such as en-US, es-ES, etc.).
- Task Type uses supported task type values (such as Analyze, Create, Edit, etc.).
However, it isn't clear whether fields such as Department and Supported Apps also require predefined values, or if administrators can enter their own custom values.
Specifically, I'm trying to determine:
- Which fields accept free-form text?
- Which fields require values from a Microsoft-defined list?
- For any fields that require predefined values, where can the complete list of valid values be found?
Reference: https://learn.microsoft.com/en-us/microsoft-365/copilot/organizational-prompts#prompt-fields-reference
Any input would be very much appreciated! Thank you!
1 Reply
Microsoft’s field reference separates authored text from controlled metadata. Title, Display Prompt, Prompt Text, Department, and Description accept text within their character limits. Department is explicitly documented as free-form. Treat Locale, Task Type, and Products as controlled values.
For Locale, use View all supported locales in the import flyout. For Task Type, use View all supported task types there; Analyze, Create, and Edit are examples. Products is the CSV column for Supported Apps and selects the Copilot surfaces where the prompt appears, so use only values accepted by the import template or admin experience.
Download a fresh template from the tenant, create a test row, save it as UTF-8 CSV, and review the validation preview before importing the set. The public field table does not publish a complete Products list. Avoid guessing values; if the required surface is not offered by the template or validation, open a Microsoft support case.