Setup:- .NET 6.0 - In-process/isolated v4 function apps - Consumption plan - Managed Identity BackgroundPreviously, I wrote a blog post "Azure Function secretless access to Azure Service Bus using Managed Identity", which describes how to use ServiceBusTriggers in an Azure function
Traditionally, the connection string to the Azure SQL database contains both username and password. Even if you store these credentials in KeyVault, a password needs maintenance/rotation and it might end up in the wrong hands (for instance if sloppy developers keep the password
I recently wrote a post where I did some exploring into managed identity for Azure app services. I showed how to get an access token, but only briefly mentioned the Microsoft.Azure.Services.AppAuthentication package, and said nothing about how to write .NET Core
Quite often we want to give an app service access to resources such as a database, a keyvault or a service bus. We used to do this by configuring the app service with secrets that enabled the application to access these protected resources. However,
