Happy Friday! In addition to the great community content this week, I'd like to highlight a new learning path on Microsoft Learn. This learning path can help you ramp up on ARM templates.
The video should help provide you with a great start on using this service with your Azure Web App Service. Utilizing resources like GitHub actions can help you on your journey to becoming a Microsoft DevOps Certified Expert.
Testing - it's an important part of a developer's day-to-day, but it's also crucial to the operations engineer. In a world where DevOps is more than just a buzzword, where it's become accepted as a mindset shift and culture change, we *all* need to consider running quality tests.
Happy Friday! I've been on vacation this week, but I found some enjoyable reading thanks to you wonderful folks. Some CI/CD with containers and a few tips and tricks posts will carry you through the weekend.
Infrastructure as Code (IaC) is the management of infrastructure (networks, virtual machines, load balancers, and connection topology) in a descriptive model, using the same versioning as DevOps team uses for source code. This blog post looks at two IaC options to use for Microsoft Azure.
The pull request workflow in Static Web Apps is super cool, but that only works for Static Web Apps and GitHub Actions.. This blog post walks you through how to implement the same PR workflow for Azure App Service using Azure DevOps
As part of our quarterly update, we’d like to share with you some of the highlights from the previous quarter and discuss what we have planned for this upcoming one. Each of the highlighted features includes a link to our public roadmap project where you'll find more details on the item and where you can check its status.
This month, we are releasing a patch that impact Team Foundation Server 2018.
Happy Friday (well, now Saturday..). Sorry for the late post, but I had some connectivity challenges that were more difficult to work around than expected yesterday. While I had connectivity challenges and am shipping this post a bit late, our community continues to deliver great content on time. Check out these great posts!
The hidden rule that assigns the bug to the person who created it when the state is changed to resolved, is about to be removed from the Agile process. In this blog post, we wanted to share the impact of this change as well as the work around for those customers who still want to use the rule in their projects.
