Hope this helps those encountering the registration sign-in issue. After the same occurring for me were observed in the logs I opened a case with support was told this is a known issue that is being investigated. Here is the recently published article - - https://urldefense.proofpoint.com/v2/url?u=https-3A__learn.microsoft.com_en-2Dus_autopilot_known-2Dissues-23known-2Dissues-2Dwith-2Dthe-2Dintune-2Dconnector-2Dfor-2Dad-2Dversion-2D6250120005&d=DwMGaQ&c=rRy1VLRfG3iq78wJmVOlVGvgLG8qPGddnoapq3qqxOA&r=NxJqk45uPs9iGPUVyGs_hQs-Xv6joMHls4yv_wTs3-M&m=76RLYB3VT6fCWk4N4Qt9g7dizt75JdRHDwj6XtQ4q9t4JPD-iY8mmRX0IA7Sx2Uv&s=Zt0drgC-EU5yLrM7NqeuIx7ni21IKz98PEpIzt9_AyU&e=
Date added: April 8, 2025
The following issues are under active investigation:
- Error MSA account <accountName> is not valid when signing in.
- This error occurs when the connector successfully creates the MSA but fails to retrieve the data from the domain controller. Various issues can cause the error, including replication delays between domain controllers in single domain, or when the user account exists in a different domain to the connector machine.
- Error Failed to create a managed service account - Element not found.
- Error Cannot start service ODJConnectorSvc on computer '.'. ---> System.ComponentModel.Win32Exception: The service did not start due to a logon failure after the MSA is created.
- This error occurs when the service can't run as the MSA. The service not being able to run as the MSA can be caused by various issues, including group or local policy restricting Log on as a service privileges.
- Error System.DirectoryServices.DirectoryServicesCOMException (0x8007202F): A constraint violation occurred.