Govern multi-cloud sources with Azure Purview

This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Tech Community.

Do you store your organizational data in multiple clouds? Azure Purview offers a unified solution to discover and govern your organizational data residing across different clouds. You can now explore your data and discover sensitive data across your data estate, including both Azure storage services and Amazon S3 buckets, in one centralized place.

 

Main benefits:

  • Govern your data centrally—the Azure Purview Data Catalog and Data Insights reports display the scanning results of both Azure storage services and Amazon S3.
  • Consistent classification across clouds—Discovery of sensitive data across clouds is based on the same M365 sensitive information types. Your sensitive data stored in either Azure or AWS services will be classified in the exact same way.
  • Simple and easy configuration—Scanning data in a remote cloud is a fully managed service. The configuration is very easy, and you don’t need to deploy and maintain any agent or perform complex configurations in your AWS environment.

 

The Azure Purview roadmap includes additions for even more non-Azure storage services and aims to strengthen Azure Purview’s multi-cloud capabilities, empowering data administrators to maximize the value of their data with a single view across clouds.

 

Scanning data in a remote cloud

Azure Purview uses unique technology to classify data in AWS, including an easy setup and configuration process while complying with the highest Microsoft standards for data privacy:

  • The Azure Purview scanner is deployed in a Microsoft account in AWS.
  • Scans are initiated by a simple configuration in Azure Purview. Likewise, Azure storage scans are initiated and do not require manual service deployments or maintenance.
  • Service access to the organization’s S3 buckets is granted by a dedicated role in AWS.

OdedBergman_0-1635070709799.png

 

 

The Purview scanning setup ensures full data privacy by classifying Amazon S3 data locally in AWS. The classification service uses full data isolation and does not store any data in the Microsoft account in AWS. Only the classification results and metadata are sent to the Azure Purview data map, where it is displayed for administrators together with the classification results from Azure services.

 

Now, let’s get started:

  1. Configure Amazon S3 in Azure Purview

In a process similar to how to add Azure data sources in Purview, you first need to register the Amazon S3 bucket as a Purview data source, and then initiate your scan.

Registration

You can either register one Amazon S3 bucket for scanning a single bucket or register an AWS account for scanning all or selected S3 buckets in the account.

 

OdedBergman_1-1635070709813.png

 


Scanning

When setting up the scan of an Amazon S3 bucket or an AWS account, you need to provide the Purview scanner credentials to access the organization’s S3 buckets. To grant this access, you first need to create a role in AWS Identity and Access Management. This role requires read-only access to the S3 buckets you wish to scan. If the buckets are KMS-encrypted, a decrypt permission is needed as well.

To keep your buckets secure and ensure this new role can only be used for your Purview scanning, use these configurations when creating the role:  

  • Microsoft account ID­ - to allow accessing the buckets from a Microsoft-account only
  • External ID - a unique identifier for your Purview account used for accessing the bucket for an additional layer of security

You get both the Microsoft account ID and the external ID values when you create a Purview credential object. You’ll need to copy-paste them into the AWS Identity and Access Management role creation screens:

 

OdedBergman_6-1635071487941.png

 


Once the role is created in AWS, copy the role ARN value from AWS and paste it in the Purview credential object in the Purview portal. Then use the credential object to initiate a scan on your Amazon S3 bucket or AWS account.

  1. Let your data consumers discover your Amazon S3 data, along with Azure data, in the Azure Purview Data Catalog

OdedBergman_3-1635070709839.png

 

 

OdedBergman_4-1635070709850.png

 

 

  1. Get granular insights into sensitive data across multi-cloud sources

In the Azure Purview Data Insights reports, see a unified view of all scanned data, including Amazon S3.

 

OdedBergman_5-1635070709858.png

 

 

Get started today!

  • Quickly and easily create an Azure Preview account to try the generally available features.
  • Read documentation on how to use the Amazon S3 multi-cloud scanning connector for Azure Purview.

 

Leave a Reply

Your email address will not be published. Required fields are marked *

*

This site uses Akismet to reduce spam. Learn how your comment data is processed.