[New Release] ADManager Plus' latest build 8010 is now live!

Hello everyone,

We are glad to let you know that we have released the latest build of ADManager Plus, 8010.

Enhancements:

ADManager Plus now allows you to manage Microsoft 365 without the mandatory configuration of a Microsoft 365 service account.
Users can now diagnose and resolve issues related to network connectivity, URL endpoint connection, Exchange session creation and authentication, and the permissions required by the Entra ID application and service account from Directory/Application Settings.
The default time period in Helpdesk Audit Reports can now be customized, allowing you to view data that aligns with your organization's requirements.
A Select All option has been for custom attributes in Custom Reports, making it easier to generate reports quickly and save time.
The User must change password at next logon field can now be configured for Microsoft 365 and Google Workspace during single user creation.
You can now view member details when selecting AD groups in Access Certification Campaigns.
OUs can now be specified while importing objects from a CSV file or an external data source in automation, allowing you to filter and import only the necessary data from the selected OUs.
The Backup tab has been redesigned for improved usability, and a new Quick Recovery tab has been added, enabling you to quickly review and restore deleted AD objects.
ADManager Plus now supports Windows Server 2025.

Issues fixed:

Exchange Attributes such as HideFromExchangeAddressList, AcceptMessagesFrom, and RejectMessagesFrom were not updated while updating user accounts using User Modification Templates.
Issue preventing Rapid7 integration settings from being saved when GDPR or HIPAA compliance was enabled.
The Members column in the All Users report displayed duplicate entries.
The technician macro assigned to an attribute in ADManager Plus always resolved as Admin when configured in an orchestration template and triggered from the Advanced Management section.
Notifications were triggered for all the objects, even when the objectName criteria in Notification Profile was not met.
Issue where separate email notifications were sent for each task in the automation policy during workflow execution, regardless of the attachment configuration in the notification template.
Issue where modifying group attributes for computers using a CSV file under Bulk Computer Modification failed for subsequent objects if the first object encountered an error.
Deleted managers still appeared in the Manager column of reports.
Issue where orchestration was not triggered for all remaining objects after one object failed during bulk user creation.
Issue where inbound trust domains could not be selected in the Target Domain dropdown during migration.