What are the Frontify Copilot integrations?
Frontify offers two custom Copilot Studio configurations, helping teams work faster and stay on brand. This setup allows your organization to connect Frontify’s content to Microsoft environments like Teams and M365 apps, through a Copilot you create and maintain.
Note: Frontify does not offer a native integration with Microsoft 365 Copilot. Microsoft Copilot integrations rely on Frontify’s API search contract. This guide provides configuration steps for building your own custom Copilot agent that connects to Frontify’s APIs.
⚠ This is NOT a plug-and-play solution This connection requires technical implementation by your IT team or a qualified developer.
The code examples provided are starting templates that will need customization for your specific use case.
Some prerequisites (e.g. Brand ID, API access, or feature enablement) are tenant-specific and typically handled with your Frontify CSM. |
Using the legacy search API contract? Scroll to the end of this article to learn how to switch to enhancedSearch for a better experience.
DAM integration: Think of Copilot as your asset finder
Use Copilot to search and access assets stored in your Frontify DAM. Instead of switching between tools, just ask Copilot for the asset you need (e.g., “Find me our campaign logo”) and get instant results with previews and download links.
Guidelines integration: Think of Copilot as your brand coach
Use Copilot to retrieve live brand guideline content from Frontify. Ask questions like “What are our official brand colors?” or “Show me our tone of voice rules” and Copilot will provide an instant, accurate answer, with a link back to the exact guideline page or block.
Together, these custom integrations make your brand more accessible than ever, whether you need the right asset or the right rule.
Why should I use these integrations?
Work smarter: Ask Copilot in natural language instead of searching manually.
Save time: Find brand assets or guidance directly within Microsoft tools like Teams.
Stay on brand: Answers and assets always come from your Frontify source of truth.
Secure access: Users only see content they have permission to view in Frontify.
What do I need before setting this up?
For both integrations, you’ll need:
Microsoft Copilot Studio access with permission to create Topics and workflows.
A Frontify access token with GraphQL API access and the beta setting turned on.
Support for Adaptive Cards in your Copilot environment (for asset previews and deep links).
Microsoft Studio tenant with the Frontify API endpoint whitelisted in the Power Platform Admin Center.
For the DAM integration, you also need:
Your Frontify Brand ID (to define which brand assets Copilot should search).
Use of the
enhancedSearchAPI contract for Microsoft Copilot integrations. This contract enables semantic search by understanding the meaning and context of queries rather than relying only on keywords.The legacy
searchcontract remains available for keyword-based search but does not support semantic search and will not receive new features. See below for more information on migration.Note: The
enhancedSearchcontract does not return a total result count due to post-processing and reranking of results.
Brand ID and API token setup are tenant-specific and are provided via your Frontify CSM.
For the Guidelines integration, you also need:
Your Frontify Brand ID (to define what content Copilot has access to).
How does each integration work?
DAM Integration (Asset Finder)
You ask Copilot: “Find the logo for Product X.”
Copilot routes the query to Frontify’s DAM via API using the
enhancedSearchcontract to perform semantic search based on meaning and context.Frontify returns relevant assets.
Copilot displays results as Adaptive Cards with previews and download buttons.
Example use cases:
“Show me campaign images”
“Find our social media banners”
“Get the latest product launch video”
For more information, please review the integration guide.
Guidelines Integration (Brand Coach)
You ask Copilot: “What are our brand colors?”
Copilot identifies the right brand and guideline.
Frontify returns content from the relevant guideline page.
Copilot responds with a concise answer and a deep link back to Frontify.
Example use cases:
“What’s our primary brand color and HEX code?”
“Show me the typography page.”
“What are the logo usage rules?”
"Link me to our tone of voice guidance.”
For more information, please review the integration guide.
Security and permissions
Both integrations respect Frontify’s user permissions. Copilot only surfaces what the API token identity is allowed to access.
Use machine user tokens for production to ensure stability and security.
Rotate tokens regularly and store them securely as environment variables in Copilot Studio.
Example in action
DAM integration:
A marketer types in Microsoft Teams: "Find images from X product launch."
Copilot instantly returns campaign images as Adaptive Cards, ready to preview or download.
Results are ranked based on semantic relevance, not just exact keyword matches.
Guidelines integration:
A sales rep asks: “What’s our official brand font?”
Copilot replies with the typography name, a short explanation, and a link back to the exact page in Frontify.
Benefits
Access both assets and guidelines without leaving Microsoft tools.
Reduce time spent searching for brand information.
Empower employees to stay on brand with minimal effort.
Keep everything governed by the permissions and content in Frontify.
Important note on API migration
If you are currently using the legacy search API contract for Microsoft Copilot integrations, you will need to migrate to enhancedSearch.
What you need to do:
Update your API configuration to replace
searchwithenhancedSearchin your Copilot integration.Review any logic that depends on the total result count, as this is no longer returned in the new contract.
Test your Copilot queries to ensure results meet your expectations with semantic search.
What to expect after migrating:
Improved result relevance, as search is based on meaning and context rather than exact keyword matches.
No total result count in responses due to post-processing and reranking.
Potential differences in result ordering compared to the legacy keyword-based search.
Timeline:
We recommend completing this migration within one month. Most integrations require only minimal changes, typically limited to updating the contract name.
If you need support, please contact your Frontify CSM.