Tested automation for update management on one of the VMs and the KBs got installed and reboot success but still the deployment status is showing failed.
][1]
Tested automation for update management on one of the VMs and the KBs got installed and reboot success but still the deployment status is showing failed.
][1]
Welcome to Microsoft Q&A! Thanks for posting the question.
I understand that you were using Azure Automation Update Management to install updates on VM, which seems to have succeeded, however the Deployment shows as failed in Azure portal. Based on the screenshot shared, it is interesting that "Maintenance Window utilization" shows as 0 minutes utilization out of the allocated 120 minutes for this update. Here are some of the probable causes and respective steps that can be taken to investigate and/or resolve this issue:
1. Were the installation of KBs done around the same time as the created schedule? You can review the "Application" and "System" event logs under "Windows Logs" in EventViewer to get details of time when these updates were installed. It is possible that the updates were installed as part of automatic update being enabled in this machine: Updates are installed without a deployment
2. To get the details of the error, please click on the "<Deployment Name>" under History in Azure Portal --> Automation Account --> Update Management. That should give you the error
at the very top of the screen as shown below:

3. You may also refer to the "All Logs" and "Output" under the scheduled deployment to understand the exact cause of error.

4. Another cause of this error could be that the VM was/is not able to communicate with the LogAnalytics workspace around the scheduled maintenance. You may use the "Heartbeat" table queries in Log Analytics workspace to check if this machine was reporting its heartbeat around that time to Log Analytics Workspace.
5. Did the "deployment name" contain special characters like "[", "}", ";" ? Inclusion of such characters may also cause the processing to fail.
6. Also, you may refer to the following logs in EventViewer for failures.
> Applications and Services Logs\Operations Manager: This would contain errors related to failure to connect to workspace and other errors related to the functioning of the LogAnalytics agent itself.
> Applications and Services Logs\Microsoft-Automation\Operational: (if available) This would contain errors related hybrid runbook execution and failures.
> Applications and Services Logs\Microsoft-SMA\Operational: (if available) This would contain errors related to functioning of local hybrid runbook worker sandbox.
Please let me know if you have any questions.
Please 'Accept as answer' and ‘Upvote’ if it helped so that it can help others in the community looking for help on similar topics.
@ramyananduri-2766, I wanted to check if you had a chance to review my answer above. Please let me know if you have any queries or concerns.
Please 'Accept as answer' if it helped so that it can help others in the community looking for help on similar topics.
7 people are following this question.