Chat now with support
Chat with Support

On Demand Migration Current - Active Directory Release Notes

Known issues

The following is a list of issues, including those issues attributed to third-party products, known to exist at the time of release.

Table 3. Directory Sync known issues

Known Issue

Issue ID

An attempt to install an older version of the agent software will fail if a newer version has already been successfully installed.  If, for some reason, the older version is needed, first uninstall the newer version, then remove all registry references to the agent.


The agent installer cannot accept a password with a first character of !.


When discovery discovers an environment, it will read in the OU structure of all domains within the forest.  The UI will show all domains and you can select them for use in all workflows. However, if a DC for that domain is not included, or the agent account does not have read access to the objects, they will not be read into the database.


Cloud Only Security Groups are not read in when reading a cloud endpoint.


User thumbnail photos do not sync to cloud environments.


The PowerShell User Group should be added to the Tenant Group Filter as the Group Owner. A security group should not be used.


An account with access to all domains within the forest is needed if you want to sync all domains within a single forest with a single agent. Using an enterprise admin account is the most efficient method for doing this.


Mapping functions do not work with multivalued attributes. For example, (results(proxyaddresses,"x500:") will not return a true even if an X500 address is present.


When a workflow for a cloud environment has been run once, but then has been idle for longer than 30 days, an error will be encountered when the job starts, and the job will fail and loop repeatedly until the retry count has been reached.


Using a federated target domain to sync users and mailboxes cloud to cloud and on-premises to cloud is currently not supported. Syncing groups and contacts is supported.


In the German and Chinese Office365 tenants, Directory Sync will always do full synchronizations because the delta sync functionality is not available in these local tenants.


An "Object with ID xyz was not found" error may occur when reading recently created Azure guest users due to the longer length of time for guest users to propagate.


Remote Mailboxes from the source are incorrectly created in the target as Users instead of MailUsers.


Delta syncs are limited to 30 days. To avoid full synchronization, a read in should be performed for all cloud environments every 29 days or less.


Password sync does not support AES hashes.


A template configured to sync a binary attribute to a non-binary attribute will not sync correctly.  For example, if syncing Binary (ThumbnailPhoto) to String(ExtensionAttribute), the target attribute will be synced as "System.Byte[]" instead of the expected binary value converted into a string.


A security group cannot be used as a filter group.


When using filter groups for Cloud environments you need to ensure that a group containing any newly created objects is present in the environment filter. This can be accomplished by having a source and target filter group with the same name so they will match and synchronize between the environments. If these objects are not read in after creation, they will not have any additional updates synchronized and they will not be matched.


When synchronizing local AD groups to Office 365 as Office 365 groups (Unified Groups) any contact in the source group will record an error in the logs and the contact will not appear in the target group.


Office 365 Group settings are not copied to the target Office 365 Group.


Likes for Office 365 Group conversations are not migrated.


Custom schema attributes can be added to template mappings but are not visible in the drop-down selection list.


All domains within an Active Directory Forest are visible within an environment when adding a single domain even though the agent account credentials may not have access to all domains.


System requirements

Ensure that your system meets the following minimum platform requirements.

Browser requirements

Table 4. Browser requirements



Chrome or Firefox

Power365 is a cloud-based service. We recommend using Chrome or Firefox for the best cloud-based platform experience.

Online Help and Video Tutorials requirements

Table 5. Online Help and Video Tutorials requirements



Internet Connection

An internet connection is required to access the online help system and video tutorials.

Desktop Experience feature (or a video codec)

Windows Server operating systems will need to have the Desktop Experience feature (or a video codec) installed to view the video tutorials.


Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating