Skip to content

Commit 9b3e616

Browse files
committed
Edits
1 parent 3769ac2 commit 9b3e616

File tree

1 file changed

+13
-12
lines changed

1 file changed

+13
-12
lines changed

articles/purview/scan-data-sources.md

Lines changed: 13 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -11,9 +11,9 @@ ms.date: 01/25/2023
1111

1212
# Scan data sources in Microsoft Purview
1313

14-
In Microsoft Purview, after you [register a data source](manage-data-sources.md#register-a-new-source) your data source, you can scan your source to import metadata about the information stored in that source, and apply any classifications to sensitive data.
14+
In Microsoft Purview, after you [register your data source](manage-data-sources.md#register-a-new-source), you can scan your source to capture technical metadata, extract schema, and apply classifications to your data.
1515

16-
* For more information about scanning in general, see our [scanning concept article](concept-scans-and-ingestion.md)
16+
* For more information about scanning in general, see our [scanning concept article](concept-scans-and-ingestion.md).
1717
* For best practices, see our [scanning best practices article.](concept-best-practices-scanning.md)
1818

1919
In this article, you'll learn the basic steps for scanning any data source.
@@ -28,18 +28,18 @@ In this article, you'll learn the basic steps for scanning any data source.
2828
Before you can scan your data source, you must take these steps:
2929

3030
1. [Register your data source](manage-data-sources.md#register-a-new-source) - This essentially gives Microsoft Purview the address of your data source, and maps it to a [collection](catalog-permissions.md#a-collections-example) in the Microsoft Purview Data Map.
31-
1. Consider your network - If your source is on an on-premises network, or a virtual private network (VPN), or if your [Microsoft Purview account is using private endpoints](catalog-private-link-end-to-end.md), you'll need a self-hosted integration runtime, which is a tool that will sit on a machine in your private network so your source and Microsoft Purview can connect during the scan. [Here are the instructions to create a self-hosted integration runtime.](manage-integration-runtimes.md)
31+
1. Consider your network - If your source is in an on-premises network, or a virtual private network (VPN), or if your [Microsoft Purview account is using private endpoints](catalog-private-link-end-to-end.md), you'll need a self-hosted integration runtime, which is a tool that will sit on a machine in your private network so your source and Microsoft Purview can connect during the scan. [Here are the instructions to create a self-hosted integration runtime.](manage-integration-runtimes.md)
3232
1. Consider what credentials you're going to use to connect to your source. All [source pages](microsoft-purview-connector-overview.md) will have a **Scan** section that will include details about what authentication types are available.
3333

34-
## Creating a scan
34+
## Create a scan
3535

3636
In the steps below we'll be using [Azure Blob Storage](register-scan-azure-blob-storage-source.md) as an example, and authenticating with the Microsoft Purview Managed Identity.
3737

3838
>[!IMPORTANT]
3939
> These are the general steps for creating a scan, but you should refer to [the source page](microsoft-purview-connector-overview.md) for source-specific prerequistes and scanning instructions.
4040
4141

42-
1. In the [Azure portal](https://portal.azure.com), open your **Microsoft Purview account** and select the **Open Microsoft Purview governance portal**.
42+
1. In the [Azure portal](https://portal.azure.com), open your **Microsoft Purview account** and select the **Open Microsoft Purview governance portal** button.
4343

4444
:::image type="content" source="./media/scan-data-sources/open-purview-studio.png" alt-text="Screenshot of Microsoft Purview window in Azure portal, with the Microsoft Purview governance portal button highlighted." border="true":::
4545

@@ -50,12 +50,13 @@ In the steps below we'll be using [Azure Blob Storage](register-scan-azure-blob-
5050

5151
1. Provide a **Name** for the scan.
5252
1. Select your authentication method. Here we chose the Purview MSI (managed identity.)
53-
1. Choose the current collection, or a sub collection for the scan. The collection you choose will house the metadata discovered during the scan.
54-
55-
1. Select **Test connection**. If it isn't successful, see our [troubleshooting] section. On a successful connection, select **Continue**
5653

5754
:::image type="content" source="media/scan-data-sources/register-blob-managed-identity.png" alt-text="Screenshot that shows the managed identity option to run the scan":::
5855

56+
1. Choose the current collection, or a sub collection for the scan. The collection you choose will house the metadata discovered during the scan.
57+
58+
1. Select **Test connection**. If it isn't successful, see our [troubleshooting] section. On a successful connection, select **Continue**.
59+
5960
1. Depending on the source, you can scope your scan to a specific subset of data. For Azure Blob Storage, we can select folders and subfolders by choosing the appropriate items in the list.
6061

6162
:::image type="content" source="media/scan-data-sources/register-blob-scope-scan.png" alt-text="Scope your scan":::
@@ -72,7 +73,7 @@ In the steps below we'll be using [Azure Blob Storage](register-scan-azure-blob-
7273

7374
:::image type="content" source="media/scan-data-sources/register-blob-review-scan.png" alt-text="review scan":::
7475

75-
## Viewing Scan
76+
## View a scan
7677

7778
Depending on the amount of data in your data source, a scan can take some time to run, so here's how you can check on progress and see results when the scan is complete.
7879

@@ -90,7 +91,7 @@ Depending on the amount of data in your data source, a scan can take some time t
9091

9192
:::image type="content" source="media/scan-data-sources/register-blob-scan-completed.png" alt-text="view scan completed":::
9293

93-
## Managing Scan
94+
## Manage a scan
9495

9596
After a scan is complete, it can be managed or run again.
9697

@@ -102,7 +103,7 @@ After a scan is complete, it can be managed or run again.
102103

103104
:::image type="content" source="media/scan-data-sources/register-blob-manage-scan-options.png" alt-text="manage scan options":::
104105

105-
1. You can _run an incremental scan_ or a _full scan_ again.
106+
1. You can run a full scan, which will scan all the content in your scope, but some sources also have **incremental scan** available. Incremental scan will scan only those resources that have been updated since the last scan. Check the **supported capabilities** table in your source page to see if incremental scan is available for your source after the first scan.
106107

107108
:::image type="content" source="media/scan-data-sources/register-blob-full-inc-scan.png" alt-text="full or incremental scan":::
108109

@@ -112,7 +113,7 @@ Setting up the connection for your scan can complex since it's a custom set up f
112113

113114
If you're unable to connect to your source, follow these steps:
114115

115-
1. Review your [source page](microsoft-purview-connector-overview.md)prerequisites to make sure there's nothing you've missed.
116+
1. Review your [source page](microsoft-purview-connector-overview.md) prerequisites to make sure there's nothing you've missed.
116117
1. Review your authentication option in the **Scan** section of your source page to confirm you have set up the authentication method correctly.
117118
1. Review our [troubleshoot connections page](troubleshoot-connections.md).
118119
1. [Create a support request](../azure-portal/supportability/how-to-create-azure-support-request.md#go-to-help--support-from-the-global-header), so our support team can help you troubleshoot your specific environment.

0 commit comments

Comments
 (0)