Near-real-time data sharing with Azure Data Explorer and Azure Data Share (preview)

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

We are excited to announce the limited public preview of in-place data sharing with Azure Data Explorer and Azure Data Share! This integration will allow you to share your data with your internal teams and external partners or customers - without the data movement and in near-real-time! Click here to sign-up!


Azure Data Explorer is a fast, fully managed, data analytics service. It offers real-time analysis on large volumes of data that stream from many sources, such as applications, websites, and IoT devices.


Azure Data Share enables organizations to simply and securely share data with multiple customers and partners. In just a few clicks, you can provision a new data share account, add datasets, and invite your customers and partners to share your data. Azure Data Share makes it simple to manage and monitor what data was shared, when, and by whom.


In today's world, data is viewed as a key strategic asset that many organizations need to simply and securely share with their customers and partners. There are many ways to share data such as through FTP, e-mail, and APIs. This requires both parties to build and maintain the data pipeline that moves data between teams and organizations. With Azure Data Explorer, customers can easily and securely share their data with their customers and partners by managing the share via Azure Data Share. There is no need to build or maintain a data pipeline. Both parties must have their own Azure Data Explorer cluster and use Azure Data Share to send an invitation and manage the sharing relationship. When the sharing relationship is established, Azure Data Share creates a symbolic link between the provider and consumer's Azure Data Explorer cluster. When the data provider revokes access, the symbolic link is deleted, and the shared database(s) are no longer available to the data consumer.


The data provider can share the data at the database level or at the cluster level. The cluster sharing the database is the leader cluster and the cluster receiving the share is the follower cluster. A follower cluster can follow one or more leader cluster databases. The follower cluster periodically synchronizes to check for changes. The lag time between the leader and follower varies from a few seconds to a few minutes, depending on the overall size of the metadata. The data is cached on the consumer cluster and is only available for read or query operations, with an exception to override the hot caching policy and the database principals. The queries running on the follower cluster does not uses the resources of the leader cluster.


Typical Use Cases

  1. Data providers can use this integration to share their data with their customers in a simple and secure way. For example, a weather forecast data provider can share their data in near-real-time with their customer without having to maintain the data pipeline. As the data is updated on the leader cluster, the change will appear on the follower cluster within a few seconds or minutes depending the data volume and metadata. The data consumers can then easily join the weather data with their business data to enrich their datasets.
  2. Organizations can share their data with partners for collaboration and data exchange. For example, a retail company sharing data with their suppliers.
  3. Share data within the company or provide data-as-a-service. Many organizations would like to share the data within the company and have individual teams accountable for their usage and cost. With Azure Data Explorer, every team share the same data from one leader cluster but have their own cluster with their choice of configuration.

This feature is currently in preview. Please submit a request here to sign-up for the preview.

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.