Merge pull request #227304 from sqlshep/sheppardshep-azure-docs-pr

prmerger-automator[bot] · web-flow · commit 6865f2a0fdc6 · 2023-02-27T18:50:44.000Z
sheppardshep  freshness docathon
diff --git a/articles/purview/concept-asset-normalization.md b/articles/purview/concept-asset-normalization.md
@@ -91,7 +91,7 @@ Remove the trailing slash from higher level assets for Azure Blob, ADLS Gen1, an
 
 Applies to: Azure Blob, Azure Data Lake Storage Gen1, Azure Data Lake Storage Gen2
 
-Asset types: "azure_blob_container", "azure_blob_service", "azure_storage_account", "azure_datalake_gen2_service", "azure_datalake_gen2_filesystem", "azure_datalake_gen1_account"
+Asset types: "azure_blob_container", "azure_blob_service", "azure_storage_account", "azure_datalake_gen2_service", "azure_datalake_gen2_filesystem", "azure_datalake_gen1_account".
 
 Before: `https://myaccount.core.windows.net/`
 
diff --git a/articles/purview/concept-best-practices-classification.md b/articles/purview/concept-best-practices-classification.md
@@ -6,7 +6,7 @@ ms.author: ankitgup
 ms.service: purview
 ms.subservice: purview-data-map
 ms.topic: conceptual
-ms.date: 11/18/2021
+ms.date: 02/15/2023
 ---
 
 # Classification best practices in the Microsoft Purview governance portal
diff --git a/articles/purview/concept-best-practices-glossary.md b/articles/purview/concept-best-practices-glossary.md
@@ -6,13 +6,13 @@ ms.author: zeinam
 ms.service: purview
 ms.subservice: purview-data-catalog
 ms.topic: conceptual
-ms.date: 12/15/2021
+ms.date: 02/15/2023
 ---
 
 # Microsoft Purview glossary best practices
 
 The business glossary is a definition of terms specific to a domain of knowledge that is commonly used, communicated, and shared in organizations as they're conducting business. 
-A common business glossary (for example, business language) is significant as it's critical in improving an organizations overall business productivity and performance. You'll observe in most organizations that their business language is being codified based on business dealings associated with:  
+A common business glossary (for example, business language) is significant as it's critical in improving an organizations overall business productivity and performance. You observe in most organizations that their business language is being codified based on business dealings associated with:  
 
 - Business Meetings
 - Stand-Ups, Projects, and Systems (ERP, CRM, SharePoint, etc.). 
diff --git a/articles/purview/concept-best-practices-migration.md b/articles/purview/concept-best-practices-migration.md
@@ -6,7 +6,7 @@ ms.author: hophan
 ms.service: purview
 ms.subservice: purview-data-map
 ms.topic: conceptual
-ms.date: 12/09/2021
+ms.date: 02/15/2023
 ---
 
 # Microsoft Purview backup and recovery for migration best practices  
@@ -45,9 +45,9 @@ The backup should allow saving a point in time copy of the following configurati
 Backup strategy is determined by restore strategy, or more specifically how long it will take to restore things when a disaster occurs. To answer that, you may need to engage with the affected stakeholders (the business owners) and understand what the required recovery objectives are.
 
 There are three main requirements to take into consideration:
-* **Recover Time Objective (RTO)** – This defines the maximum allowable downtime following a disaster for which ideally the system should be back operational.
-* **Recovery Point Objective (RPO)** – This defines the acceptable amount of data loss that is ok following a disaster. Normally this is expressed as a timeframe in hours or minutes.
-* **Recovery Level Object (RLO)** – This defines the granularity of the data being restored. It could be a SQL server, a set of databases, tables, records, etc.
+* **Recover Time Objective (RTO)** – Defines the maximum allowable downtime following a disaster for which ideally the system should be back operational.
+* **Recovery Point Objective (RPO)** – Defines the acceptable amount of data loss that is ok following a disaster. Normally RPO is expressed as a timeframe in hours or minutes.
+* **Recovery Level Object (RLO)** – Defines the granularity of the data being restored. It could be a SQL server, a set of databases, tables, records, etc.
 
 ### High availability
 In computing, the term availability is used to describe the period of time when a service is available, and the time required by a system to respond to a request made by a user. For Microsoft Purview, high availability means ensuring that Microsoft Purview instances are available if there's a problem that is local to a data center or single region in the cloud region.
