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: copilot/microsoft-365-copilot-privacy.md
+19-6Lines changed: 19 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ ms.localizationpriority: medium
10
10
ms.collection: Tier1
11
11
description: "Learn how Microsoft 365 Copilot uses data and how it stores and protects that data."
12
12
hideEdit: true
13
-
ms.date: 11/06/2023
13
+
ms.date: 11/10/2023
14
14
---
15
15
16
16
# Data, Privacy, and Security for Microsoft 365 Copilot
@@ -57,7 +57,7 @@ Abuse monitoring for Microsoft 365 Copilot occurs in real-time, without providin
57
57
58
58
### Microsoft 365 Copilot and public web content
59
59
60
-
Microsoft 365 Copilot chat experiences can reference public web content when responding to a user’s prompt. Based on the user’s prompt, Copilot determines whether it needs to use Bing to query public web content to help provide a relevant response to the user.
60
+
Microsoft 365 Copilot chat experiences can reference public web content when responding to a user’s prompt. Based on the user’s prompt, Microsoft 365 Copilot determines whether it needs to use Bing to query public web content to help provide a relevant response to the user.
61
61
62
62
If Microsoft 365 Copilot determines web content can help provide a more relevant response, it generates a search query to send to Bing. That search query is based on the user’s prompt, conversation history, and data the user has access to in Microsoft 365. This query might include your organization’s data, but the user’s account and their tenant ID aren't included in the search query sent to Bing.
63
63
@@ -70,7 +70,20 @@ Admins can prevent their users from referencing public web content in their requ
70
70
71
71
### Extensibility of Microsoft 365 Copilot
72
72
73
-
While Microsoft 365 Copilot is already able to use the apps and data within the Microsoft 365 ecosystem, many users still depend on various external tools and services for work management and collaboration. Customers can address this gap by extending Microsoft 365 Copilot to enable users to work with their third-party tools and services. This can be done through extending Microsoft 365 Copilot by building a plug-in or by connecting to an external data source. For more information, see [Extend Microsoft 365 Copilot](/microsoftteams/platform/copilot/how-to-extend-copilot).
73
+
While Microsoft 365 Copilot is already able to use the apps and data within the Microsoft 365 ecosystem, many organizations still depend on various external tools and services for work management and collaboration. Microsoft 365 Copilot experiences can reference third-party tools and services when responding to a user’s request by using [Microsoft Graph connectors](/graph/connecting-external-content-connectors-overview) or plugins. Data from Graph connectors can be returned in Microsoft 365 Copilot responses if the user has permission to access that information.
74
+
75
+
When plugins are enabled, Microsoft 365 Copilot determines whether it needs to use a specific plugin to help provide a relevant response to the user. If a plugin is needed, Microsoft 365 Copilot generates a search query to send to the plugin on the user’s behalf. The query is based on the user’s prompt, conversation history, and data the user has access to in Microsoft 365.
76
+
77
+
In the **Integrated apps** section of the [Microsoft 365 admin center](/microsoft-365/admin/admin-overview/admin-center-overview), admins can view the permissions and data access required by a plugin as well as the plugin’s terms of use and privacy statement. Admins have full control to select which plugins are allowed in their organization. A user can only access the plugins that their admin allows and that the user installed or is assigned. Microsoft 365 Copilot only uses plugins that are turned on by the user.
78
+
79
+
> [!NOTE]
80
+
> The policy settings that control the use of optional connected experiences in Microsoft 365 Apps don’t apply to plugins.
81
+
82
+
For more information, see the following articles:
83
+
84
+
-[Manage Plugins for Copilot in Integrated Apps](/microsoft-365/admin/manage/manage-plugins-for-copilot-in-integrated-apps)
85
+
-[Extend Microsoft 365 Copilot](/microsoftteams/platform/copilot/how-to-extend-copilot)
86
+
-[How Microsoft 365 Copilot can work with your external data](https://techcommunity.microsoft.com/t5/microsoft-mechanics-blog/how-microsoft-365-copilot-can-work-with-your-external-data/ba-p/3937645)
74
87
75
88
## How does Microsoft 365 Copilot protect organizational data?
76
89
@@ -98,7 +111,7 @@ For European Union (EU) users, we have additional safeguards to comply with the
98
111
99
112
## Microsoft 365 Copilot and data residency
100
113
101
-
Customers with [Advanced Data Residency (ADR) in Microsoft 365](/microsoft-365/enterprise/advanced-data-residency) or [Microsoft 365 Multi-Geo](/microsoft-365/enterprise/microsoft-365-multi-geo) can purchase and enable Microsoft 365 Copilot. However, at this time, Microsoft Copilot doesn't provide data residency commitments for Microsoft 365 Copilot customer data-at-rest.
114
+
Customers with [Advanced Data Residency (ADR) in Microsoft 365](/microsoft-365/enterprise/advanced-data-residency) or [Microsoft 365 Multi-Geo](/microsoft-365/enterprise/microsoft-365-multi-geo) can purchase and enable Microsoft 365 Copilot. However, at this time, Microsoft 365 Copilot doesn't provide data residency commitments for Microsoft 365 Copilot customer data-at-rest.
102
115
103
116
## Meeting regulatory compliance requirements
104
117
@@ -120,7 +133,7 @@ If you turn off connected experiences that analyze content for Microsoft 365 App
120
133
- Outlook (classic)
121
134
- Word
122
135
123
-
Similarly, Copilot features in those apps on Windows or Mac devices won’t be available if you turn off the use of connected experiences for Microsoft 365 Apps.
136
+
Similarly, Microsoft 365 Copilot features in those apps on Windows or Mac devices won’t be available if you turn off the use of connected experiences for Microsoft 365 Apps.
124
137
125
138
For more information about these policy settings, see the following articles:
126
139
@@ -148,5 +161,5 @@ We aim to help our customers use our AI products responsibly, sharing our learni
Copy file name to clipboardExpand all lines: microsoft-365/commerce/licenses/manage-auto-claim-policies.md
-5Lines changed: 0 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -166,11 +166,6 @@ If you have backup products assigned to the policy, you can change the order in
166
166
167
167
## Auto-claim policies for Microsoft Power Apps
168
168
169
-
> [!NOTE]
170
-
> The ability to create auto-claim policies for Microsoft Power Apps is currently in preview. The auto-claim policies for Power Apps is being gradually rolled out across areas and might not be available yet in your area.
171
-
172
-
Preview features aren't meant for use in production and can have limited functionality. These features are made available to customers before an official release so that they can get early access to the features and provide feedback.
173
-
174
169
Admins can now create auto-claim policies for Power Apps per user licenses in the Microsoft 365 admin center, similar to how they can create auto-claim policies for other Microsoft products and services. After the policy is set, any user in the organization who requests an individual Power Apps license is automatically granted one.
175
170
176
171
If a user lacks a standalone Power Apps license and launches an app that requires a premium license, the system automatically grants a Power Apps per user license to the user.
Copy file name to clipboardExpand all lines: microsoft-365/frontline/deploy-dynamic-teams-at-scale.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,7 @@ ms.collection:
16
16
appliesto:
17
17
- Microsoft Teams
18
18
- Microsoft 365 for frontline workers
19
-
ms.date: 11/06/2023
19
+
ms.date: 11/10/2023
20
20
21
21
---
22
22
@@ -42,19 +42,19 @@ Team membership is automatically managed over time through the power of dynamic
42
42
43
43
## Prerequisites
44
44
45
+
> [!IMPORTANT]
46
+
> The admin running the deployment process must be a Global admin.
47
+
45
48
- Users must have a Microsoft 365 F3, F1, E3, or E5 license. If a user doesn't have one of these licenses, they'll need a Microsoft Entra ID P1 add-on license to use dynamic teams. [Learn more about frontline licensing](flw-licensing-options.md).
46
-
- The admin running the deployment process must be a Teams admin and Global admin.
49
+
- Ensure you can define your frontline workers and their work locations through data available in Microsoft Entra ID. If you don't have this data in Microsoft Entra ID, you can sync it through a [human capital management (HCM) connector](/azure/active-directory/app-provisioning/plan-cloud-hr-provision) or [use the PowerShell solution](deploy-teams-at-scale.md) to create static teams at scale.
50
+
51
+
When evaluating the right solution for your organization, we recommend you do the following:
47
52
48
-
- Ensure you can define your frontline workers and their work locations through data available in Microsoft Entra ID. If you don't have this data in Microsoft Entra ID, you can sync it through a [human capital management (HCM) connector](/azure/active-directory/app-provisioning/plan-cloud-hr-provision) or [use the PowerShell solution](deploy-teams-at-scale.md) to create teams at scale.
49
-
- When evaluating the right solution, we recommend you do the following:
50
53
1. Plan your frontline deployment.
51
-
1. Test the deploy tools (dynamic or static team creation).
54
+
1. Test the deploy tools—dynamic team creation (the process described in this article) or static team creation (using the [PowerShell solution](deploy-teams-at-scale.md)). Keep in mind that static teams aren't managed automatically.
52
55
1. Deploy to a pilot location.
53
56
1. Deploy to a broader set of locations using a phased approach.
54
57
55
-
>[!NOTE]
56
-
>The PowerShell solution creates static teams, which aren't managed automatically.
57
-
58
58
## Set up your frontline dynamic teams
59
59
60
60
1. In the left navigation of the [Teams admin center](https://admin.teams.microsoft.com), choose **Teams** > **Manage frontline teams**.
0 commit comments