Azure AD Connect v1.2.69.0 fixes an issue with Device Write-Back

Reading Time: < 1 minute

Azure AD Connect

Late last week, Microsoft released a new version of Azure AD Connect, its free Hybrid Identity bridge product to synchronize objects and their attributes from on-premises Active Directory Domain Services (AD DS) environments and LDAP v3-compatible directories to Azure Active Directory.


What’s Fixed

There is only one fix in version

This hotfix build allows an admin to select a target domain, within the specified forest, for the RegisteredDevices container when enabling device write-back.

In the previous versions that contain the new Device Options functionality (versions 1.1.819.0 through, the RegisteredDevices container location was limited to the forest root and did not allow child domains. This limitation only manifested itself on new deployments; in-place upgrades were unaffected.

If any build containing the updated Device Options functionality was deployed to a new server and device write-back was enabled, you will need to manually specify the location of the container if you do not want it in the forest root. To do this, you need to disable device write-back and re-enable it which will allow you to specify the container location on the Writeback forest page.

This release is only distributed to organizations using Azure AD Connect for manual download.


Version information

This is version of Azure AD Connect.
It was signed off on on November 19th, 2018 and made available for download on December 11th, 2018



You can download Azure AD Connect here.
The download weighs 83,5 MB.

leave your comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.