In the Setting up an Azure Service Bus endpoint recipe earlier in this chapter, we used built-in plugin capabilities to write a plugin context to an Azure Service Bus queue when a specific event is triggered (update of a specific field).

We can also use this same capability to also trigger an event when records are read, effectively creating a read audit notification/log.

In this recipe we will configure a read plugin step to write its context to an Azure Service Bus queue. We'll then create a listener that will gather the user GUID, the entity name and the entity GUID of the record read, and store those values in a NoSQL Azure Cosmos DB (previously known as Document DB) database in the JSON format: