Adaxes roadmap

Allow dynamic updates of forms in Web Interface. For example, change which fields are displayed on the user creation form based on the Employee Type property or depending on which Department is selected, alter the values in the drop-down list for the Job Title field.

Add an option to use Adaxes as a Software as a Service (SaaS) application hosted in the Microsoft Azure cloud.

Make the Administration console a web-based application, so all Adaxes configuration can be managed from a web browser.

Add a possibility to add members to groups for a limited amount of time.

Allow users to bulk import Active Directory objects from CSV files via the Web Interface.

Add an option that will allow users to choose between receiving a code via SMS or using an authenticator app when they reset their forgotten password (if both methods are enabled).

When entering a new password in the Web Interface, display additional information, e.g. if the entered password is weak or strong, whether all requirements are met, etc.

Allow managing Microsoft Teams from Adaxes – create teams and channels, add members, assign policies to members, etc.

Make it possible to send notifications from Adaxes to Microsoft Teams channels. For example, send notifications when users from a specific group reset their passwords.

Allow specifying properties that need to have unique values with the help of Property Patterns and define what needs to be done if a value is not unique. For example, automatically add a digit at the end of an entered username if such a value already exists.

Add an option to Property Patterns which allows generating property values with the help of scripts. For example, automatically generate a custom username on the user creation form using a PowerShell script.

Improve the brute force protection mechanism so that users will not need to enter CAPTCHA. Instead, Adaxes will force the attackers to solve complex cryptographic functions which will render even multi-threaded attacks unfeasible.

Make it possible to enable, disable, and reset multi-factor authentication for Microsoft 365 accounts from Adaxes.

Add more options for drop-down lists. For example, automatically put in all the existing values of the Department property as values of the drop-down list when creating or editing user accounts.

Allow replacing and removing specific characters when generating values with the help of Property Patterns, e.g. always replace ä, ö, ü with a, o, u.

Allow specifying From, CC, BCC fields, setting Sender Name and adding attachments for the ‘Send e-mail notification’ action in Business Rules, Custom Commands and Scheduled Tasks.

Add the ability to forcefully sign out users from their Microsoft 365 accounts, for example, as a part of the deprovisioning process.

Allow updating the operations that were already sent for approval. For example, if an approver notices a mistake or needs to provide additional information for the operation, let them introduce the edits before approving.

When an operation is sent for approval, allow the initiator to specify the reason for why the operation needs to be executed.

Add unique identifiers to be associated with each approval request, so that it’s possible to easily find specific requests and refer to them using their IDs.

Add support for HTML-formatting of emails, such as Enrollment Invitations and Reset Password notifications.

Similarly to sending actions for approval to group owners, also allow sending approval requests to co-owners who are specified via ms-Exch-Co-Managed-By-Link.

Allow users to modify objects in bulk in the Web Interface, for example, to set a manager, change account expiration date or enable smartcard authentication for multiple users in one go.