Skip to content

Commit 61c493b

Browse files
authored
Added clarification for dual state cleanup
1 parent 86d1890 commit 61c493b

File tree

1 file changed

+1
-3
lines changed

1 file changed

+1
-3
lines changed

articles/active-directory/devices/hybrid-azuread-join-plan.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -91,9 +91,7 @@ If your Windows 10 domain joined devices are [Azure AD registered](overview.md#g
9191
- In Windows 10 1803, if you have Windows Hello for Business configured, the user needs to re-setup Windows Hello for Business after the dual state clean up.This issue has been addressed with KB4512509
9292

9393
> [!NOTE]
94-
> The Azure AD registered device will not be automatically removed if it is managed by Intune. When the automatic device removal is attempted, you will see an error in the User Device Registration event log with an Event ID of 204 and an error code of 0x801c03f2 (DSREG_E_DIRECTORY_FAILURE).
95-
>
96-
> The server response will include the following message: The device object with id '00000000-0000-0000-0000-000000000000' in tenant '00000000-0000-0000-0000-000000000000' could not be removed from the store because it is managed by MDM application '00000000-0000-0000-0000-000000000000'.
94+
> The Azure AD registered device will not be automatically removed if it is managed by Intune.
9795
9896
## Review controlled validation of hybrid Azure AD join
9997

0 commit comments

Comments
 (0)