A collection of 59 posts
Azure App Service Environments are expensive. You do get true network isolation and dedicated instances in which you can place behind custom WAF appliances. However, in many cases, many organizations can save on costs by using multi-tenant Azure app services....
You have to think about its usage patterns, how to will be accessible to other systems, what applications it will host, how it will be named, where it will be placed, how many resources to allocate them and what type,...
In Azure DevOps, it’s convenient and easy to use one of the hosted agent pools. Microsoft takes the time to update the tooling as new versions of the of SDKs come out - like .NET Core. But, there’s one drawback...
Azure just announced support for using Azure Application Gateways for ingress. It’s great because it creates more options than just using an NGNIX ingress controller or other in-cluster solutions. When creating ingress routes, they ought to be annotated so that...
Deploying Azure Resource Manager (ARM) templates from Azure DevOps is very powerful. It encourages developers and operators to maintain a declarative file describing the infrastructure on Azure. Also helps prevent pesky environment drifts because of someone clicking from the portal...