Review

Author: whhender

articles/purview/how-to-integrate-with-azure-security-products.md

@@ -5,7 +5,7 @@ author: aashishr
 ms.author: aashishr
 ms.service: purview
 ms.topic: how-to
-ms.date: 01/23/2022
+ms.date: 03/23/2023
 ---
 # Integrate Microsoft Purview with Azure security products
 
@@ -20,7 +20,9 @@ Classifications and labels applied to data resources in Microsoft Purview are in
 To take advantage of this [enrichment in Microsoft Defender for Cloud](../security-center/information-protection.md), no more steps are needed in Microsoft Purview. Start exploring the security enrichments with Microsoft Defender for Cloud's [Inventory page](https://portal.azure.com/#blade/Microsoft_Azure_Security/SecurityMenuBlade/25) where you can see the list of data sources with classifications and sensitivity labels.
 
 ### Supported data sources
+
 The integration supports data sources in Azure and AWS; sensitive data discovered in these resources is shared with Microsoft Defender for Cloud:
+
 - [Azure Blob Storage](./register-scan-azure-blob-storage-source.md)
 - [Azure Cosmos DB](./register-scan-azure-cosmos-database.md)
 - [Azure Data Explorer](./register-scan-azure-data-explorer.md)
@@ -36,14 +38,16 @@ The integration supports data sources in Azure and AWS; sensitive data discovere
 - [Amazon S3](./register-scan-amazon-s3.md)
 
 ### Known issues
-1. Data sensitivity information is currently not shared for sources hosted inside virtual machines - like SAP, Erwin, and Teradata.
-2. Data sensitivity information is currently not shared for Amazon RDS.
-3. Data sensitivity information is currently not shared for Azure PaaS data sources registered using a connection string. 
-5. Unregistering the data source in Microsoft Purview doesn't remove the data sensitivity enrichment in Microsoft Defender for Cloud.
-6. Deleting the Microsoft Purview account will persist the data sensitivity enrichment for 30 days in Microsoft Defender for Cloud.
-7. Custom classifications defined in the Microsoft Purview compliance portal or Microsoft Purview governance portal aren't shared with Microsoft Defender for Cloud.
+
+- Data sensitivity information is currently not shared for sources hosted inside virtual machines - like SAP, Erwin, and Teradata.
+- Data sensitivity information is currently not shared for Amazon RDS.
+- Data sensitivity information is currently not shared for Azure PaaS data sources registered using a connection string.
+- Unregistering the data source in Microsoft Purview doesn't remove the data sensitivity enrichment in Microsoft Defender for Cloud.
+- Deleting the Microsoft Purview account will persist the data sensitivity enrichment for 30 days in Microsoft Defender for Cloud.
+- Custom classifications defined in the Microsoft Purview compliance portal or Microsoft Purview governance portal aren't shared with Microsoft Defender for Cloud.
 
 ### FAQ
+
 #### **Why don't I see the AWS data source I have scanned with Microsoft Purview in Microsoft Defender for Cloud?**
 
 Data sources must be onboarded to Microsoft Defender for Cloud as well. Learn more about how to [connect your AWS accounts](../security-center/quickstart-onboard-aws.md) and see your AWS data sources in Microsoft Defender for Cloud.
@@ -67,4 +71,5 @@ Customize the Microsoft Purview workbook and analytics rules to best suit the ne
 For more information, see [Tutorial: Integrate Microsoft Sentinel and Microsoft Purview](../sentinel/purview-solution.md).
 
 ## Next steps
+
 - [Experiences in Microsoft Defender for Cloud enriched using sensitivity from Microsoft Purview](../security-center/information-protection.md)