diff --git a/articles/purview/concept-scans-and-ingestion.md b/articles/purview/concept-scans-and-ingestion.md
@@ -6,7 +6,7 @@ ms.author: shjia
 ms.service: purview
 ms.subservice: purview-data-map
 ms.topic: conceptual
-ms.date: 08/18/2021
+ms.date: 02/14/2023
 ms.custom: ignite-fall-2021
 ---
 
diff --git a/articles/purview/register-scan-amazon-s3.md b/articles/purview/register-scan-amazon-s3.md
@@ -6,7 +6,7 @@ ms.author: aashishr
 ms.service: purview
 ms.subservice: purview-data-map
 ms.topic: how-to
-ms.date: 12/07/2021
+ms.date: 02/15/2023
 ms.custom: references_regions
 # Customer intent: As a security officer, I need to understand how to use the Microsoft Purview connector for Amazon S3 service to set up, configure, and scan my Amazon S3 buckets.
 ---
@@ -16,7 +16,7 @@ ms.custom: references_regions
 
 The Multi-Cloud Scanning Connector for Microsoft Purview allows you to explore your organizational data across cloud providers, including Amazon Web Services in addition to Azure storage services.
 
-This article describes how to use Microsoft Purview to scan your unstructured data currently stored in Amazon S3 standard buckets, and discover what types of sensitive information exists in your data. This how-to guide also describes how to identify the Amazon S3 Buckets where the data is currently stored for easy information protection and data compliance.
+This article describes how to use Microsoft Purview to scan your unstructured data currently stored in Amazon S3 standard buckets, and discover what types of sensitive information exist in your data. This how-to guide also describes how to identify the Amazon S3 Buckets where the data is currently stored for easy information protection and data compliance.
 
 For this service, use Microsoft Purview to provide a Microsoft account with secure access to AWS, where the Multi-Cloud Scanning Connector for Microsoft Purview will run. The Multi-Cloud Scanning Connector for Microsoft Purview uses this access to your Amazon S3 buckets to read your data, and then reports the scanning results, including only the metadata and classification, back to Azure. Use the Microsoft Purview classification and labeling reports to analyze and review your data scan results.
 
@@ -110,7 +110,7 @@ This procedure describes how to create the AWS role, with the required Microsoft
 
 1. Select **New** to create a new credential.
 
-    In the **New credential** pane that appears on the right, in the **Authentication method** dropdown, select **Role ARN**.
+    In the **New credential** pane that appears, in the **Authentication method** dropdown, select **Role ARN**.
 
     Then copy the **Microsoft account ID** and **External ID** values that appear to a separate file, or have them handy for pasting into the relevant field in AWS. For example:
 
@@ -322,7 +322,7 @@ You'll need the name of your Amazon S3 bucket to copy it in to Microsoft Purview
 
 You'll need your AWS account ID to register your AWS account as a Microsoft Purview data source, together with all of its buckets.
 
-Your AWS account ID is the ID you use to log in to the AWS console. You can also find it once you're logged in on the IAM dashboard, on the left under the navigation options, and at the top, as the numerical part of your sign-in URL:
+Your AWS account ID is the ID you use to sign in to the AWS console. You can also find it once you're logged in on the IAM dashboard, on the left under the navigation options, and at the top, as the numerical part of your sign-in URL:
 
 For example:
 
diff --git a/articles/purview/register-scan-azure-files-storage-source.md b/articles/purview/register-scan-azure-files-storage-source.md
@@ -6,7 +6,7 @@ ms.author: shjia
 ms.service: purview
 ms.subservice: purview-data-map
 ms.topic: how-to
-ms.date: 11/02/2021
+ms.date: 02/14/2023
 ms.custom: template-how-to, ignite-fall-2021
 ---
 
@@ -52,11 +52,11 @@ Currently there's only one way to set up authentication for Azure file shares:
 
 When authentication method selected is **Account Key**, you need to get your access key and store in the key vault:
 
-1. Navigate to your storage account
-1. Select **Settings > Access keys**
+1. Navigate to your storage account 
+1. Select **Security + networking > Access keys**
 1. Copy your *key* and save it somewhere for the next steps
 1. Navigate to your key vault
-1. Select **Settings > Secrets**
+1. Select **Objects > Secrets**
 1. Select **+ Generate/Import** and enter the **Name** and **Value** as the *key* from your storage account
 1. Select **Create** to complete
 1. If your key vault isn't connected to Microsoft Purview yet, you will need to [create a new key vault connection](manage-credentials.md#create-azure-key-vaults-connections-in-your-microsoft-purview-account)
