Skip to content

Commit 0992af0

Browse files
authored
Update search-security-overview.md
Changing some wording and adding important notes.
1 parent 05fd3f5 commit 0992af0

File tree

1 file changed

+5
-4
lines changed

1 file changed

+5
-4
lines changed

articles/search/search-security-overview.md

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -166,17 +166,18 @@ Currently, the only external resource that a search service writes customer data
166166

167167
### Exceptions to data residency commitments
168168

169-
Although customer data isn't stored outside of your region, object names will appear in the telemetry logs used by Microsoft Support to troubleshoot your service issues. Object names are considered customer data. Names in telemetry logs include those of indexes, indexers, data sources, skillsets, containers, and key vault store.
169+
Although customer data isn't stored outside of your region, object names (considered as customer data), will appear in the telemetry logs used by Microsoft Support to troubleshoot your service issues. Telemetry logs includes names of indexes, indexers, data sources, skillsets, containers, and key vault store.
170170

171-
Object names aren't obfuscated in the telemetry logs. If possible, avoid using names that convey sensitive information.
171+
>[!IMPORTANT]
172+
>Object names aren't obfuscated in the telemetry logs. If possible, please avoid using names that convey sensitive information.
172173
173-
Telemetry logs are retained for one and a half years. During that period, support engineers might access and reference object names under these conditions:
174+
Telemetry logs are retained for one and a half years. During that period, support engineers might access and reference object names under the following conditions:
174175

175176
+ Diagnose an issue, improve a feature, or fix a bug. In this scenario, data access is internal only, with no third-party access.
176177

177178
+ Proactively suggest to the original customer a workaround or alternative. For example, "Based on your usage of the product, consider using `<feature name>` since it would perform better." In this scenario, Microsoft might expose an object name through dashboards visible to the customer.
178179

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, the trade off is reduced ability to troubleshoot any issues related to the object in question.
180+
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 will reduce the ability to troubleshoot with historical information related to the object in question.
180181

181182
To remove references to specific objects, or to change the data retention period, [file a support ticket](/azure/azure-portal/supportability/how-to-create-azure-support-request) for your search service.
182183

0 commit comments

Comments
 (0)