-
Using Azure Functions to integrate with Dataverse (Azure Functions V4 and Dataverse Client with MSAL)
Power Automate can handle an incredible range of scenarios but sometimes you may need to do something more complex. Sometimes your organisation won’t allow the use of certain features or purchasing of third party power automate task. When Power Automate falls short there is always azure functions as an option. You can even write an… — read more
-
logic Apps temp solution for Form Recognizer 3.0
UPDATE: Look like the adaptors for Form Recognizer 3.0 are now available. More details here: Form Recognizer – Connectors | Microsoft Learn. I’ve posted a quick update here: Azure Logic Apps with Form Recognizer version 3.0 – Bruno Lucas Azure Blog Form Recognizer Studio allows users to train models to analyze forms and extract fields… — read more
-
Apache Kafka bindings for Azure Functions
I was currently looking for a way to listen to Kafka topics direct from Azure Functions when I found the Kafka bindings are now available for Azure Functions v3+ hosted on Elastic Premium Plan and Dedicated (App Service) plan. The trigger has been available for preview for a while, but now it is suitable for production: Apache Kafka… — read more
-
Azure Key Vault Secret client library vs Azure Key Vault Reference
When you code an App Service or Azure Function, Azure Key Vault Reference is a great way to improve security and avoid problems like redeploying code to pick up new service secret keys. All you need is this simple syntax to retrieve a key secret: @Microsoft.KeyVault(SecretUri=https://myvault.vault.azure.net/secrets/mysecret/) But Azure Key Vault Reference is for App Service… — read more
-
Sending Adaptive Card to Multiple Recipients using Logic Apps
Before starting, you may have seen this posted around many blogs. I decided to write an updated post after finding most of the solutions mentioned around are using a Team action that is no longer available: “Post an adaptive card to a Teams user and wait for a response.” We will follow the same approach… — read more
-
Terraform and Azure Vault – Create secrets, store them in the Vault, and invoke it in Azure Functions.
Scenario Development challenge Solution To eliminate those problems, speedup development and increase security: The Terraform Code We start by creating the vault (#1). With the vault created we can now create resources that require access keys\connection strings (#2) and store the secret in the vault (#3) The azure hub and many other resources don’t force… — read more
-
Terraform and Azure Vault – Create secrets, store them in the Vault and invoke it in Azure Functions.
The path to complete automation and the end of sharing secrets through unsafe channels. Renew Secrets whenever you need without breaking environments or manually updating config files Azure Key Vault reference is pretty popular around the world but there are still a lot of Azure developers adding secrets to config files or Devops secret variables.… — read more
-
Getting Started with Azure Terraform from scratch – Install Dev tools and run your first script.
Last year I had the opportunity to spend quite a bit of time working with Terraform. For my surprise it was simpler than I expected. If you never used Terraform and have been dwelling with ARM templates, CLI and PowerShell, I highly recommend to give it a try. Azure Terraform is not hard to learn… — read more
-
Getting Started with Azure Event Hub and IOT Hub Triggers using Visual Studio 2019
After seeing quite a few questions regarding writing code for Azure Event Hub on the forums, I thought would be a good time to write a post to share my experience and help whoever is getting started… or getting stuck. Developing code locally with Visual Studio depends on the emulator for debugging and sometimes that… — read more
-
Azure Event Hub error: “An attempt was made to access a socket in a way forbidden by its access permissions”
If you are working on an azure function with a trigger for event hub or service bus and notice this error when debugging locally, the cause is very likely that your machine or network has blocked the TCP ports 5671 and 5672. “Azure Service Bus or Azure Event Hubs requires the use of TLS at all… — read more