AzureVM Extension Microsoft.EnterpriseCloud.Monitoring CPU Architecture x64 was not found in the extension repository

Fabrice 116 Reputation points


Hello together,

When i want to install the Microsoft.EnterpriseCloud.Monitoring Agent with PowerShell i got this error message:
Set-AzVMExtension: Extension with publisher ... for CPU Architecture x64 was not found in the extension repository.

The VM type is: Standard E4as

I strongly suspect that it is the VM Type, because I can still install the extension on other VMs.

Does anyone have an idea how I could solve this?

Set-AzVMExtension -ExtensionName "Microsoft.EnterpriseCloud.Monitoring" -ResourceGroupName $VM.ResourceGroupName
-VMName $VM.Name -Publisher "Microsoft.EnterpriseCloud.Monitoring"
-ExtensionType "MicrosoftMonitoringAgent" -TypeHandlerVersion 1.2

Azure Monitor
Azure Monitor
An Azure service that is used to collect, analyze, and act on telemetry data from Azure and on-premises environments.
2,851 questions
Azure Virtual Machines
Azure Virtual Machines
An Azure service that is used to provision Windows and Linux virtual machines.
7,244 questions
0 comments No comments
{count} votes

4 answers

Sort by: Most helpful
  1. Olga Os - MSFT 5,836 Reputation points Microsoft Employee

    Hello @Fabrice ,

    Welcome to the MS Q&A forum.

    I suspect the root cause could be the script itself. I noticed you are using the publisher name "Microsoft.EnterpriseCloud.Monitoring" while setting up the "ExtensionName" parameter. This one should be "MicrosoftMonitoringAgent" or "omsagentforlinux" depending on the OS.

    As example, check this code snippet below: Log Analytics virtual machine extension for Windows


    As additional if above doesn't help to resolve the issue, please kindly share what is VM OS, your end goal, and if you are following up any specific public article to deploy the extension.


    Let us know if you need additional assistance. If the answer was helpful, please accept it and complete the quality survey so that others can find a solution.

    1 person found this answer helpful.

  2. Olga Os - MSFT 5,836 Reputation points Microsoft Employee

    @Fabrice ,

    I engaged the engineering team and they confirmed where is no known limitation do deploy the agent on a machine with the specified SKUs.
    Are you able to share variable values which were used in your deployment?
    Can you do one quick test for me? Can you please resize VM to another size and try to install the MicrosoftMonitoringAgent agent.
    One more ask, can you run below PowerShell command with your VM location and provide output?

    Get-AzVMExtensionImage -Location 'westcentralus' -PublisherName 'Microsoft.EnterpriseCloud.Monitoring' -Type 'MicrosoftMonitoringAgent' | foreach { $_.Version } | sort {[version] $_} -Descending   

    PS: we are investigating if where is any failing downstream or outage affecting your deployment.


  3. Olga Os - MSFT 5,836 Reputation points Microsoft Employee

    Hello @Fabrice ,

    I am just wondering if you were facing the same issue again?

    I found few similar posts and on all issue with the same failure was also self-resolved and mostly didn't occur again.

    Olga Os

    0 comments No comments

  4. Fabrice 116 Reputation points

    Hello Olga Os,

    Solution: Migration to the Azure Monitoring Agent and not use the log analytics agent.

    Best greetings