Reviewing Audit Trails for Azure Health Bot

The Azure Health Bot Services allows us to build a bot with a predefined set of data and build bots. With the power of Azure Platform, you can expand the chatbot across several channels, including Web, Desktop, integrate with Whatsapp, Microsoft Team, or any other external interface using Directline APIs. Microsoft Azure Health Bot abstracted out the complex part including several data validation, regulation, and data privacy. It provided an opportunity for the organization to build and deploy an AI-based, compliant bot for real healthcare use cases. Of course, at scale and rapidly. However, Audit Trial is a key aspect for the security as well as compliance perspective for any digital health application. The system must capture the changes happening with the application by any creation, modification, delete, or other operations. When it comes to Azure Helath Both, it has a detailed log for Audit Trails. In this post, let us check how we can review the Audit Trails for Azure Health Bot.

Must Read:

Reviewing Audit Trails for Azure Health Bot

Following are the scenarios covers as part of the Audit Trails: Creating, Modifying, Deleting, Activating, Deactivating, and Importing a scenario. You can view the Audit Trials by navigating to Azure Helath Bot Management Portal and then selecting user.

Select the “Audit Trails”, it will navigate to Audit Trails details page.

Any transaction related with Creating, Modifying, Deleting, Activating, Deactivating, and Importing a scenario, logs here as Audiot Trails for the Azure Health Bot.