In Azure Automation State Configuration, the Desired State Configuration (DSC) configuration files are used to define the desired state of resources on a system. The structure of the code blocks in a DSC configuration file should be organized in a logical and meaningful way.
One way to structure the code blocks is as follows:
Configuration: This block defines the overall configuration, including any parameters that are used in the configuration.
Node: This block defines the target node(s) for the configuration, typically specified by the hostname or IP address of the target system.
Resource: This block defines the resources that are managed by the configuration, including the resource type, module, and properties.
"A configuration script consists of the following parts:
The Configuration block. This is the outermost script block. You define it by using the Configuration keyword and providing a name. In this case, the name of the configuration is MyDscConfiguration.
One or more Node blocks. These define the nodes (computers or VMs) that you are configuring. In the above configuration, there is one Node block that targets a computer named TEST-PC1. The Node block can accept multiple computer names.
One or more resource blocks. This is where the configuration sets the properties for the resources that it is configuring. In this case, there are two resource blocks, each of which call the WindowsFeature resource."
https://docs.microsoft.com/en-us/powershell/dsc/configurations/configurations?view=dsc-1.1#configuration-syntax

Denies non HTTPS traffic.

For containerized applications that serve traffic, you might want to verify that your container is ready to handle incoming requests. Azure Container Instances supports readiness probes to include configurations so that your container can't be accessed under certain conditions.
Reference:
https://docs.microsoft.com/en-us/azure/container-instances/container-instances-readiness-probe

You can manage technical debt with Sonar Rube and Azure DevOps.
Note: Technical debt is the set of problems in a development effort that make forward progress on customer value inefficient. Technical debt saps productivity by making code hard to understand, fragile, time-consuming to change, difficult to validate, and creates unplanned work that blocks progress. Unless they are managed, technical debt can accumulate and hurt the overall quality of the software and the productivity of the development team in the long term SonarQube an open source platform for continuous inspection of code quality to perform automatic reviews with static analysis of code to:
Detect Bugs
Code Smells
Security Vulnerabilities
Centralize Quality
What's covered in this lab
Reference:
https://azuredevopslabs.com/labs/vstsextend/sonarqube/

Reference:
https://docs.microsoft.com/en-us/azure/devops/report/dashboards/velocity-guidance?view=vsts
https://docs.microsoft.com/en-us/azure/devops/report/dashboards/cycle-time-and-lead-time?view=vsts
https://docs.microsoft.com/en-us/azure/devops/report/dashboards/configure-burndown-burnup-widgets?view=vsts