Skip to content

Commit dec86e0

Browse files
committed
docs: add connector description details
1 parent 800fbc1 commit dec86e0

File tree

1 file changed

+9
-1
lines changed

1 file changed

+9
-1
lines changed

concepts/connecting-external-content-experiences.md

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,15 @@ To make sure that Copilot for Microsoft 365 uses your content effectively:
4545
- Apply the `searchable` property label to schema properties with stored content that you would like your users' prompts to match against in Copilot. The `searchable` label is the most important with respect to Copilot because it defines which schema properties can be searched against.
4646
- Add a [urlToItemResolver](/graph/api/resources/externalconnectors-urltoitemresolverbase) in [activitySettings](/graph/api/resources/externalconnectors-activitysettings) when you [create your connection](/graph/connecting-external-content-manage-connections#create-a-connection). A `urlToItemResolver` enables the platform to detect when users share URLs from your external content with each other. Copilot for Microsoft 365 has a higher likelihood of displaying content that has been shared with that user.
4747
- Add [user activities](/graph/api/externalconnectors-externalitem-addactivities) on your items. For a list of supported activity types, see [externalActivity](/graph/api/resources/externalconnectors-externalactivity). Items that have more activities are boosted in importance.
48-
- Provide meaningful descriptions in the `description` property when [creating connections](/graph/api/externalconnectors-external-post-connections). Rich descriptions improve the likelihood of displaying content in Copilot.
48+
- Provide meaningful descriptions in the `description` property when [creating connections](/graph/api/externalconnectors-external-post-connections). Rich descriptions improve the likelihood of displaying content in Copilot. The connection description should answer the following questions briefly:
49+
50+
- What kind of content does this connection have?
51+
52+
- How do users refer to this content source in their respective orgs?
53+
54+
- What part of the workflow do users refer to this content in their day-to-day work?
55+
56+
- What are some characteristics of the content?
4957

5058
In addition, search administrators should ensure that your Microsoft Graph connector connections are enabled for [inline results](/microsoftsearch/connectors-in-all-vertical), by using the following steps:
5159

0 commit comments

Comments
 (0)