AAD Connect Endpoint Error

[Christian Taveras]

This is now the second time we are getting this error.  The Fix Azure Support recommended was to build a new server, so we did.  Now 5 months later were right back here again.  I am lost as to WTH is going on.  Our Sync is broken and I am at my wits end here,  Im hoping someone out there has some info on how to fix this without me having to build a new server.  I upgraded from 1.5.30 to 1.5.45 in hopes that it would fix this but no go.  Im lost and I really need some help.  Here is the error:

Exception details =>
Type => Microsoft.MetadirectoryServices.ServerDownException
Failed even after 5 retries. Action: ExportV1, Network error occurrences = 5. Exception: Unable to communicate with the Windows Azure Active Directory service (CommunicationException). Tracking ID: 598c261e-dfb6-4b94-b7dd-bc988ea49c4f. Endpoint: https://adminwebservice.microsoftonline.com/provisioningservice.svc. See the event log for more details : An error occurred while receiving the HTTP response to https://adminwebservice.microsoftonline.com/provisioningservice.svc. This could be due to the service endpoint binding not using the HTTP protocol. This could also be due to an HTTP request context being aborted by the server (possibly due to the service shutting down). See server logs for more details..
StackTrace =>
at Microsoft.Azure.ActiveDirectory.Connector.ProvisioningServiceAdapter.ExecuteWithRetry(String actionName, Action action)
at Microsoft.Azure.ActiveDirectory.Connector.ProvisioningServiceAdapter.ExportV1(AzureADSyncObjectRequest request)
at Microsoft.Azure.ActiveDirectory.Connector.AADConnector.ExportCore(ICollection`1 connectorSpaceEntriesChanges)
at Microsoft.Azure.ActiveDirectory.Connector.AADConnector.ExportBatch(IList`1 connectorSpaceEntriesChanges)
at Microsoft.Azure.ActiveDirectory.Connector.AADConnector.PutExportEntriesWithRetry(IList`1 connectorSpaceEntriesChanges)

InnerException =>
Type => Microsoft.Online.Coexistence.ProvisionRetryException
Unable to communicate with the Windows Azure Active Directory service (CommunicationException). Tracking ID: 598c261e-dfb6-4b94-b7dd-bc988ea49c4f. Endpoint: https://adminwebservice.microsoftonline.com/provisioningservice.svc. See the event log for more details : An error occurred while receiving the HTTP response to https://adminwebservice.microsoftonline.com/provisioningservice.svc. This could be due to the service endpoint binding not using the HTTP protocol. This could also be due to an HTTP request context being aborted by the server (possibly due to the service shutting down). See server logs for more details.
StackTrace =>
at Microsoft.Online.Coexistence.ProvisionHelper.CommunicationExceptionHandler(CommunicationException ex)
at Microsoft.Online.Coexistence.ProvisionHelper.InvokeAwsAPI[T](Func`1 awsOperation, String opsLabel, IEnumerable`1 operationHeaders)
at Microsoft.Online.Coexistence.ProvisionHelper.Provision(AzureADSyncObjectRequest exports)
at Microsoft.Azure.ActiveDirectory.Connector.ProvisioningServiceAdapter.<>c__DisplayClass76_0.<ExportV1>b__0()
at Microsoft.Azure.ActiveDirectory.Connector.ProvisioningServiceAdapter.ExecuteWithRetry(String actionName, Action action)

InnerException =>
Type => System.ServiceModel.CommunicationException
An error occurred while receiving the HTTP response to https://adminwebservice.microsoftonline.com/provisioningservice.svc. This could be due to the service endpoint binding not using the HTTP protocol. This could also be due to an HTTP request context being aborted by the server (possibly due to the service shutting down). See server logs for more details.
StackTrace =>

Server stack trace:
at System.ServiceModel.Channels.HttpChannelUtilities.ProcessGetResponseWebException(WebException webException, HttpWebRequest request, HttpAbortReason abortReason)
at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)
at System.ServiceModel.Dispatcher.RequestChannelBinder.Request(Message message, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at Microsoft.Online.Coexistence.Schema.IProvisioningWebService.ProvisionAzureADSyncObjects(AzureADSyncObjectRequest syncRequest)
at Microsoft.Online.Coexistence.ProvisionHelper.InvokeAwsApi[T](Func`1 awsOperation, String apiAction, String applicationId, Guid clientTrackingId, String clientVersion, String contextId, String dirSyncBuildNumber, String fimBuildNumber, String machineIdentity, IEnumerable`1 operationHeaders)
at Microsoft.Online.Coexistence.ProvisionHelper.InvokeAwsAPI[T](Func`1 awsOperation, String opsLabel, IEnumerable`1 operationHeaders)

InnerException =>
Type => System.Net.WebException
The underlying connection was closed: An unexpected error occurred on a receive.
StackTrace =>
at System.Net.HttpWebRequest.GetResponse()
at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)

InnerException =>
Type => System.IO.IOException
Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
StackTrace =>
at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)
at System.Net.FixedSizeReader.ReadPacket(Byte[] buffer, Int32 offset, Int32 count)
at System.Net.Security._SslStream.StartFrameHeader(Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security._SslStream.StartReading(Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security._SslStream.ProcessRead(Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.TlsStream.Read(Byte[] buffer, Int32 offset, Int32 size)
at System.Net.PooledStream.Read(Byte[] buffer, Int32 offset, Int32 size)
at System.Net.Connection.SyncRead(HttpWebRequest request, Boolean userRetrievedStream, Boolean probeRead)

InnerException =>
Type => System.Net.Sockets.SocketException
An existing connection was forcibly closed by the remote host
StackTrace =>
at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)

I ran a test to that URI from Posh which I found online and that seems to work so I dont get why the sync server is having an issue with that End point  Here is the output.

PS C:\Users\bdpbmain> Invoke-webrequest -uri https://adminwebservice.microsoftonline.com/ProvisioningService.svc

StatusCode : 200
StatusDescription : OK
Content : <HTML><HEAD><STYLE type="text/css">#content{ FONT-SIZE: 0.7em; PADDING-BOTTOM: 2em; MARGIN-LEFT:
30px}BODY{MARGIN-TOP: 0px; MARGIN-LEFT: 0px; COLOR: #000000; FONT-FAMILY: Verdana;
BACKGROUND-COLOR: wh...
RawContent : HTTP/1.1 200 OK
Strict-Transport-Security: max-age=31536000; includeSubDomains
Content-Length: 6437
Cache-Control: private
Content-Type: text/html; charset=UTF-8
Date: Mon, 10 Aug 2020 03:41:59 G...
Forms : {}
Headers : {[Strict-Transport-Security, max-age=31536000; includeSubDomains], [Content-Length, 6437],
[Cache-Control, private], [Content-Type, text/html; charset=UTF-8]...}
Images : {}
InputFields : {}
Links : {@{innerHTML=http://go.microsoft.com/fwlink/?LinkId=65455;
innerText=http://go.microsoft.com/fwlink/?LinkId=65455; outerHTML=<A href="http://go.microsoft.com/
fwlink/?LinkId=65455">http://go.microsoft.com/fwlink/?LinkId=65455</A>;
outerText=http://go.microsoft.com/fwlink/?LinkId=65455; tagName=A;
href=http://go.microsoft.com/fwlink/?LinkId=65455}}
ParsedHtml : System.__ComObject
RawContentLength : 6437

I also RAn the AAD connect test PS1 file and got the following

[2020-08-10 00:15:03] [INFO] =========================================================
[2020-08-10 00:15:03] [INFO] Starting AAD Connect connectivity and resolution testing.
[2020-08-10 00:15:03] [INFO] Starting Office 365 global administrator and credential tests.
[2020-08-10 00:15:03] [ERROR] Credential required to validate Office 365 credentials. Enter global admin credential.
[2020-08-10 00:15:22] [INFO] Checking Microsoft Online Services Module.
[2020-08-10 00:15:22] [INFO] Finished Microsoft Online Service Module check.
[2020-08-10 00:15:22] [INFO] Attempting logon as ctaveras@XXXXXX.com to Azure Active Directory.
[2020-08-10 00:15:26] [SUCCESS] Successfully logged on to Azure Active Directory as ctaveras@bpbcpa.com.
[2020-08-10 00:15:38] [SUCCESS] User ctaveras@XXXXX.com is a member of Global Administrators.
[2020-08-10 00:15:38] [INFO] Starting local DNS resolution tests.
[2020-08-10 00:15:38] [SUCCESS] Successfully resolved _ldap._tcp.XXXXX.COM.
[2020-08-10 00:15:38] [SUCCESS] Successfully resolved BDCAZ02.XXXXX.COM.
[2020-08-10 00:15:38] [INFO] Finished local DNS resolution tests.
[2020-08-10 00:15:38] [INFO] Starting local network port tests.
[2020-08-10 00:15:41] [SUCCESS] TCP connection to BDCAZ02.XXXXX.COM:53 succeeded.
[2020-08-10 00:15:42] [SUCCESS] TCP connection to BDCAZ02.XXXXX.COM:135 succeeded.
[2020-08-10 00:15:42] [SUCCESS] TCP connection to BDCAZ02.XXXXX.COM:389 succeeded.
[2020-08-10 00:15:42] [SUCCESS] TCP connection to BDCAZ02.XXXXX.COM:445 succeeded.
[2020-08-10 00:15:42] [SUCCESS] TCP connection to BDCAZ02.XXXXX.COM:3268 succeeded.
[2020-08-10 00:15:42] [INFO] Finished local network port tests.
[2020-08-10 00:15:42] [INFO] Starting Online Endpoints tests (Commercial/GCC).
[2020-08-10 00:15:42] [INFO] See https://support.office.com/en-us/article/office-365-urls-and-ip-address-ranges-8548a211-3fe7-47cb-ab...
[2020-08-10 00:15:42] [INFO] for more details on Commercial/GCC endpoints.
[2020-08-10 00:15:42] [INFO] Testing CRL endpoint tests (Invoke-WebRequest).
[2020-08-10 00:15:42] [SUCCESS] Successfully obtained CRL from http://ocsp.msocsp.com.
[2020-08-10 00:15:42] [SUCCESS] Successfully obtained CRL from http://crl.microsoft.com/pki/crl/products/microsoftrootcert.crl.
[2020-08-10 00:15:42] [SUCCESS] Successfully obtained CRL from http://mscrl.microsoft.com/pki/mscorp/crl/msitwww2.crl.
[2020-08-10 00:15:42] [SUCCESS] Successfully obtained CRL from http://ocsp.verisign.com.
[2020-08-10 00:15:42] [SUCCESS] Successfully obtained CRL from http://ocsp.entrust.net.
[2020-08-10 00:15:42] [INFO] Testing Required Resources (TCP:443).
[2020-08-10 00:15:42] [SUCCESS] TCP connection to adminwebservice.microsoftonline.com [40.126.2.5]:443 successful.
[2020-08-10 00:15:42] [SUCCESS] TCP connection to adminwebservice.microsoftonline.com [40.126.2.4]:443 successful.
[2020-08-10 00:15:44] [ERROR] TCP connection to adminwebservice-s1-co2.microsoftonline.com [65.54.170.140]:443 failed.
[2020-08-10 00:15:44] [SUCCESS] TCP connection to login.microsoftonline.com [40.126.2.35]:443 successful.
[2020-08-10 00:15:44] [SUCCESS] TCP connection to login.microsoftonline.com [40.126.2.37]:443 successful.
[2020-08-10 00:15:44] [SUCCESS] TCP connection to login.microsoftonline.com [40.126.2.39]:443 successful.
[2020-08-10 00:15:44] [SUCCESS] TCP connection to login.microsoftonline.com [40.126.2.0]:443 successful.
[2020-08-10 00:15:44] [SUCCESS] TCP connection to login.microsoftonline.com [40.126.2.1]:443 successful.
[2020-08-10 00:15:44] [SUCCESS] TCP connection to login.microsoftonline.com [40.126.2.2]:443 successful.
[2020-08-10 00:15:44] [SUCCESS] TCP connection to login.microsoftonline.com [40.126.2.18]:443 successful.
[2020-08-10 00:15:44] [SUCCESS] TCP connection to login.microsoftonline.com [40.126.2.33]:443 successful.
[2020-08-10 00:15:45] [SUCCESS] TCP connection to provisioningapi.microsoftonline.com [20.190.133.80]:443 successful.
[2020-08-10 00:15:45] [SUCCESS] TCP connection to provisioningapi.microsoftonline.com [20.190.133.82]:443 successful.
[2020-08-10 00:15:45] [SUCCESS] TCP connection to provisioningapi.microsoftonline.com [20.190.133.83]:443 successful.
[2020-08-10 00:15:45] [SUCCESS] TCP connection to provisioningapi.microsoftonline.com [40.126.5.34]:443 successful.
[2020-08-10 00:15:45] [SUCCESS] TCP connection to provisioningapi.microsoftonline.com [40.126.5.38]:443 successful.
[2020-08-10 00:15:45] [SUCCESS] TCP connection to provisioningapi.microsoftonline.com [40.126.5.97]:443 successful.
[2020-08-10 00:15:46] [SUCCESS] TCP connection to provisioningapi.microsoftonline.com [20.190.133.67]:443 successful.
[2020-08-10 00:15:46] [SUCCESS] TCP connection to login.windows.net [40.126.2.37]:443 successful.
[2020-08-10 00:15:46] [SUCCESS] TCP connection to login.windows.net [40.126.2.39]:443 successful.
[2020-08-10 00:15:46] [SUCCESS] TCP connection to login.windows.net [40.126.2.0]:443 successful.
[2020-08-10 00:15:46] [SUCCESS] TCP connection to login.windows.net [40.126.2.1]:443 successful.
[2020-08-10 00:15:46] [SUCCESS] TCP connection to login.windows.net [40.126.2.2]:443 successful.
[2020-08-10 00:15:46] [SUCCESS] TCP connection to login.windows.net [40.126.2.18]:443 successful.
[2020-08-10 00:15:46] [SUCCESS] TCP connection to login.windows.net [40.126.2.33]:443 successful.
[2020-08-10 00:15:46] [SUCCESS] TCP connection to login.windows.net [40.126.2.35]:443 successful.
[2020-08-10 00:15:46] [SUCCESS] TCP connection to secure.aadcdn.microsoftonline-p.com [104.105.81.99]:443 successful.
[2020-08-10 00:15:47] [SUCCESS] TCP connection to management.core.windows.net [23.102.135.246]:443 successful.
[2020-08-10 00:15:48] [ERROR] TCP connection to bba800-anchor.microsoftonline.com [65.54.170.140]:443 failed.
[2020-08-10 00:15:48] [SUCCESS] TCP connection to graph.windows.net [40.126.2.17]:443 successful.
[2020-08-10 00:15:48] [SUCCESS] TCP connection to graph.windows.net [20.190.130.33]:443 successful.
[2020-08-10 00:15:48] [SUCCESS] TCP connection to graph.windows.net [20.190.130.34]:443 successful.
[2020-08-10 00:15:48] [SUCCESS] TCP connection to graph.windows.net [20.190.130.35]:443 successful.
[2020-08-10 00:15:48] [SUCCESS] TCP connection to graph.windows.net [20.190.130.36]:443 successful.
[2020-08-10 00:15:49] [SUCCESS] TCP connection to graph.windows.net [20.190.130.37]:443 successful.
[2020-08-10 00:15:49] [SUCCESS] TCP connection to graph.windows.net [20.190.130.38]:443 successful.
[2020-08-10 00:15:49] [SUCCESS] TCP connection to aadcdn.msauth.net [13.107.246.10]:443 successful.
[2020-08-10 00:15:49] [SUCCESS] TCP connection to aadcdn.msftauth.net [152.199.4.44]:443 successful.
[2020-08-10 00:15:49] [SUCCESS] TCP connection to ccscdn.msauth.net [13.107.246.10]:443 successful.
[2020-08-10 00:15:49] [SUCCESS] TCP connection to ccscdn.msftauth.net [192.229.211.199]:443 successful.
[2020-08-10 00:15:49] [INFO] Testing Optional Resources (TCP:443).
[2020-08-10 00:15:49] [SUCCESS] TCP connection to management.azure.com [40.71.13.226]:443 successful.
[2020-08-10 00:15:49] [SUCCESS] TCP connection to policykeyservice.dc.ad.msft.net [20.190.130.38]:443 successful.
[2020-08-10 00:15:49] [SUCCESS] TCP connection to policykeyservice.dc.ad.msft.net [40.126.2.17]:443 successful.
[2020-08-10 00:15:49] [SUCCESS] TCP connection to policykeyservice.dc.ad.msft.net [20.190.130.33]:443 successful.
[2020-08-10 00:15:49] [SUCCESS] TCP connection to policykeyservice.dc.ad.msft.net [20.190.130.34]:443 successful.
[2020-08-10 00:15:49] [SUCCESS] TCP connection to policykeyservice.dc.ad.msft.net [20.190.130.35]:443 successful.
[2020-08-10 00:15:49] [SUCCESS] TCP connection to policykeyservice.dc.ad.msft.net [20.190.130.36]:443 successful.
[2020-08-10 00:15:49] [SUCCESS] TCP connection to policykeyservice.dc.ad.msft.net [20.190.130.37]:443 successful.
[2020-08-10 00:15:49] [SUCCESS] TCP connection to s1.adhybridhealth.azure.com [40.126.2.17]:443 successful.
[2020-08-10 00:15:49] [SUCCESS] TCP connection to s1.adhybridhealth.azure.com [20.190.130.33]:443 successful.
[2020-08-10 00:15:49] [SUCCESS] TCP connection to s1.adhybridhealth.azure.com [20.190.130.34]:443 successful.
[2020-08-10 00:15:50] [SUCCESS] TCP connection to s1.adhybridhealth.azure.com [20.190.130.35]:443 successful.
[2020-08-10 00:15:50] [SUCCESS] TCP connection to s1.adhybridhealth.azure.com [20.190.130.36]:443 successful.
[2020-08-10 00:15:50] [SUCCESS] TCP connection to s1.adhybridhealth.azure.com [20.190.130.37]:443 successful.
[2020-08-10 00:15:50] [SUCCESS] TCP connection to s1.adhybridhealth.azure.com [20.190.130.38]:443 successful.
[2020-08-10 00:15:50] [SUCCESS] TCP connection to autoupdate.msappproxy.net [52.149.186.68]:443 successful.
[2020-08-10 00:15:50] [SUCCESS] TCP connection to adds.aadconnecthealth.azure.com [20.190.130.38]:443 successful.
[2020-08-10 00:15:50] [SUCCESS] TCP connection to adds.aadconnecthealth.azure.com [40.126.2.17]:443 successful.
[2020-08-10 00:15:50] [SUCCESS] TCP connection to adds.aadconnecthealth.azure.com [20.190.130.33]:443 successful.
[2020-08-10 00:15:50] [SUCCESS] TCP connection to adds.aadconnecthealth.azure.com [20.190.130.34]:443 successful.
[2020-08-10 00:15:50] [SUCCESS] TCP connection to adds.aadconnecthealth.azure.com [20.190.130.35]:443 successful.
[2020-08-10 00:15:50] [SUCCESS] TCP connection to adds.aadconnecthealth.azure.com [20.190.130.36]:443 successful.
[2020-08-10 00:15:50] [SUCCESS] TCP connection to adds.aadconnecthealth.azure.com [20.190.130.37]:443 successful.
[2020-08-10 00:15:50] [SUCCESS] TCP connection to enterpriseregistration.windows.net [40.126.2.40]:443 successful.
[2020-08-10 00:15:50] [INFO] Testing Required Resources Endpoints (Invoke-Webrequest).
[2020-08-10 00:15:50] [SUCCESS] Successfully connected to https://adminwebservice.microsoftonline.com/provisioningservice.svc.
[2020-08-10 00:15:52] [ERROR] Exception: Unable to contact https://adminwebservice-s1-co2.microsoftonline.com/provisioningservice.svc
[2020-08-10 00:15:52] [ERROR] Unable to connect to the remote server
[2020-08-10 00:15:52] [SUCCESS] Successfully connected to https://login.microsoftonline.com.
[2020-08-10 00:15:53] [SUCCESS] Successfully connected to https://provisioningapi.microsoftonline.com/provisioningwebservice.svc.
[2020-08-10 00:15:53] [SUCCESS] Successfully connected to https://login.windows.net.
[2020-08-10 00:15:53] [SUCCESS] Successfully connected to https://secure.aadcdn.microsoftonline-p.com/ests/2.1.5975.9/content/cdnbundles/jquery.1.11.min.js.
[2020-08-10 00:15:53] [INFO] Testing Optional Resources Endpoints (Invoke-Webrequest).
[2020-08-10 00:15:53] [SUCCESS] Successfully connected to https://policykeyservice.dc.ad.msft.net/clientregistrationmanager.svc.
[2020-08-10 00:15:53] [SUCCESS] Successfully connected to https://device.login.microsoftonline.com.
[2020-08-10 00:15:53] [INFO] Testing Seamless SSO Endpoints (TCP:443).
[2020-08-10 00:15:53] [SUCCESS] TCP connection to autologon.microsoftazuread-sso.com [20.190.137.73]:443 successful.
[2020-08-10 00:15:54] [SUCCESS] TCP connection to autologon.microsoftazuread-sso.com [20.190.137.96]:443 successful.
[2020-08-10 00:15:54] [SUCCESS] TCP connection to autologon.microsoftazuread-sso.com [20.190.137.98]:443 successful.
[2020-08-10 00:15:54] [SUCCESS] TCP connection to autologon.microsoftazuread-sso.com [40.126.9.6]:443 successful.
[2020-08-10 00:15:54] [SUCCESS] TCP connection to autologon.microsoftazuread-sso.com [40.126.9.66]:443 successful.
[2020-08-10 00:15:54] [SUCCESS] TCP connection to autologon.microsoftazuread-sso.com [40.126.9.73]:443 successful.
[2020-08-10 00:15:54] [SUCCESS] TCP connection to autologon.microsoftazuread-sso.com [20.190.137.6]:443 successful.
[2020-08-10 00:15:55] [SUCCESS] TCP connection to autologon.microsoftazuread-sso.com [20.190.137.10]:443 successful.
[2020-08-10 00:15:55] [SUCCESS] TCP connection to aadg.windows.net.nsatc.net [40.126.2.33]:443 successful.
[2020-08-10 00:15:55] [SUCCESS] TCP connection to aadg.windows.net.nsatc.net [40.126.2.34]:443 successful.
[2020-08-10 00:15:55] [SUCCESS] TCP connection to aadg.windows.net.nsatc.net [40.126.2.36]:443 successful.
[2020-08-10 00:15:55] [SUCCESS] TCP connection to aadg.windows.net.nsatc.net [40.126.2.37]:443 successful.
[2020-08-10 00:15:55] [SUCCESS] TCP connection to aadg.windows.net.nsatc.net [40.126.2.39]:443 successful.
[2020-08-10 00:15:55] [SUCCESS] TCP connection to aadg.windows.net.nsatc.net [40.126.2.2]:443 successful.
[2020-08-10 00:15:55] [SUCCESS] TCP connection to 0.register.msappproxy.net [104.45.154.25]:443 successful.
[2020-08-10 00:15:55] [SUCCESS] TCP connection to 0.registration.msappproxy.net [52.149.251.86]:443 successful.
[2020-08-10 00:15:56] [SUCCESS] TCP connection to proxy.cloudwebappproxy.net [23.98.154.105]:443 successful.
[2020-08-10 00:15:56] [INFO] Testing Additional Resources Endpoints (Invoke-Webrequest).
[2020-08-10 00:15:56] [ERROR] Unable to resolve host watchdog.servicebus.windows.net.
[2020-08-10 00:15:56] [ERROR] watchdog.servicebus.windows.net : DNS name does not exist
[2020-08-10 00:15:56] [INFO] Finished Online Endpoints tests.
[2020-08-10 00:16:17] [INFO] AAD_PREMIUM_P2 contains an Azure AD Premium Service to enable Password Write Back.
[2020-08-10 00:16:17] [INFO] EMS contains an Azure AD Premium Service to enable Password Write Back.
[2020-08-10 00:16:17] [INFO] Starting Active Directory tests.
[2020-08-10 00:16:21] [INFO] Forest is Windows Server 2012 R2 mode. Supported.
[2020-08-10 00:16:21] [SUCCESS] Domain NetBIOS name does not contain a period. Passed.
[2020-08-10 00:16:21] [INFO] AD Recycle Bin is ENABLED.
[2020-08-10 00:16:21] [INFO] Starting system configuration gathering.
[2020-08-10 00:16:21] [INFO] System name: AZADC02
[2020-08-10 00:16:21] [INFO] 64-bit operating system detected: True
[2020-08-10 00:16:21] [INFO] Operating System: Microsoft Windows Server 2016 Datacenter 10.0
[2020-08-10 00:16:21] [INFO] Operating System Edition is Datacenter Server. Installation may be supported if the Operating System version is supported.
[2020-08-10 00:16:21] [INFO] WinHTTP proxy settings (netsh winhttp show proxy):
[2020-08-10 00:16:21] [INFO] Current WinHTTP proxy settings: Direct access (no proxy server).
[2020-08-10 00:16:21] [INFO] .NET proxy settings (machine.config/configuration/system.net/defaultproxy):
[2020-08-10 00:16:21] [INFO] No proxy configuration exists in C:\windows\Microsoft.NET\Framework64\v4.0.30319\Config\machine.config.
[2020-08-10 00:16:21] [INFO] For more .NET proxy configuration parameters, see https://docs.microsoft.com/en-us/dotnet/framework/configure-apps/file-schema/network/proxy-element-n...
[2020-08-10 00:16:21] [INFO] The version of .NET Framework installed is 4.7.2 or greater.
[2020-08-10 00:16:21] [INFO] No service packs are required for this version of Windows.
[2020-08-10 00:16:21] [INFO] Attempting to check installed features.
[2020-08-10 00:16:22] [INFO] Command available. Checking installed features.
[2020-08-10 00:16:22] [SUCCESS] Required feature .NET Framework 4.6 Features [NET-Framework-45-Features] is installed.
[2020-08-10 00:16:22] [SUCCESS] Required feature .NET Framework 4.6 [NET-Framework-45-Core] is installed.
[2020-08-10 00:16:22] [INFO] Finished checking installed features.
[2020-08-10 00:16:22] [INFO] Checking TLS settings for Windows Server 2016.
[2020-08-10 00:16:22] [INFO] Key HKLM:SOFTWARE\Microsoft\.NETFramework\v4.0.30319\SchUseStrongCrypto with a value of 1 is set correctly for TLS 1.2 Configuration.
[2020-08-10 00:16:22] [INFO] Key HKLM:SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319\SchUseStrongCrypto with a value of 1 is set correctly for TLS 1.2 Configuration.
[2020-08-10 00:16:22] [INFO] Finished checking for TLS 1.2 Configuration settings.
[2020-08-10 00:16:22] [SUCCESS] PowerShell transcription is not configured.
[2020-08-10 00:16:22] [INFO] Finished gathering system configuration.
[2020-08-10 00:16:22] [INFO] Done! Logfile is 2020-08-10_AADConnectConnectivity.txt.
[2020-08-10 00:16:22] [INFO] ---------------------------------------------------------

Im hoping someone can help.

[#2]

@Christian Taveras 

Ive been seeing the same issue across all out Domain controllers and AAD connect servers running Azure AD connect health. Did you ever get to the bottom of this?

[#3]

Nope, if I run the AADCONNECT PS Script that checks all the endpoints it still errors out.
It has been working or i should say it has been sending over local AD changes to Azure.
However these errors that caused it to crash have stopped. I cannot say what the issue is cause MS is clueless. They themselves saw the errors to specific endpoints and did not know how to resolve. Im basically living on borrowed time cause sooner or later I think its going to break again. I ran the script 3days ago just to see if the errors still occurred and they do.

[#4]

Thanks Christian,

I actually got to the bottom of our issues. It was caused by outbound IPS monitoring on our Fortinet firewalls. We have a cause open with them investigating it but for now at least we have a workaround.

Regards

David 

[#5]

اى موسيقاه