What's new in Adaxes 2026.2

Adaxes 2026.2 is all about refining existing functionality and closing the gaps in your everyday workflows. It brings resource mailbox creation, better accountability for every operation, more options to provide contextual information to web interface users, and improved performance.

Here's more about what's new in Adaxes 2026.2.

Resource mailbox creation

Until now, creating a room or equipment mailbox meant creating a user account, assigning an Exchange Online license, converting the mailbox to a resource mailbox, and finally revoking the license. Sure, you could automate most of those steps, but it wasn't ideal.

Adaxes 2026.2 lets you create resource mailboxes in a single operation.

There are customizable creation forms in the web interface, business rules that trigger before or after resource mailbox creation, a new built-in Resource property pattern, and so on. All the typical object creation workflows that you are so familiar with are now also available for resource mailboxes.

If you need to use scripts to provision resource mailboxes from external systems, we've also got you covered. Have a look at the resource mailbox creation script examples for PowerShell and REST API in our SDK.

Operation reason

By popular demand, every operation in the web interface can now prompt users for a reason before proceeding.

On the surface, this allows your users to justify the actions they send for approval, making life easier for the approvers. But it's much more than that.

Think of it as a customizable field that you can add to any operation, request any kind of information from the initiator, and provide any last-minute details they need to know.

Of course, the value entered by the initiator can be used in automated workflows that trigger after the operation. For example, you can configure an operation to request a ticket number, and have a business rule which updates this ticket in your ticketing system.

By default, the reason prompt is disabled for every operation. For information on how to enable and customize it, see the Operation reason section in this tutorial: How to configure and organize operations.

Summary before creation

Adaxes now shows a summaryas a final step before creating a new object. This lets the creator preview exactly what will be committed to the directory, and catch mistakes before they matter.

After upgrading to the new version, a summary will be displayed when creating all types of objects, except organizational units. If you need guidance on how to adjust this behavior, see the Summary section in this tutorial: How to configure and organize operations.

Success step customization

You can now display a custom message when a web interface operation succeeds or is sent for approval. For example, you can add guidelines, checklists, instructions on what to do next, useful links, or any other relevant information.

With the help of value references, these messages can include contextual information about the operation target. A reminder to call the user's manager after an MFA reset is easier to act upon if it contains the manager's name and phone number.

For details on how to customize the success step, see the Success step section in this tutorial: How to configure and organize operations.

Event log IDs

Each event written to the Adaxes event log now has a unique identifier, making it easier to monitor Adaxes health, set up alerts for critical errors, and troubleshoot issues when they occur.

The help article on How to view the service event log now contains a table with event descriptions, IDs, and troubleshooting steps in some well-known cases. Of course, your feedback is always welcome – if you are concerned about a particular event and the available information is insufficient, just let our support team know. We'll investigate it and expand the documentation as needed.

Webcam photo capture

Users can now set their profile photo directly from their webcam. This makes it easier for new employees to meet photo requirements without preparing and uploading an image file separately.

There's one caveat which is unlikely to impact production deployments but is still worth mentioning: webcam photo capture only works via HTTPS.

New operators for criteria

We have added -in and -notin operators to criteria. They can only be used in PowerShell scripts, but they let you transform lengthy chains of -or operators into more readable code. For example:

# With only four values, this
$values = @("Sales", "Marketing", "IT", "HR")
$criteria = New-AdmCriteria -Type "user" -Expression {department -in $values}

