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: articles/search/search-security-overview.md
+3-19Lines changed: 3 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -166,29 +166,13 @@ Currently, the only external resource that a search service writes customer data
166
166
167
167
### Exceptions to data residency commitments
168
168
169
-
Object names will be stored and processed outside of your selected region or location. Customers shouldn't place any sensitive data in name fields or create applications designed to store sensitive data in these fields. This data will appear in the telemetry logs used by Microsoft to provide support for the service. Object names include names of indexes, indexers, data sources, skillsets, containers, and key vault store.
169
+
Object names will be stored and processed outside of your selected region or location. Customers shouldn't place any sensitive data in name fields or create applications designed to store sensitive data in these fields. This data will appear in the telemetry logs used by Microsoft to provide support for the service. Object names include names of indexes, indexers, data sources, skillsets, resources, containers, and key vault store.
170
170
171
171
Telemetry logs are retained for one and a half years. During that period, Microsoft might access and reference object names under the following conditions:
172
172
173
173
+ Diagnose an issue, improve a feature, or fix a bug. In this scenario, data access is internal only, with no third-party access.
174
174
175
-
+ During support, this information may be used to make suggestions to the customer. For example, "Based on your usage of the product, consider using `<feature name>` since it would perform better."
176
-
177
-
+ Microsoft might expose an object name in dashboards visible to the customer.
178
-
179
-
Upon request, Microsoft can shorten the retention interval or remove references to specific objects in the telemetry logs. Remember that if you request data removal, Microsoft won't have a full history of your service, which could impede troubleshooting of the object in question.
180
-
181
-
To remove references to specific objects, or to change the data retention period, [file a support ticket](../azure-portal/supportability/how-to-create-azure-support-request.md) for your search service.
182
-
183
-
1. In **Problem details**, tag your request using the following selections:
184
-
185
-
+**Issue type**: Technical
186
-
+**Problem type**: Setup and configuration
187
-
+**Problem subtype**: Issue with security configuration of the service
188
-
189
-
1. When you get to **Additional details** (the third tab), describe the object names you would like removed, or specify the retention period that you require.
190
-
191
-
:::image type="content" source="media/search-security-overview/support-request.png" alt-text="Screenshot of the first page of the support ticket with issue and problem types selected." border="true":::
175
+
+ During support, this information may be used to provide quick resolution to issues and escalate product team if needed
192
176
193
177
<aname="encryption"></a>
194
178
@@ -258,4 +242,4 @@ Watch this fast-paced video for an overview of the security architecture and eac
0 commit comments