Enable button greyed out on Manage Machines for Update Management

BrianB24 1 Reputation point

The Enable button is greyed out for every machine that I am trying to Enable update management for. I am PIM'd as a Global Administrator, yet I am unable to to add any machines to Update Management.

Azure Automation
Azure Automation
An Azure service that is used to automate, configure, and install updates across hybrid environments.
1,072 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. SwathiDhanwada-MSFT 16,646 Reputation points

    @BrianB24 Welcome to Microsoft Q & A Community Forum. I understand that you want to add further machines to update management for patch management but the enable button has been greyed out. These are couple scenarios where enable button is disabled.

    • To enable Update Management for all available machines reporting to the workspace, select Enable on all available machines on the Manage Machines page. This action disables the control to add machines individually and adds all of the machines reporting to the workspace to the computer group saved search query MicrosoftDefaultComputerGroup. When selected, this action disables the Manage Machines option.
    • To enable the feature for all available machines and future machines, select Enable on all available and future machines. This option deletes the saved search and scope configuration from the workspace and permits the feature to include all Azure and non-Azure machines that currently or in the future, report to the workspace. When selected, this action disables the Manage Machines option permanently, as there's no scope configuration available.

    I assume, you have selected one of the above options, due to which the option to enable the virtual machines has been disabled. If necessary, you can add the scope configuration back by re-adding the initial saved search query. For more information, see Limit Update Management deployment scope. Also, you can try adding the virtual machines by following the steps mentioned in this document.

    0 comments No comments

  2. BrianB24 1 Reputation point

    Found that it was a permissions issue. This has been resolved Thank you for your input.

    0 comments No comments