To configure your environment, you need certain prerequisites in place:
A Microsoft Azure subscription. To use Azure services, including Event Hubs, you need an Azure subscription. If you don't have an Azure account, you can sign up for a free trial or use your MSDN subscriber benefits when you create an account.
If your Microsoft Purview account was created before December 15th, 2022 you may have a managed Event Hubs resource already associated with your account.
You can check in Managed Resources under settings on your Microsoft Purview account page in the Azure portal.
If you do not see this resource, or it is disabled, follow the steps below to configure your Event Hubs.
If it is enabled, you can continue to use this managed Event Hubs namespace if you prefer. (There is associated cost. See see the pricing page.) If you want to manage your own Event Hubs account, you must first disable this feature and follow the steps below.
If you disable the managed Event Hubs resource you won't be able to re-enable a managed Event Hub resource. You will only be able to configure your own Event Hubs.
Bring your own Event Hubs namespace
You can configure an existing Azure Event Hubs namespace with an Event Hubs or create a new one to connect with Microsoft Purview.
Event Hubs permissions
To authenticate with your Event Hubs, you can either use:
Microsoft Purview managed identity(Recommended)
User assigned managed identity - only available when configuring namespaces after account creation and if using Event Hubs with an open network.
These identities will need at least contributor permissions on your Event Hubs to be able to configure them to use with Microsoft Purview.
Your Event Hubs workspace network needs to be configured in one of two ways:
Public network access set to Selected networks or Disabled, Allow trusted Microsoft services to bypass this firewall set to Yes, and using the Microsoft Purview managed identity to authenticate.
Public network access set to All networks and using the Microsoft Purview managed identity or a user assigned managed identity to authenticate.
Microsoft Purview's status as a trusted service means that, as long as Allow trusted Microsoft services to bypass this firewall is set to Yes on your Event Hubs resource, your hooks can still receive messages from Event Hubs.
Configure Event Hubs to publish messages to Microsoft Purview
Navigate to Kafka configuration under settings on your Microsoft Purview account page in the Azure portal.
Select Add configuration and Hook configuration.
Note
You can add as many hook configurations as you need.
Give a name to your hook configuration, select your subscription, an existing Event Hubs namespace, an existing Event Hubs to send the notifications to, the consumer group you want to use, and the kind of authentication you would like to use.
Tip
You can use the same Event Hubs namespace more than once, but each configuration will need its own Event Hubs.
Select Save. It will take a couple minutes for your configuration to complete.
Configure Event Hubs to receive messages from Microsoft Purview
Navigate to Kafka configuration under settings on your Microsoft Purview account page in the Azure portal.
If there's a configuration already listed as type Notification, Event Hubs is already configured, and you can begin the steps to receive Microsoft Purview messages.
Note
Only one Notification Event Hubs can be configured at a time.
If there isn't a Notification configuration already listed, select Add configuration and Notification configuration.
Give a name to your notification configuration, select your subscription, an existing Event Hubs namespace, an existing Event Hubs to send the notifications to, the partitions you want to use, and the kind of authentication you would like to use.
Tip
You can use the same Event Hubs namespace more than once, but each configuration will need its own Event Hubs.
Select Save. It will take a couple minutes for your configuration to complete.
Learn to use Azure Event Hubs to reliably process high-volume data streams to enable you to code applications to send and receive messages through the hub.
Data policies enable customers to manage access to different data systems across their entire data estate, all from a central location - Microsoft Purview. Workflow is a capability within Microsoft Purview that enables customers to orchestrate various operations, such as adding glossary terms or approval of data access request using repeatable business processes. In this episode of Data Exposed with Anna Hoffman, Blesson John, and Naga Yenamamdra, we are demoing a capability that combines the power of workf