You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: concepts/connecting-external-content-experiences.md
+6-9Lines changed: 6 additions & 9 deletions
Original file line number
Diff line number
Diff line change
@@ -42,20 +42,17 @@ To configure your connector for Context IQ:
42
42
To make sure that Copilot for Microsoft 365 uses your content effectively:
43
43
44
44
- Apply [semantic labels](/graph/connecting-external-content-manage-schema). Semantic labels help Copilot for Microsoft 365 interpret the semantic meaning of your schema. Apply as many of them to your schema as applicable. The `iconUrl`, `title`, and `url` labels must be applied for content to surface in Copilot. Users can use semantic labels as part of their prompts in Copilot, but they won't get the expected response if the respective semantic label isn't applied.
45
-
- 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.
46
-
- 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.
45
+
- 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.
46
+
- 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.
47
47
- 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. The connection description should answer the following questions briefly:
48
+
- Provide meaningful descriptions in the **description** property when [creating connections](/graph/api/externalconnectors-external-post-connections). Rich descriptions improve the likelihood of content displaying in Copilot. The connection description should briefly answer the following questions:
49
49
50
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
-
51
+
- How do users refer to this content source in their respective organizations?
52
+
- During what part of the workflow do users refer to this content in their day-to-day work?
56
53
- What are some characteristics of the content?
57
54
58
-
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:
55
+
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:
59
56
60
57
- Open the Admin Center, go to **Search & intelligence** > **Customizations** > **Verticals** and select the **All** vertical.
61
58
- Select **Manage connector result**. Ensure that **Show results inline** is selected and that the connections that you want to enable for Search and Copilot are checked.
0 commit comments