The Microsoft Azure AD Connect Agent Updater service failed to check for updates.

Question

The Microsoft Azure AD Connect Agent Updater service failed to check for updates.

Nikhil George 41

Hi All,

Hope somebody can help. Very limited documentation available online on this Azure AD Connect Cloud Provisioning Agent.

Only noticed now that the Microsoft Azure AD Connect Agent hasn't been updating. However, the agent synchronizations to azure AD is working without any issue.

The agent is installed on an Azure VM Domain controller on an Azure internal network, no firewalls in the azure network.

The Microsoft Azure AD Connect Agent Updater is installed & running on the same server.

On Investigation from event viewer I am able to see below errors. Where do I look? Why is the updater looking for msappproxy.net? It is not mentioned in the pre-requisites.

The Microsoft Azure AD Connect Agent Updater service failed to check for updates.
Additional details: 'Unable to connect to the remote server'.

The Microsoft Azure AD Connect Agent Updater service failed to check for updates.
Additional details: 'The remote name could not be resolved: 'autoupdate.msappproxy.net''.

The Agent was unable to connect to the service due to networking issues. The Agent tried to access the following URL: 'https://xxxxxx.msappproxy.net/', See Agent troubleshooting for more information: http://go.microsoft.com/fwlink/?LinkID=512316&clcid=0x409

Accepted answer

1 additional answer

Your answer

Answer 1

Carlos Solís Salazar 18,191 MVP Volunteer Moderator

Hi @Nikhil George

Thank you for asking this question on the **Microsoft Q&A Platform. **

Because you have Azure AD Connect version 1.1.584.0, the first troubleshooting action I can recommend is to upgrade Azure AD Connect to the latest version.

According to this documentation, you should upgrade the Azure AD Connect, because of the following:

We're only applying critical changes to the V1.x versions going forward. You might not find some of the features and fixes for V2.0 in the V1.x releases. For this reason, upgrade to the V2.0 version as soon as possible.
On August 31, 2022, all 1.x versions of Azure AD Connect will be retired because they include SQL Server 2012 components that will no longer be supported. Upgrade to the most recent version of Azure AD Connect (2.x version) by that date or evaluate and switch to Azure AD cloud sync.

Hope this helps,
Carlos Solís Salazar

----------

Accept Answer and Upvote, if any of the above helped, this thread can help others in the community looking for remediation for similar issues.
NOTE: To answer you as quickly as possible, please mention me in your reply.

Nikhil George 41 Reputation points

2022-08-18T08:42:52.483+00:00

Hi @Carlos Solís Salazar ,

Again please take note this is not the Full Azure AD connect, This is the lighter Azure AD connect agent which is the agent for the Azure AD cloud sync I am guessing.

Because from azure portal the dashboard for the Cloud sync provides official documentation to below link:
https://learn.microsoft.com/en-us/azure/active-directory/cloud-sync/tutorial-single-forest

which is part of the cloud sync documentation:
https://learn.microsoft.com/en-us/azure/active-directory/cloud-sync/

If you check release history in below link it is different from the regular AD connect. It does not have a version 2.x.x.xx which makes me think retirement notice of August 31 for version 1.x.x.x of the regular AD connect may not apply in this case as the agent is for the Azure Cloud Sync.

1.1.972.0 (Release date: August 8, 2022)
1.1.587.0 (Release date: November 2, 2021)
1.1.584.0 (Release date: August 20, 2021) ----> Our current version
https://learn.microsoft.com/en-us/azure/active-directory/app-provisioning/provisioning-agent-release-version-history

I saw the retirement notice of August 31 which was why I was investigating the status of all the AD connects in my environment.

I have updated all the other AD Connects in my environment manually. But we are using this agent in this 1 instance, I cannot find any documentation on how to upgrade the agent except that it is supposed to update automatically. Which in my case it has not. So I was investigating.

Do you have any guides on how to preform the update specifically for this agent??
Carlos Solís Salazar 18,191 Reputation points MVP Volunteer Moderator

2022-08-19T12:12:40.793+00:00

Hi @Nikhil George this document may help Azure AD Connect: Upgrade from a previous version to the latest
JimmySalian-2011 42,496 Reputation points

2022-08-19T13:03:36.947+00:00

Hi,

You can either manuall run the upgrade installer by following this guide or follow the link provided above - how-to-automatic-upgrade

