Skip to content

Commit 621ccf1

Browse files
authored
Fix typo in Microsoft Graph description
1 parent 40a2f69 commit 621ccf1

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

concepts/insights-customize-item-insights-privacy.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ The rest of this article describes how an administrator can customize item insig
3737

3838
## Background
3939

40-
At the time of its first release in 2014, Microsot Graph was a backend service for Delve. (Delve was deprecated in December 2024.) They shared a set of privacy controls over both the Office Graph insights and the Delve user experience. Office Graph has since become more independent and powerful, as part of every Microsoft 365 experience and of Microsoft Graph. To offer a coherent Microsoft Graph schema, Microsoft introduced an [itemInsights](/graph/api/resources/iteminsights?view=graph-rest-1.0&preserve-view=true) entity, which inherits all the properties of the pre-existing [officeGraphInsights](/graph/api/resources/officegraphinsights?view=graph-rest-1.0&preserve-view=true) resource, and has kept **officeGraphInsights** around for backward compatibility. The introduction of **itemInsights** also decouples the privacy story for the two independent pieces.
40+
At the time of its first release in 2014, Microsot Graph was a backend service for Delve. (Delve was deprecated in December 2024.) They shared a set of privacy controls over both the Office Graph insights and the Delve user experience. Microsoft Graph has since become more independent and powerful, as part of every Microsoft 365 experience and of Microsoft Graph. To offer a coherent Microsoft Graph schema, Microsoft introduced an [itemInsights](/graph/api/resources/iteminsights?view=graph-rest-1.0&preserve-view=true) entity, which inherits all the properties of the pre-existing [officeGraphInsights](/graph/api/resources/officegraphinsights?view=graph-rest-1.0&preserve-view=true) resource, and has kept **officeGraphInsights** around for backward compatibility. The introduction of **itemInsights** also decouples the privacy story for the two independent pieces.
4141

4242
Although existing apps can continue to use **officeGraphInsights**, they should upgrade to **itemInsights** to gain the flexibility to fine-tune item insights in Microsoft Graph.
4343

0 commit comments

Comments
 (0)