For AAD authentication to Event hubs, the sender will need to fetch a token from Azure Active directory and then use it as authentication to send messages to Eventhub.
There are 3 ways a sender can send a message to an Eventhub.
Most of you may already be aware of how to register an app/service principal in Azure Active directory. Once the app is registered, it can be used to authenticate against AAD and get access to Azure resources. For those of you need a refresher, you can refer to this LINK.
The documentation talks of 2 way to authenticate on AAD.
Most of the cases, I’ve seen people using the 1st method because it is easier. The secret is just a random string which is shared with the client. If this along with the other…
I was just exploring of ways to load balance a http API hosted on Azure functions. Hopefully with the solution, this would provide high availability as well. What I’m talking about is can how can we setup our functions in 2 paired regions so that data is distributed amongst them? Also, if one region goes down, I would like all requests to be routed to the remaining function. Obviously this means I need 2 function apps setup in 2 regions. But I do need something else for the load balancing and health probes.
We had a requirement recently of implementing queue logic to allow for loose coupling. As part of that research, I did some testing on how we could use Service bus for this and thought I can share what I have discovered.
Service bus is one of the queue PaaS services available on Azure. It comes in 3 tiers : basic, standard and premium. Some good initial reading about what a service bus is can be found here https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-messaging-overview
Pricing and functionality of the different tiers can be found here : https://azure.microsoft.com/en-in/pricing/details/service-bus/
For today’s demo, we will use a…
As some of you may already know, Azure functions is a serverless service which can be used to expose APIs to do certain tasks. Today we are going to cover an example of fetching data from an Azure SQL using an Azure function API. But you can use the API to pretty much do any CRUD operations on the DB with some minor tweaks. We will use Postman to trigger our API. A high level diagram of our setup is below.
For starters, let’s create our SQL DB.
Sign in to the Azure portal with your Azure account credentials.
Today we are going to be talking about securing your function app API using Azure active directory(AAD).
Recently as part of a business request, we were required to host an API on Azure. We decided to host the API using Azure functions. As you may already know, we can secure the function API using API keys(by setting the authorization to “function” level) but today we will cover how to secure your function API using oAuth (via AAD). This means, to call our API, we will first need to call a token endpoint to retrieve a token. Then using…
Queue triggered Function with Cosmos DB output binding
Let’s talk about serverless!!
What is serverless? Well it’s definitely not “No Servers!” that’s for sure. It just means the person using the service does not have to bother about the deployment and support of the servers. The servers actually still exist somewhere but Microsoft takes care of the provisioning for you.
Today we are going to use Azure functions that are going to be triggered by a storage queue and write the message into a Cosmos DB container. For this demo we will be doing nearly everything on the portal using…
In this little demo, we are going to use 1 azure logic app to encrypt some data using keys in our key vault and then push that encrypted data out to dynamic endpoints. These endpoints will be determined by the data in the body of the http API request which we will use to trigger the flow.
Below is a visual representation of what we will try to achieve.
My business use case was to push data out near real time to various endpoints. Creating separate static connections seemed like overkill and wasn’t a very flexible option. …