OMS Monitoring Agent Extension fails intermittently on different VMs (EnterpriseCloudMonitoring)

[davoodharun]

{"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-debug for usage details.","details":[{"code":"Conflict","message":"{\r\n "status": "Failed",\r\n "error": {\r\n "code": "ResourceDeploymentFailure",\r\n "message": "The resource operation completed with terminal provisioning state 'Failed'.",\r\n "details": [\r\n {\r\n "code": "VMExtensionProvisioningError",\r\n "message": "VM has reported a failure when processing extension 'EnterpriseCloudMonitoring'. Error message: \"Operation Failed: 9ad96a5d-b3ff-4428-91de-e1ea33fa6747 is currently connected to a different Azure Cloud, and updating the cloud type is not supported. Please login to the machine, disconnect the workspace, and try again.\"."\r\n }\r\n ]\r\n }\r\n}"}]}

[davoodharun]

[davoodharun]

Although the extension fails, the computer still gets connected to OMS.

[davoodharun]

Provisioning is done through arm template:

{
            "type": "Microsoft.Compute/virtualMachines/extensions",
            "name": "[concat(parameters('vmName'), '/EnterpriseCloudMonitoring')]",
            "apiVersion": "2015-06-15",
            "location": "[resourceGroup().location]",
            "dependsOn": [],
            "properties": {
                "publisher": "Microsoft.EnterpriseCloud.Monitoring",
                "type": "MicrosoftMonitoringAgent",
                "typeHandlerVersion": "1.0",
                "autoUpgradeMinorVersion": true,
                "settings": {
                    "workspaceId": "[reference(resourceId('Microsoft.OperationalInsights/workspaces/', parameters('workspaceName')), '2015-03-20').customerId]"
                },
                "protectedSettings": {
                    "workspaceKey": "[listKeys(resourceId('Microsoft.OperationalInsights/workspaces/', parameters('workspaceName')), '2015-03-20').primarySharedKey]"
                }
            }
        }

[haitch]

this issue should be solved by now, we just published the newer version of the extension.

[davoodharun]

@haitch thank you! I will test tonight

[davoodharun]

confirmed this as resolved.