# AD Provisioning Error - Incorrect DN referenced

**URL:** <https://developer.sailpoint.com/discuss/t/ad-provisioning-error-incorrect-dn-referenced/20164>\
**Category:** SHF Discussion and Questions\
**Tags:** provisioning, identity-security-cloud\
**Created:** [November 2, 2023, 7:07pm UTC](https://developer.sailpoint.com/discuss/t/ad-provisioning-error-incorrect-dn-referenced/20164 "2023-11-02T19:07:42Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![mcheek](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/mcheek/32/23705_2.png) [@mcheek](https://developer.sailpoint.com/discuss/u/mcheek)\
**Post date:** [November 2, 2023, 7:34pm UTC](https://developer.sailpoint.com/discuss/t/ad-provisioning-error-incorrect-dn-referenced/20164/4 "2023-11-02T19:34:11Z")

</div>

@KevinHarrington ok, it seems others are having this issue too… I’m going to open a support ticket. I can try your fix in a sub prod environment

> [@Issues with Active Directory Connector](https://developer.sailpoint.com/discuss/t/issues-with-active-directory-connector/19305/11):
>
> SailPoint’s message is consistent that OU moves should take place in IDN in order to utilize a recent fix: Connectivity (CB-DIR 6.1 ) - Active Directory CONETN-4261 The Active Directory connector now instantly returns the Resource Object to IdentityNow on any OU changes done by the AC\_New Parent, which can be further utilized to any rule to work with the updated Resource Object data values.

---

_[View the full topic](https://developer.sailpoint.com/discuss/t/ad-provisioning-error-incorrect-dn-referenced/20164)._