Blog

It's hard to believe that 2021 is done, and we're now in 2022. In one sense, it feels like a 'blink and you miss it' year. In another way, it feels as though it's been one of the longest years to have passed us by. It's fair to say that 2021 has had its challenges, not least in the backdrop of the ongoing COVID-19 pandemic. You may have caught my recent blog post on my mental health challenges. Practicing mindfulness and gratitude are excellent approaches for me to keep my overall mental health in balance. So, this post is just as much for me as anyone else. I want to highlight the achievements from the last year or so. I won't be setting any resolutions for 2021, but want to build upon what I've learned in 2021.

You will have noticed that there haven't been any updates on Cloud With Chris for some time. I've also been quiet on social media. For any of my colleagues, you may have seen that I've had time away from work by my out of office messages. In this blog post, I want to open up about my recent challenges and have an honest discussion. Whether you've experienced mental health challenges before, are currently going through tough times, or haven't experienced any and don't quite understand - I hope that me sharing this helps. We're going to be talking about mental health.

A little while ago, I wrote a blog post on Using the GitHub self-hosted runner and Azure Virtual Machines to login with a System Assigned Managed Identity, which seems to get a good amount of views week on week. Reflecting on some questions that have popped up this week (and regularly received over my time in the DevOps space), I thought that it makes sense to write a post on how to use Azure DevOps self-hosted agents to deploy to private resources. So, that's what we'll be covering in this post!

Migrating to the Cloud is more than just deciding which technology you want to adopt, or building out the appropriate architectures for your implementation. There is a significant amount of planning needed before you take your initial steps. For example, the initial migration process, establishing a foundation for your ongoing governance, and the wider management of expectations from your business, as well as establishing team structure and responsibilities. This is where the Azure Cloud Adoption Framework comes in.

This post is similar to another I recently wrote on using Branch Protection Rules in GitHub. Instead of focusing on GitHub, we'll be looking at how you can use Branch Policies in Azure DevOps (specifically, Azure Repos). If you're using Azure Repos, but not using Branch Policies - I'd encourage you to start using them! I hope this post helps you learn how!

In case you haven't heard, I'm planning to do some livestreams in the near future which are focused on live development / building in the cloud. I'm working on a few ideas, but if you have any suggestions - please throw them my way! To prepare for this, I've recently spent some time making sure my local development environment is in order. Windows Terminal and Windows Subsystem for Linux are a couple of the key tools in my local development environment. Windows Subsystem for Linux is the focus for this post.

If you're using GitHub as your source control provider, then I'd encourage you to using Branch Protection Rules if you're not already doing so! In this blog post, we'll cover what Branch Protection Rules are and how they can increase your code quality.

Azure Front Door - It's an Azure Service that has been generally available for quite some time. It went Generally Available (GA) in April of 2019 after being in Public Preview since September 2018. It's had several updates since, including a slew of Web Application Firewall enhancements, Rules Engine support and much more. But did you know Microsoft released the Azure Front Door Standard and Premium SKUs in preview in Feburary of 2021? So, what are they? How do they compare to the aforementioned Azure Front Door offering? And when would you want to think about using Azure Front Door compared with Azure CDN? We'll be covering all of those points in this post.

You'll have probably spotted by now that cloud architecture is a passion area of mine, and a regular topic that features on Cloud With Chris. We've talked a lot about Cloud Design Patterns and requirements-driven engineering in the past, as well as the various pillars of software quality. But one area that hasn't been explored too much is the Azure Well-Architected Framework. So in this blog post, we'll explore that, and identify how it can be used in your own projects.

Back in June, I wrote a blog post on API Management and how you can use API Management policies to enforce access restriction policies. I was going to write a follow up post on how to use API Management policies in additional scenarios, but it's one of those scenarios where great minds think alike!