Yesterday I was working with one of our customers to fix an issue with an ASP.NET application throwing an error. That application threw the error on the first request coming in through Azure Front Door. When we sent a request to the original (back end) URL, the application worked fine and never threw the exception. 🤔
This post is part of a series on Managed Identity. For an introduction, see Managed Identity – Part I. For a post that shows you how to connect your application to different types of Azure resources using Managed Identity see Managed Identity – Part II. Stay tuned for future posts.
Next week my colleague Daniël te Winkel and I will do a session at Techorama 2019 titled Getting sh*t done with Azure Functions (on AKS!). Or GSDwAF for short 🤓
We will talk about running Azure Functions in a Kubernetes deployment using Managed Identities and implementing Dependency Injection. And, even better, we’ll show you how!
Some time ago Oscar van Tol and I started creating video content for the community. We call them #Betatalks and create them because of two very important reasons:
We talk about a lot of developer stuff: from “Microsoft Build 2019 Highlights” in episode 1 to “C# 8, What’s new?” in episode 4.
This post is part of a series on Managed Identity. For an introduction, see Managed Identity – Part I. Stay tuned for future posts.
Elaborating on Part I, this blog post will show you how to connect your application to different types of Azure resources using Managed Identity.
This post is part of a series on Managed Identity. Stay tuned for future posts.
Connecting your application to a resource like Storage or a SQL database used to involve a connection string. This isn’t very secure. These settings are available through the Azure portal. So they might get compromised.
With the introduction of Azure Key Vault, we got a way of separating these secrets from our application configuration. We can store them in a safe, secure place. There’s only one downside: you need a connection string to connect to Key Vault. So the problem isn’t solved; we only moved it. We can still get to the connection string the application uses to get secrets from Key Vault. So anyone with access to that connection string can still access those same secrets.
Calling an API from a Logic App is pretty straightforward. You open up the Logic App Designer and add an HTTP Action. Specify the method to use and the URI you want to call and you’re good to go!
I am humbled and very proud to be awarded a Microsoft Azure MVP award today. A big “thank you” to all who helped me get here. 🙏🏻
A special thank you to my employer Betabit who supports me putting lots of effort into the community and helps organize or sponsor events.
It’s strange but very cool to see social media ’explode’ (at least according to my standards) after my announcement. But I’m still just Rick, a guy who loves to do fun things with code, in the cloud.
Last week one of my colleagues had a question: Is there a performance penalty when you add multiple Azure Blob storage bindings in an Azure Function? Or is the connection only established when you access one of those blobs? Answering this grew into a way to have Dynamic output bindings in Azure Functions.
To start things off: yes. There’s some pretty decent documentation on all the available Triggers & Bindings in Azure Functions. Like this overview page. And you can also find documentation on specific bindings, like the Service Bus Binding. Nevertheless, I wanted to add to that documentation with some simple, real-world examples using triggers & bindings. So here goes.
While trying to publish an NPM package to our artifacts registry in Azure DevOps, we got an error:
This Thursday December 6th I’ll be speaking at Azure Thursday - December 2018. The last of the regular Azure Thursdays this year.
This is a group for all developers, consultants, architects and IT professionals who want to dive into for them unknown topics related to Azure. Azure Thursday are happening every first Thursday of the month and the format will be different every evening. From hand-on workshops to technical talks.
Azure Thursdays