Merge pull request #180348 from yelevin/patch-8

Update data residency regions, take 2

Author: PMEds28

articles/sentinel/quickstart-onboard.md

@@ -32,8 +32,10 @@ After you connect your data sources, choose from a gallery of expertly created w
 
 - **Permissions**:
 
-    - To enable Microsoft Sentinel, you need contributor permissions to the subscription in which the Microsoft Sentinel workspace resides. 
-    - To use Microsoft Sentinel, you need either contributor or reader permissions on the resource group that the workspace belongs to.
+    - To enable Microsoft Sentinel, you need **contributor** permissions to the subscription in which the Microsoft Sentinel workspace resides. 
+
+    - To use Microsoft Sentinel, you need either **contributor** or **reader** permissions on the resource group that the workspace belongs to.
+
     - Additional permissions may be needed to connect specific data sources.
 
 - **Microsoft Sentinel is a paid service**. For more information, see [About Microsoft Sentinel](https://go.microsoft.com/fwlink/?linkid=2104058) and the [Microsoft Sentinel pricing page](https://azure.microsoft.com/pricing/details/azure-sentinel/)
@@ -42,29 +44,11 @@ For more information, see [Pre-deployment activities and prerequisites for deplo
 
 ### Geographical availability and data residency
 
-- Microsoft Sentinel can run on workspaces in most [GA regions of Log Analytics](https://azure.microsoft.com/global-infrastructure/services/?products=monitor) except the China and Germany (Sovereign) regions. New Log Analytics regions may take some time to onboard the Microsoft Sentinel service. 
-
-- Data generated by Microsoft Sentinel, such as incidents, bookmarks, and analytics rules, may contain some customer data sourced from the customer's Log Analytics workspaces. This Microsoft Sentinel-generated data is saved in the geography listed in the following table, according to the geography in which the workspace is located:
-
-    | Workspace geography | Microsoft Sentinel-generated data geography |
-    | --- | --- |
-    | United States<br>India | United States |
-    | Europe<br>France | Europe |
-    | Australia | Australia |
-    | United Kingdom | United Kingdom |
-    | Canada | Canada |
-    | Japan | Japan |
-    | Asia Pacific | Asia Pacific * |
-    | Brazil | Brazil * |
-    | Norway | Norway |
-    | Africa | Africa |
-    | Korea | Korea |
-    | Germany | Germany |
-    | United Arab Emirates | United Arab Emirates |
-    | Switzerland | Switzerland |
-    |
-
-    \* Single-region data residency is currently provided only in the Southeast Asia region (Singapore) of the Asia Pacific geography, and in the Brazil South (Sao Paulo State) region of the Brazil geography. For all other regions, customer data can be stored anywhere in the geography of the workspace where Sentinel is onboarded.
+- Microsoft Sentinel can run on workspaces in most [regions where Log Analytics is generally available](https://azure.microsoft.com/global-infrastructure/services/?products=monitor). Regions where Log Analytics is newly available may take some time to onboard the Microsoft Sentinel service. 
+
+- See [Data residency in Azure](https://azure.microsoft.com/global-infrastructure/data-residency/) for information on [Geos and regions](https://azure.microsoft.com/global-infrastructure/data-residency/#select-geography) and on [where customer data is stored](https://azure.microsoft.com/global-infrastructure/data-residency/#more-information).
+
+- Single-region data residency is currently provided only in the Southeast Asia (Singapore) region of the Asia Pacific geography, and in the Brazil South (Sao Paulo State) region of the Brazil geography.
 
     > [!IMPORTANT]
     > - By enabling certain rules that make use of the machine learning (ML) engine, **you give Microsoft permission to copy relevant ingested data outside of your Microsoft Sentinel workspace's geography** as may be required by the machine learning engine to process these rules.