# is already better than this
$criteria = New-AdmCriteria -Type "user" -Expression `
{department -eq "Sales" -or department -eq "Marketing" -or department -eq "IT" -or department -eq "HR"}

Keep in mind that both examples above compile down to the same criteria and will look the same in the UI.

Reworked Exchange mailbox database selection

It is no longer possible to restrict allowed mailbox databases or change the database selection mechanism using a property pattern. Any existing configuration for the Mailbox database virtual property will be lost after upgrading to Adaxes 2026.2.

Here's a screenshot for a closer look at what we're talking about:

What does this mean for you and your on-premises mailbox creation processes?

• Automated workflows – nothing changes. The Create an Exchange mailbox action in business rules, custom commands, and scheduled tasks still has the same database selection options as before.
• Mailbox creation in the administration console – nothing changes. You have the same mailbox database selection options as before.
• REST API – nothing changes. As before, you have to specify a mailbox database in the API request.
• Single mailbox creation in the web interface – it is no longer possible to hide specific mailbox databases from the user creating a mailbox. If the operation configuration allows selecting a database, the user will be able to select from all applicable databases.
• Bulk mailbox creation in the web interface – it is no longer possible to prioritize databases with fewer mailboxes when creating several on-premises mailboxes in a single operation. You can still use the in turn distribution method or let Exchange automatically select a database for each new mailbox.

Security improvements

We continue improving the security of Adaxes, adding features that follow modern best practices.

Sign-in session termination

Adaxes now signs users out of all their active sessions when their account expires, gets disabled, or has its password changed or reset. A web interface session will never outlive the credentials used to create it.

The sessions are terminated no matter where the action came from. You can reset a user's password directly in the Entra admin center, and every Adaxes web interface session will be terminated.

Native browser cryptography

The web interface now uses the browser's built-in Web Crypto API to generate RSA keys, sign requests, and encrypt sensitive data. This replaces the third-party cryptography library previously used for these operations, which has recently reached end of support. The library is retained only as a fallback for environments where secure context is unavailable, for example, when the web interface is accessed over plain HTTP.

Vulnerability fixes

• Fixed a vulnerability where temporary direct links for downloading files exported from the web interface were accessible without authentication until their expiration.

Other improvements

• The Reset multifactor authentication operation now also resets FIDO2 passkeys when the option to reset MFA in Microsoft 365 is selected, with no additional configuration required.
• It is now possible to delete photos of Microsoft Entra accounts in the web interface.
• Recent value suggestions and autocomplete are now available in the Exchange section of the web interface, and in a variety of input fields that support value references.
• We have updated the web interface configuration caching mechanism to avoid excessive checks for configuration changes. It should improve the performance in certain scenarios and increase the initial web interface loading speed after the configuration has changed or the application pool in IIS was recycled.
• We have also updated the built-in PowerShell SDK to version 7.6 and the Exchange Online Management PowerShell module to version 3.10.1.
• Adaxes can now log requests sent to the configured SMS provider, making it easier to troubleshoot SMS delivery issues.
• Adaxes now has 10 more custom date attributes: adm-CustomAttributeDate16...adm-CustomAttributeDate25.

Bug fixes

Here are the issues we have addressed in this release.

Adaxes service

• Fixed the An unknown directory domain object was requested error that caused an Entra domain to be unavailable for a period after restoring a configuration backup with an expired Entra app client secret and entering a new secret.
• Fixed the The recipient has neither a mailbox nor an email address error that could occur because Exchange-related actions in business rules that trigger after user creation didn't wait for mailbox readiness when creating Entra users.
• Fixed an issue where the Adaxes service would fail to start if the Windows Time Service was not running and the system clock had been manually set forward and then corrected back.
• Fixed an issue where Adaxes failed to clean up temporary files in C:\Users\AdaxesWebUIPool\AppData\Local\Temp, which could cause the folder to grow significantly.
• Fixed an issue where Adaxes was unable to determine the domain and forest functional level if the domain service account was denied read access to the ms-DS-Behavior-Version property.
• Fixed an issue that could cause master key corruption in some edge cases when connectivity was lost between Adaxes services in a configuration set, requiring a secure storage reset or reinstallation.
• Fixed an issue where security role permissions over group members failed to apply when the trustee, group, and its members were from a parent domain, but Active Directory routed Adaxes service queries to a subdomain's Global Catalog.

• Fixed an issue in several built-in reports that caused certain Microsoft 365 groups to be omitted from results. Affected reports: Members of groups, Members of my managed groups, Membership in groups, Objects' membership in groups, Users' membership in groups, Direct member count.

Web interface

• Fixed an issue where the web interface configurator would not load if the connection to the domain of the signed in user was lost after signing in.
• Fixed an issue in the Edit Microsoft 365 properties web interface action where copying an object and pasting it back in would fail to resolve that object due to redundant metadata in the pasted value.
• Fixed missing navigation controls and redirection to the original URL when using the ReturnUrl parameter in the password self-service URL as described in this tutorial.
• Fixed an endless redirect loop that occurred when attempting to sign in to a web interface with an Entra account not managed by Adaxes if the web interface was configured to use SAML-based SSO.
• Fixed the The parameter value is not a valid numeric error that occurred when the value of a numeric custom command parameter included a leading zero.
• Fixed an issue where editing a web interface action and selecting Use custom form would result in an empty form when a filter was applied to the Actions section of the web interface configurator.
• Fixed an issue where reserved HTML characters in web interface action names were converted to HTML entities when the action was saved (for example, < became &lt;).
• Fixed an issue where the default settings for the Reset password action were not saved when the Customize operation option was selected but left unchanged.
• Fixed an issue where autocomplete would not remember entered property values if creation was sent for approval rather than executed immediately.
• Fixed an issue with duplicate values in the drop-down list when configuring Idle session sign out for a web interface.
• Fixed the behavior of the Favorites panel that previously was impossible to close when a user with zero read access signed in to the web interface.

Visual issues

• Removed an unnecessary selection step when adding sections to forms and views if only one section type could be added.
• Improved the behavior of web interface wizards when using the keyboard to select elements and navigate between steps.
• Fixed an issue where top-level nodes were displayed in a different order in some web interface views, for example, when adding members to an Entra security group.
• Fixed the incorrect display name for the Common sign-in page object type that appeared when adding permissions to security roles.
• Fixed a bug where unusually long object names caused the field containing the object to extend beyond boundaries of some UI elements.
• Fixed several visual issues with long Microsoft 365 license names in the web interface configurator.
• Fixed several minor visual issues that occurred when editing specific Exchange properties or membership rules of rule-based groups on mobile devices.