Skip to content

Commit 083cc54

Browse files
authored
Update data-locations.md
Minor clarification changes
1 parent 08f6acf commit 083cc54

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

articles/virtual-desktop/data-locations.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ Azure Resource Manager paths to service objects are considered organizational in
2525

2626
## Customer data
2727

28-
The Azure Virtual Desktop service doesn't directly store any user-created or app-related information, but it does store customer data, such as application names and user principal names, because they're part of the resource deployment process. This information is stored in the geography associated with the region you created the resource in.
28+
The Azure Virtual Desktop service doesn't directly store any User data, i.e. user-created data such as Word documents etc. or application related data such as databases or configuation files, but it does store customer data, such as application names, virtual machine names and user principal names etc., because they're part of the resource deployment process, as described in the Customer input section above. This information is stored in the geography associated with the region you created the resource in. Please see the Data locations section below.
2929

3030
## Diagnostic data
3131

@@ -38,7 +38,9 @@ Diagnostic data is generated by the Azure Virtual Desktop service and is gathere
3838

3939
To keep Azure Virtual Desktop reliable and scalable, traffic patterns and usage are aggregated to check the health and performance of the infrastructure control plane. For example, to help us understand how to ramp up regional infrastructure capacity as service usage increases, we process service usage log data. We then review the logs for peak times and decide where to increase capacity.
4040

41-
Storing service-generated data is currently supported in the following geographies:
41+
## Data locations
42+
43+
Storing Customer data and service-generated data is currently supported in the following geographies:
4244

4345
- United States (US)
4446
- Europe (EU)

0 commit comments

Comments
 (0)