Adobe Experience Platform Launch has been rebranded as a suite of data collection technologies in Adobe Experience Platform. Several terminology changes have rolled out across the product documentation as a result. Please refer to the following document for a consolidated reference of the terminology changes.
In Microsoft Azure, Event Hubs is a highly scalable, real-time data ingress service that allows you to process and analyze the massive amounts of data produced by your connected devices and applications. Once data is collected into an event hub, it can be transformed and stored using any real-time analytics provider or batching/storage adapters.
The Microsoft Azure event forwarding extension leverages Event Hubs to send events from the Adobe Experience Platform Edge Network to Azure for further processing. This guide covers how to install the extension and employ its capabilities in an event forwarding rule.
In order to use this extension, you must have a valid Azure account with access to Event Hubs. You must also create an event hub using the Azure portal before following the steps below.
To install the Microsoft Azure extension, navigate to the Data Collection UI or Experience Platform UI and select Event Forwarding from the left navigation. From here, select a property to add the extension to, or create a new property instead.
Once you have selected or created the desired property, select Extensions in the left navigation, then select the Catalog tab. Search for the Microsoft Azure card, then select Install.
Since the extension does not have any configuration properties, it is immediately added to the list of installed extensions. You can now start using Event Hub action types when configuring event forwarding rules.
Start creating a new event forwarding rule and configure its conditions as desired. When selecting the actions for the rule, select Microsoft Azure for the extension, then select Send Data to Event Hubs for action type.
The right panel updates to show configuration options for how the data should be sent. Specifically, you must assign data elements to the various properties that represent your Event Hub configuration.
Event Hub Details
|The name of the Event Hubs namespace that you created when setting up the event hub.
|The name of the event hub.
|SAS Authorization Rule Name
|The name of the shared access authorization rule for your entire Event Hubs namespace or the specific event hub instance that you want to send data to. See the appendix section on obtaining SAS authorization values for more information.
|SAS Access Key
|The primary key of the shared access authorization rule for your entire Event Hubs namespace or the specific event hub instance that you want to send data to. See the appendix section on obtaining SAS authorization values for more information.
|Event Hubs allows you to send events directly to specific partitions. To leverage this feature, provide the ID of the partition that you want to receive the events.
|This field contains the data that will be forwarded to the Event Hubs. The data can be a JSON object, a string, or a data element.
When finished, select Keep Changes to add the action to the rule configuration. When you are satisfied with the rule, select Save to Library.
Finally, publish a new event forwarding build to enable the changes to the library.
This guide covered how to send data to Event Hubs using the Microsoft Azure event forwarding extension. For more information on event forwarding capabilities in Experience Platform, refer to the event forwarding overview.
External applications are granted access to Event Hubs through shared access signatures (SAS). Each Event Hubs namespace and event hub instance has a default SAS authorization rule automatically assigned on creation, but you can also create additional policies for each resource if you wish.
When configuring an event forwarding rule using the Azure extension, you must provide the name and the primary key for the authorization rule governing the namespace or specific event hub you want to send data to. For details on how to obtain these values from the Azure portal, refer to the following sections in the Azure documentation:
Once you have the required values, the authorization rule name can be provided directly as a string in the config input or you can create a string-type data element to reference it instead. The primary key, however, must first be contained inside of an event forwarding secret before it can be supplied in the rule configuration in order to protect your data security.
Within the event forwarding UI, create a new secret and select Token as the secret type. For the token value itself, provide the primary key you copied earlier. After creating the secret, create a data element with the type Secret and select the Event Hubs secret from the list. Once the secret data element has been set up, you can reference that data element in the SAS Access Key field.