Azure DevOps is a work item tracking, source control, and release management solution provided by Microsoft. It is the cloud-based evolution of Team Foundation Server. If you don’t have a DevOps account, you can get one for free at https://azure.microsoft.com/en-us/services/devops/.
Release Pipelines is a powerful feature of DevOps that allows you to create pipelines to deploy your builds out to your server environments. Let’s say that you are creating a Release Pipeline for your website and you have a separate environment for Dev and Production, both hosted on Azure App Services. When you check code in, you want it to be deployed to your Dev environment automatically through Continuous Integration. This is easily configurable through the Release Pipeline interface.
What about your Production environment though? You want to use the same build artifacts for your Dev and Production environments, so it makes…
Recently we had a problem with an internal application that is hosted on Azure PaaS. Windows Authentication would be disabled periodically for our Cloud Service. This would cause our application to return a 403 error to all visitors because we required that users be authenticated before accessing the application. Originally we didn’t have this issue with our application on Azure, but at some point the default IIS configuration changed and we started seeing this issue when a new role was started.