==
Please "Accept the answer" if the information helped you. This will help us and others in the community as well.
Nikhil George 41 Reputation points

2022-08-25T09:44:17.827+00:00

Hi @Carlos Solís Salazar ,

Again please take note this is not the Full Azure AD connect. I didn't see anything about upgrading the agent in this document.

Pls refer to document shared by Jimmy Salian below
Nikhil George 41 Reputation points

2022-08-25T09:49:30.593+00:00

Hi @JimmySalian-2011 ,

Thank you. Your MS document link is for the correct cloud Sync agent. I have been referring to the same link before posting in this forum.

It mentions that the agent is supposed to auto upgrade but no steps on how to manually upgrade.

So you are suggesting, I execute AzureADConnectAgentUpdater.exe to update it manually? Though this course of action is not mentioned in the documentation:
https://learn.microsoft.com/en-us/azure/active-directory/cloud-sync/how-to-automatic-upgrade
JimmySalian-2011 42,496 Reputation points

2022-08-25T10:02:26.97+00:00

Hi Nikhil,

With the Microsoft AAD Connect and Cloud Sync agent they are automatically upgraded on the new release, when a new version is released, your installation is automatically upgraded. Automatic upgrade is enabled by default.

IIdeally if you are running on the latest version you do not have to manually do any changes, AzureADConnectAgentUpdater.exe should upgrade to the latest version if there are any.

Can you check the config files under Program files, previous experience was to add the proxy settings

AzureADConnectAuthenticationAgentService.exe.config
AzureADConnectAgentUpdater.exe.config
Adding the same lines from last time around then restarting both Updater and Agent services immediately changed the traffic path to a direct connection, no more proxy involvement! The below lines need to go in the <configuration> section:

<system.net>

<defaultProxy enabled="false"></defaultProxy>

</system.net>

verify this FAQ and Proxy settings - how-to-connect-pta-faq

Answer 2

JimmySalian-2011 42,496

Hi,

Can you please provide the version of the AAD Connect on the server?

On the AAD Connect can you run this command on the powershell and provide the output please-:

Invoke-WebRequest -Uri https://adminwebservice.microsoftonline.com/ProvisioningService.svc

If you receiver Error Code 403 - Forbidden The proxy has not been opened for the requested URL - You will have to configure proxy configuration and make sure the URLs are allowed for connectivity (urls-and-ip-address-ranges)

If you receive Error Code 407 Proxy Authentication Required The proxy server required a sign-in and none was provided. If your proxy server requires authentication, make sure to have this setting configured in the machine.config. Also make sure you are using domain accounts for the user running the wizard and for the service account.

If you're using an outbound proxy for connecting to the internet, the following setting in the C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Config\machine.config file must be added for the installation wizard and Azure AD Connect sync to be able to connect to the internet and Azure AD. This text must be entered at the bottom of the file. In this code, <PROXYADDRESS> represents the actual proxy IP address or host name.

Nikhil George 41 Reputation points

2022-08-17T08:46:00.847+00:00

Hello Jimmy,

There is no proxy anywhere in the network.

Output of "Invoke-WebRequest -Uri https://adminwebservice.microsoftonline.com/ProvisioningService.svc" is 200 ok.
StatusCode : 200
StatusDescription : OK.

Please take note this is not the Full Azure AD connect, This is the lighter Azure AD connect agent and it can connect and sync with Azure just fine. No issues there.

It is also supposed to update automatically and it has installed the Microsoft Azure AD Connect Agent Updater on the server for the same.

But it is still running the version 1.1.584.0 from the time of installation and has not updated automatically since. Hence the messages I picked up from the event viewer in my original post.
https://learn.microsoft.com/en-us/azure/active-directory/app-provisioning/provisioning-agent-release-version-history
JimmySalian-2011 42,496 Reputation points

2022-08-17T14:11:21.947+00:00

Sure, the version is critical here and it is very old 1.x so is it possible to upload the log file from the below folder - Open the %ProgramData%\AADConnect\ folder, and upload the latest installation trace log. This log file will provide some details.

As Carlos has also mentioned about the version I agree with that statement.
Nikhil George 41 Reputation points

2022-08-18T10:34:03.727+00:00

Hi @JimmySalian-2011

Please refer to my reply to Carlos.

I am guessing the path will be different for the cloud sync agent. Let me check and back to you.

Share via

The Microsoft Azure AD Connect Agent Updater service failed to check for updates.

1 additional answer

Your answer