Skip to content

Commit c531afd

Browse files
Merge pull request #17797 from MicrosoftDocs/frankroj-patch-4
Update formatting
2 parents c3b9287 + 0e8981a commit c531afd

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

autopilot/known-issues.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ author: frankroj
88
ms.author: frankroj
99
ms.reviewer: madakeva
1010
manager: aaroncz
11-
ms.date: 04/17/2025
11+
ms.date: 04/21/2025
1212
ms.collection:
1313
- M365-modern-desktop
1414
- highpri
@@ -43,8 +43,7 @@ This article describes known issues that can often be resolved with configuratio
4343
4444
### Known issues with the Intune Connector for AD version 6.2501.2000.5
4545
46-
Date added: *April 8, 2025*
47-
46+
Date added: *April 8, 2025*<br>
4847
Date updated: *April 18, 2025*
4948
5049
The following issues are under active investigation:
@@ -59,9 +58,11 @@ The following issues are under active investigation:
5958
6059
- **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.**
6160
62-
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. For more information on how to mitigate, see [Troubleshooting FAQ](/autopilot/troubleshooting-faq#troubleshooting-the-intune-connector-for-active-directory).
61+
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. For more information on how to mitigate this error, see [Troubleshooting FAQ](/autopilot/troubleshooting-faq#why-is-the-error--cannot-start-service-odjconnectorsvc-on-computer------occurring-when-setting-up-the-intune-connector-for-active-directory-).
6362
64-
- **Error `System.DirectoryServices.DirectoryServicesCOMException (0x8007202F): A constraint violation occurred.`** For more information on how to mitigate, see [Troubleshooting FAQ](/autopilot/troubleshooting-faq#troubleshooting-the-intune-connector-for-active-directory).
63+
- **Error `System.DirectoryServices.DirectoryServicesCOMException (0x8007202F): A constraint violation occurred.`**
64+
65+
For information on how to mitigate this error, see [Troubleshooting FAQ](/autopilot/troubleshooting-faq#troubleshooting-the-intune-connector-for-active-directory).
6566
6667
### TPM attestation isn't working for TPMs which use high-range RSA 3072EK
6768
@@ -77,8 +78,7 @@ The Windows Autopilot profile setting which enables automatic configuration of t
7778
7879
### Windows Autopilot report incorrectly shows failure even though the deployment was successful
7980
80-
Date added: *February 11, 2025*
81-
81+
Date added: *February 11, 2025*<br>
8282
Date updated: *March 20, 2025*
8383
8484
This issue is resolved.

0 commit comments

Comments
 (0)