Explanation
System-assigned managed identities enable Azure resources to authenticate to cloud services without storing credentials in code. They also support granting privileges to the identity, making them the ideal choice for this scenario. Source: Microsoft

Explanation
Graphical user interface, text, application Description automatically generated

Box 1: Create an Azure logic app.
Box 2: Select the HTTP request trigger.
Box 3: Updated the action group in Azure Monitor.
Reference:
https://docs.microsoft.com/en-us/azure/azure-monitor/alerts/action-groups-logic-app

Explanation

Box 1: Configuration
The following example shows a simple example of a configuration.
configuration IISInstall
{
node "localhost"
{
WindowsFeature IIS
{
Ensure = "Present"
Name = "Web-Server"
}
}
}
Box 2: WindowsFeature
Reference:
https://docs.microsoft.com/en-us/azure/virtual-machines/extensions/dsc-overview

Explanation
There are two different ways to deploy templates to Azure DevOps Services. Both methods provide the same results, so choose the one that best fits your workflow.
1. Add a single step to your build pipeline that runs the PowerShell script that's included in the Azure Resource Group deployment project (Deploy-AzureResourceGroup.ps1). The script copies artifacts and then deploys the template.
2. Add multiple Azure DevOps Services build steps, each one performing a stage task.
The first option has the advantage of using the same script used by developers in Visual Studio and providing consistency throughout the lifecycle.
References:
https://docs.microsoft.com/en-us/azure/vs-azure-tools-resource-groups-ci-in-vsts

Explanation
Branch policies help teams protect their important branches of development. Policies enforce your team's code quality and change management standards.
Reference:
https://docs.microsoft.com/en-us/azure/devops/repos/git/branch-policies