[ad_1]
Microsoft announced the public preview of Azure Data Share, which offers features to share data with users in its own organization, as well as with other organizations. For the most part, Microsoft is positioning the newly announced service as a Big Data tool, although it is also possible to share individual files.
Traditionally, data exchange between organizations often included tools such as FTP, email or OneDrive. However, this does not always meet the requirements in a business environment, as Sam Cogan, Solution Architect, and Microsoft Azure MVP explain.
This can be problematic when you use very large data sets and often goes against the company's security policies. The use of these tools also makes it painful to update the data. By using Data Share, you can quickly make the data available to other Azure users without having to copy them anywhere.
The Azure Data Share service provides its capabilities as a PaaS option, eliminating the need to deploy an infrastructure. The data sharing configuration is done entirely via the configuration, without writing any code. In addition, two options are currently available for data sources, Azure Blob Storage and Azure Data Lake Storage (Gen 1 and 2), with more choices expected as the service moves to general availability. Shared data is, by default, a snapshot of the data as it was when the share was created. However, the ability to configure incremental data updates is also available, allowing you to renew data every hour or every day. There is also the ability to revoke access to shared data subscriptions; although this does not remove the remote data, it simply ensures that it no longer receives updates.
Source: https://docs.microsoft.com/en-us/azure/data-share/how-tokerevoke-share-subscription
It is important to note that data sharing is only possible between Azure subscriptions and that the receiving party must have write permissions to the storage account containing the information. Seeing how Azure Data Share is built on Azure, the service leverages the built-in security features of the platform, such as in-transit or inactive data encryption, if the data store supports it. In addition, it uses RBAC features to define service access and leverages managed service identities to access the underlying datastore.
Additional monitoring is added by Azure Data Share, such as invitation statuses and snapshot history. According to Charbel Nemnom, Cloud Architect and Microsoft MVP, using these features simplifies the process of sharing data with partners.
Azure Data Share aims to simplify this process and to have a single pane of data to meet all your data sharing needs. So, instead of losing track of those with whom you shared data? What did you share? When you shared it, and things like that. This aims to be these one-stop shops for customers, data sharing needs.
To start with Azure Data Share, you must create an account and create a data share, which is shared with the recipients. The next step is to add datasets from the source services to the data share and optionally add an update schedule. The recipient receives an email with an invitation, which allows them to access the share and link it to their storage account in their Azure tenant.
[ad_2]
Source link
