In the previous post I described the approach to remove specific ExpressRoute VirtualNetworkGateway connections, solely using the PowerShell basic commands. As mentioned, that did not serve our purpose.

Recently I was working on an assignment, that at the start seemed like an easy one. We had to redeploy ExpressRoute Circuit which required that we first remove all the connections towards that Circuit. An important thing to mention is that all is done via Azure DevOps release pipelines and that the parameter we had to use is the circuit name.

Lately I came accross a lot of unsecurity and even knowledge lack about how to secure your Azure networking communication. Based on the example I will showcase you differences between no security and using Service or Private Endpoints.

Providing good billing overview and reports for customers through CSP is still not fully integrated in either MSP or Azure portal. That’s why most providers use 3rd party solutions. Browsing through one of those for a client I noticed strange reports for a month or two. We implemented Azure SQL with Elastic Pool. Great thing with EP is that you pay just for selected DTU and you may create “unlimited” number of databases. But, if you create a new database and don’t add it to the pool, it will be billed separately.

Hopefully you didn’t recognize yourself in my previous post. After we cooled off our heads we started thinking about the solution/workaround because, once again, client was not yet ready to invest in HA solution.

For the past 8 months I’ve been working on an Azure project for a financial institution. I’ve never imagined so many security and compliancy checks. The team did a great job - we passed all advisory scans with high grades and were ready to go live in a couple of days.

Important part of the infrastructure was relying on Azure SQL. Monday morning. I’ve made myself a cup of coffee and logged in to the portal and systems to do a base check once again. And this is where our story begins.