Systems Administrator

Scott Simmons 10 Reputation points
2025-02-25T18:14:59.9666667+00:00

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'

Microsoft Security | Microsoft Entra | Microsoft Entra ID
0 comments No comments
{count} votes

3 answers

Sort by: Most helpful
  1. Andy David - MVP 157.8K Reputation points MVP Volunteer Moderator
    2025-02-25T20:04:10.2066667+00:00

    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.

    0 comments No comments

  2. Dave_MME 0 Reputation points
    2025-02-25T20:42:41.1133333+00:00

    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

    0 comments No comments

  3. Raja Pothuraju 23,715 Reputation points Microsoft External Staff Moderator
    2025-03-03T15:24:00.53+00:00

    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".


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.