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: learn-pr/wwl/design-responsible-ai-security-governance-risk-management-compliance/includes/7-validate-data-residency-movement-compliance.md
@@ -6,162 +6,98 @@ Solution architects must know where data is stored, how it moves across services
6
6
7
7
## Learning Objectives
8
8
9
-
After completing this unit, learners will be able to:
9
+
-After completing this unit, learners will be able to:
10
10
11
-
Identify required data residency and sovereignty requirements for AI workloads.
11
+
-Identify required data residency and sovereignty requirements for AI workloads.
12
12
13
-
Validate how Copilot Studio manages customer data, logs, and model interactions.
13
+
-Validate how Copilot Studio manages customer data, logs, and model interactions.
14
14
15
-
Assess and restrict data movement across regions for generative AI capabilities.
15
+
-Assess and restrict data movement across regions for generative AI capabilities.
16
16
17
-
Apply Purview capabilities to strengthen compliance controls for Microsoft 365 Copilot.
17
+
-Apply Purview capabilities to strengthen compliance controls for Microsoft 365 Copilot.
18
18
19
-
Recommend architectural controls that ensure compliant endtoend data handling.
19
+
-Recommend architectural controls that ensure compliant endtoend data handling.
20
20
21
21
## Key Concepts for Data Residency Compliance
22
22
23
23
### 1. Understanding Data Residency Boundaries
24
24
25
-
Data residency defines the physical or geographic location where customer data is stored and processed. AI solutions use multiple services and toolchains, so architects must understand:
25
+
Data residency defines the physical or geographic location where customer data is stored and processed.
26
26
27
-
Where user prompts, context, and model inputs are processed.
27
+
#### AI solutions use multiple services and toolchains, so architects must understand:
28
28
29
-
Which services store logs, conversations, or telemetry.
29
+
- Where user prompts, context, and model inputs are processed.
30
30
31
-
Whether data used by generative AI stays within the designated region.
31
+
- Which services store logs, conversations, or telemetry.
32
32
33
-
How multitenant cloud services distribute workloads.
33
+
- Whether data used by generative AI stays within the designated region.
34
34
35
-
#### Professional Visual - Data Residency Boundary Map (TextBased)
36
-
37
-
+------------------------------+
38
-
39
-
| Data Residency Zones |
40
-
41
-
+------------------------------+
42
-
43
-
| • Data Input Region |
44
-
45
-
| • AI Processing Region |
46
-
47
-
| • Storage & Logging Region |
48
-
49
-
| • Backup/DR Region |
50
-
51
-
+------------------------------+
35
+
- How multitenant cloud services distribute workloads.
52
36
53
37
### 2. Copilot Studio Data Residency Behavior
54
38
55
-
Copilot Studio enforces regional boundaries depending on the environment configuration. Architects should validate:
56
-
57
-
Where prompt data and agent interactions are processed.
39
+
Copilot Studio enforces regional boundaries depending on the environment configuration.
58
40
59
-
Whether unpublished agents and preview features follow different residency rules.
41
+
#### Architects should validate:
60
42
61
-
How data is stored when agents use connectors or custom plugins.
43
+
- Where prompt data and agent interactions are processed.
62
44
63
-
Whether crossregion interactions occur during inference or orchestration.
45
+
-Whether unpublished agents and preview features follow different residency rules.
64
46
65
-
### 3. Data Movement Controls for Generative AI
66
-
67
-
Generative AI features may require movement of data for model evaluation, orchestration, or enrichment. To validate compliance:
68
-
69
-
Determine which components may transmit data outside the region.
70
-
71
-
Confirm whether data movement is necessary or optional.
72
-
73
-
Review environment settings that allow or restrict crossgeographic model operations.
47
+
- How data is stored when agents use connectors or custom plugins.
74
48
75
-
Apply configuration policies that block crossregion routing for sensitive workloads.
49
+
- Whether crossregion interactions occur during inference or orchestration.
76
50
77
-
#### Professional Visual - AI Data Movement Control Flow (TextBased)
78
-
79
-
User Action → AI Request → Model Processing
51
+
### 3. Data Movement Controls for Generative AI
80
52
81
-
| | |
53
+
Generative AI features may require movement of data for model evaluation, orchestration, or enrichment.
82
54
83
-
v | v
55
+
#### To validate compliance:
84
56
85
-
Residency Checks <--+--- Region Enforcement
57
+
- Determine which components may transmit data outside the region.
86
58
87
-
|
59
+
- Confirm whether data movement is necessary or optional.
88
60
89
-
v
61
+
- Review environment settings that allow or restrict crossgeographic model operations.
90
62
91
-
Compliant Output
63
+
- Apply configuration policies that block crossregion routing for sensitive workloads.
92
64
93
65
### 4. Purview Controls for Microsoft 365 Copilot
94
66
95
-
Microsoft Purview provides governance, labeling, and monitoring necessary to validate compliant data handling. Solution architects should:
96
-
97
-
Apply sensitivity labels that restrict crosstenant or crossregion transmission.
98
-
99
-
Use data loss prevention (DLP) rules to prevent sensitive data from being used in AI prompts or outputs.
67
+
Microsoft Purview provides governance, labeling, and monitoring necessary to validate compliant data handling.
100
68
101
-
Review auditing, policy insights, and compliance documentation for Copilot solutions.
69
+
#### Solution architects should:
102
70
103
-
Validate that Copilot interaction logs follow organizational residency rules.
71
+
- Apply sensitivity labels that restrict crosstenant or crossregion transmission.
0 commit comments