These tips and tricks offer valuable insights on how to effectively manage and utilize input parameters during Azure Bicep deployment.
When you start thinking about moving your workload to the cloud, your first concern is security. In the following post, I’d like to summarize what you can do to reduce risk and protect workloads deployed in Azure.
Every Azure Function instance requires to have a Azure Storage Account for storing sensitive data – sometimes even source code of functions. Out of the box, this storage has enabled public endpoint. With PrivateLink, you can add an extra layer of protection.
If you manage many AWS accounts in an enterprise environment, you probably feel the need for better user management and federate it with IdP (in my case with Azure Active Directory). In 2017 AWS has introduced a new way how to federate access – with an AWS SSO service. In this post, I would like to describe some properties of the solution you need to count on.
In case you want to send HTML content as HTTP response directly from .NET Azure Functions, you can use following code snippet to reduce your work.