This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(201.6, 18%, 29%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESS%3C/text%3E%3C/svg%3E)
Start-ADSyncSyncCycle : System.Management.Automation.CmdletInvocationException: System.InvalidOperationException: There was an issue obtaining cloud sync intervals --->
System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: The remote name could not be resolved:
'autologon.microsoftazuread-sso.com'
What changes have been made? When did this start?
Looks like firewall? Network? DNS? Did anyone make an changes in Entra with policies or othewise?
Look in Entra for the "On-Premises Directory Synchronization Service Account" and check the
User sign-ins (non-interactive)
and see if there are any failures and if so, what is causing it.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(240, 17%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ED%3C/text%3E%3C/svg%3E)
We had the same issue. It startet around "February 25, 2025 18:27 UTC" and was resolved around "February 25, 2025 18:57 UTC"
Our Sync Server is in Switzerland
Hello @Scott Simmons,
Thank you for posting your query on Microsoft Q&A.
Based on the error message you provided, it appears your issue aligns with the recent DNS outage. A critical DNS misconfiguration in Microsoft Entra ID disrupted authentication services globally for nearly 90 minutes on February 25, 2025, impacting organizations using Seamless Single Sign-On (SSO) and Microsoft Entra Connect Sync.
The outage was caused by an IPv6 infrastructure cleanup operation that inadvertently removed essential CNAME records for the autologon.microsoftazuread.sso.com domain, leading to cascading failures in Kerberos ticket validation.
By 17:40 UTC, our engineers identified the faulty DNS change and began rollback procedures. Full recovery was achieved by 18:35 UTC after reverting the configuration, though some Entra Connect Sync deployments experienced residual synchronization delays.
For more details on this outage, you can refer to the following blog post:
Microsoft DNS Change Disrupts Entra ID Authentication – What You Need to Know
Please let me know if you are still encountering this error.
I hope this information is helpful. Please feel free to reach out if you have any further questions.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Hello @Scott Simmons,
Following up to see if the above answer was helpful. If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.
Hello @Scott Simmons,
Following up to see if the above answer was helpful. If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.