See solution below.
Explanation
Step 1: To create a general-purpose v2 storage account in the Azure portal, follow these steps:
* On the Azure portal menu, select All services. In the list of resources, type Storage Accounts. As you begin typing, the list filters based on your input. Select Storage Accounts.
* On the Storage Accounts window that appears, choose Add.
* Select the subscription in which to create the storage account.
* Under the Resource group field, select RG1lod11566895
* Next, enter a name for your storage account named: az400lod11566895stor
* Select Create.
Step 2: Enable boot diagnostics on existing virtual machine
To enable Boot diagnostics on an existing virtual machine, follow these steps:
1. Sign in to the Azure portal, and then select the virtual machine VM1.
2. In the Support + troubleshooting section, select Boot diagnostics, then select the Settings tab.
3. In Boot diagnostics settings, change the status to On, and from the Storage account drop-down list, select the storage account az400lod11566895stor.
4. Save the change.

You must restart the virtual machine for the change to take effect.
Reference:
https://docs.microsoft.com/en-us/azure/storage/common/storage-account-create
https://docs.microsoft.com/en-us/azure/virtual-machines/troubleshooting/boot-diagnostics

Explanation
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-synt

See solution below.
Explanation
Set up staging environments in Azure App Service
1. Open Microsoft Azure Portal
2. Log into your Azure account, select your app's resource page, in the left pane, select Deployment slots > Add Slot.

3. In the Add a slot dialog box, give the slot a name, and select whether to clone an app configuration from another deployment slot. Select Add to continue.

4. After the slot is added, select Close to close the dialog box. The new slot is now shown on the Deployment slots page. By default, Traffic % is set to 0 for the new slot, with all customer traffic routed to the production slot.
5. Select the new deployment slot to open that slot's resource page.

6. Change TRAFFIC % to 10
References:
https://docs.microsoft.com/en-us/azure/app-service/deploy-staging-slots

Explanation
In some cases, you need to bypass policy requirements so you can push changes to the branch directly or complete a pull request even if branch policies are not satisfied. For these situations, grant the desired permission from the previous list to a user or group. You can scope this permission to an entire project, a repo, or a single branch. Manage this permission along the with other Git permissions.
References: https://docs.microsoft.com/en-us/azure/devops/repos/git/branch-policies