Change the ConfigurationMode parameter from ApplyOnly to ApplyAndAutocorrect.
The Register-AzureRmAutomationDscNode cmdlet registers an Azure virtual machine as an APS Desired State Configuration (DSC) node in an Azure Automation account.
Scenario: Current Technical Issue
The test servers are configured correctly when first deployed, but they experience configuration drift over time. Azure Automation State Configuration fails to correct the configurations.
Azure Automation State Configuration nodes are registered by using the following command.

References:
https://docs.microsoft.com/en-us/powershell/module/azurerm.automation/register-azurermautomationdscnode?vi

See explanation 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:
Sign in to the Azure portal, and then select the virtual machine VM1.
In the Support + troubleshooting section, select Boot diagnostics, then select the Settings tab.
In Boot diagnostics settings, change the status to On, and from the Storage account drop-down list, select the storage account az400lod11566895stor.
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

The first thing to do is to declare your SonarQube server as a service endpoint in your VSTS/DevOps project settings.
References: https://docs.sonarqube.org/display/SCAN/Analyzing+with+SonarQube+Extension+for+vsts-TFS

See solution below.
Explanation:
Enable Remote Debugging
Before we start a debugging session to our Azure Function app we need to enable the functionality.
* Navigate in the Azure portal to your function app fa-11566895
* Go to the "Application settings"
* Under "Debugging" set Remote Debugging to On and set Remote Visual Studio version to 2017.
Reference:
https://www.locktar.nl/uncategorized/azure-remote-debugging-manually-in-visual-studio-2017/