Skip to main content

Get back to work using Azure Health Bot

For the past year and half, Covid-19 pandemic has forced most of the companies to allow their employees to work from home. However, now that vaccines are available, companies are looking for a way to get their employees back to office safely. Most of the organizations are creating some kind of app which will capture employee health information safely and allow them to get approve/deny an employee's return to office. But what if instead of rolling out your own platform, you could leverage the full power of Azure with almost no code and also ensure full compliance with health data regulations. Meet Azure Health Bot.

Azure Health Bot is an Azure Marketplace offering by Microsoft built on top of Microsoft Bot Platform. It provides features like drag/drop editor, authentication with OAuth providers, generating reports and managing user information. It also integrates with existing chat apps like WhatsApp, Telegram, Facebook Messenger etc. so that users don't have to install a new app just to use it.

To get started, create a new Azure Health Bot using Azure Portal. There is Free Plan for dev and test purposes too. Once the bot is created, go to the management URL provided by it and create or import a scenario.


Here I will import a scenario "Back to Work". You can select others as per your requirement.


Once imported, you can start editing the scenario in the editor or Run it to start testing it in the browser itself.


Here I have interacted with the bot and it cleared me to get back to office! 😀


Once your users start using your bot, you can generate reports out of it for reporting/compliance purposes.


Give it a try and get back to work!

Comments

Popular posts from this blog

Integrating React with SonarQube using Azure DevOps Pipelines

In the world of automation, code quality is of paramount importance. SonarQube and Azure DevOps are two tools which solve this problem in a continuous and automated way. They play well for a majority of languages and frameworks. However, to make the integration work for React applications still remains a challenge. In this post we will explore how we can integrate a React application to SonarQube using Azure DevOps pipelines to continuously build and assess code quality. Creating the React Application Let's start at the beginning. We will use npx to create a Typescript based React app. Why Typescript? I find it easier to work and more maintainable owing to its strongly-typed behavior. You can very well follow this guide for jsx based applications too. We will use the fantastic Create-React-App (CRA) tool to create a React application called ' sonar-azuredevops-app '. > npx create-react-app sonar-azuredevops-app --template typescript Once the project creation is done, we

Centralized Configuration for .NET Core using Azure Cosmos DB and Narad

We are living in a micro services world. All these services are generally hosted in Docker container which are ephemeral. Moreover these service need to start themselves up, talk to each other, etc. All this needs configuration and there are many commercially available configuration providers like Spring Cloud Config Server, Consul etc. These are excellent tools which provide a lot more functionality than just storing configuration data. However all these have a weakness - they have a single point of failure - their storage mechanism be it a file system, database etc. There are ways to work around those but if you want a really simple place to store configuration values and at the same time make it highly available, with guaranteed global availability and millisecond reads, what can be a better tool than Azure Cosmos DB! So I set forth on this journey for ASP.NET Core projects to talk to Cosmos DB to retrieve their configuration data. For inspiration I looked at Steeltoe Con

Add Git Commit Hash and Build Number to a Static React Website using Azure DevOps

While working on a React based static website recently, there was a need to see exactly what was deployed in the Dev/Test environments to reduce confusion amongst teams. I wanted to show something like this: A quick look at the site's footer should show the Git Commit Hash and Build Number which was deployed and click through to actual commits and build results. Let's see how we achieved this using Azure DevOps. Git Commit Hash Azure DevOps exposes a variable called  $(Build.SourceVersion) which contains the hash of the commit. So I defined a variable in the Build Pipeline using it. Build Id and Build Number Azure DevOps also exposes two release time variables  $(Build.BuildId) and  $(Build.BuildNumber) which can be used to define custom variables in the pipeline. So we have a total of 3 variables defined: Next we use these variables in our React App. I created 3 global variables in index.html and assigned a token value to them. < script   type = "text/JavaScript&quo