Azure Update Management - old updates detected as missing

Bojan Zivkovic 436 Reputation points

Hi, I am in the process of evaluating Azure Update Management - we potentially want to use it in environments without Configuration Manager. Having connected test Windows Server 2016 system to Log Analytics Workspace I see these updates as missing ones:


All these updates are superseded by newer updates so basically I see "stale" updates and no newest updates such as July CU for Windows Server 2016. What is wrong here and how to remediate - I am newbie in Azure Update Management, having been working with Configuration Manager to patch servers for many years.

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

3 answers

Sort by: Most helpful
  1. Stanislav Zhelyazkov 21,506 Reputation points MVP

    Updates are detected depending on what Windows Update service on the local server reports as available updates. For example, if Windows Update on the service is configured to get updates from WSUS server and that WSUS server has approved only certain updates you will see only those available. Check if that is the case with our server. You can also login to the server and see what updates are available locally, whatever the server sees it is also what will be shown in Update Management.

    Please "Accept the answer" if the information helped you. This will help us and others in the community as well.

    0 comments No comments

  2. Bojan Zivkovic 436 Reputation points

    We do not have any WSUS server in that environment - just DC and a few member servers and that's it thereby I wanted to patch that environment with Azure Update Management as PoC. We want to test it out and potentially use in all environments where currently we do not have WSUS or MECM and even maybe replace standalone WSUS in some.

  3. Joel Young 15 Reputation points

    I know this is an older post, but I have the same question. I have a domain controller and a member server added into Update Manager. I have no scheduled jobs setup yet. I login daily to these servers to check for updates and compare to what Update Manager is showing. This morning I applied version 1.381.2763.0 so I expected that one to show as missing in Update Manager. But why is this older definition file hanging around as "needed"?

    User's image

    0 comments No comments