Patch Version 11.1.7 Released

Want the full details? Click the link below!

Overview

The following list contains a comprehensive overview of the updates and fixes released on 28 May 2026. This release includes improvements across Entra ID integration, Dynasty management, Smart Groups, the self-service portal, notifications, and installation.

Announcement: Deprecation of Directory Manager as an Identity Provider

Netwrix Directory Manager has historically supported use as an Identity Provider (IDP), enabling applications to authenticate users directly through Directory Manager.

We are announcing the planned deprecation of this capability. While no end-of-life date has been set at this time, we intend to remove Directory Manager as a supported Identity Provider in a future release. We are making this announcement now to give customers sufficient time to plan and transition to an alternative Identity Provider.

Customers currently using Directory Manager as an Identity Provider should begin evaluating alternative IDP solutions. We recommend reviewing your authentication architecture and identifying a replacement ahead of future release guidance.

Further details, including a confirmed timeline and migration guidance, will be communicated in advance of any change taking effect. If you have questions about how this may affect your deployment, please contact Netwrix Support.

Bug Fixes

Entra ID and Microsoft 365

Description Case #
Improved Entra ID replication reliability, ensuring consistent synchronization of users, groups, and OUs without replication stalls. 425303
Resolved an issue causing failures in Entra ID identity store operations following a product update. 434985
Resolved an issue where Teams channels created in Microsoft 365 were not being replicated or displayed in the portal’s Team Channels tab. See known limitation note below regarding Teams channel replication behavior. 416346
Resolved an issue where distribution list owner assignments were failing and owner changes were not syncing correctly in Entra ID environments. 434844
Resolved an issue where owners and members could not be added to distribution lists through the self-service portal. 435622
Resolved an issue where the Owners field was not displaying existing owner data when viewing or editing a group. 435656
Resolved an issue causing intermittent group creation failures through the portal. [PENDING: confirm whether this is Entra ID-specific or affects all identity stores] 437721

Dynasties

Description Case #
Resolved an issue where dynasties were deleted when an update operation was performed, rather than being modified as intended. 433207
Resolved an issue where intermediate groups in a managerial dynasty could be incorrectly removed in Entra ID environments. 412903
Resolved an issue causing unintended deletion of child groups during dynasty updates in Entra ID environments. 398148

Smart Groups

Description Case #
Resolved an issue where SQL queries in ODBC-based Smart Groups were being unintentionally modified when opened or edited. 420498
Resolved an issue where the Query Designer could incorrectly revert to a default view, causing saved Smart Group queries not to display correctly. 420703
Improved Smart Group scheduling reliability, resolving an issue where schedules could stop updating group memberships after the initial run. 369063
Improved Smart Group scheduling notifications to more accurately reflect the outcome of successful updates. 411930

Notifications

Description Case #
Improved denied request notifications so that requester and approver names display consistently with approval notification emails. 410827
Resolved an issue where scheduled job notifications were not respecting configuration settings, resulting in failure alerts being sent when no failure had occurred. 396486

Installation and Infrastructure

Description Case #
Resolved an issue preventing the product from being installed without an internet connection. 424913
Improved prerequisite handling for .NET runtimes, preventing unnecessary installation of older versions when a supported newer release is already present. 420499
Updated underlying components to address an ASP.NET Core HTTP request/response smuggling vulnerability (CVE-2025-55315). 420416
Resolved an issue where credentials could surface in administrative log files. 412264

New Platform Support

Added support for Windows Server 2025.

Known Limitations

Teams Channel Replication

Teams channel replication is disabled by default and does not affect standard replication performance.
If enabled, the following occurs on each replication cycle:

  • Directory Manager queries Microsoft Graph for Teams channel changes
  • Microsoft Graph does not include Teams channel additions, removals, or modifications in delta query results — this is a current limitation of the Microsoft Graph API
  • Because incremental change detection is not available for this object type, Directory Manager cannot determine whether changes have occurred and must retrieve all Microsoft Teams objects in full
  • All Microsoft Teams objects are replicated regardless of whether any changes have been made

This behavior is governed entirely by the Microsoft Graph API and is not a limitation of Directory Manager. Microsoft has not provided a mechanism for delta-based Teams channel change detection at this time.
Customers who enable Teams channel replication should expect an increase in replication time proportional to the number of Teams objects in their environment.

Need help with this update?

There are many different ways to get help with our products!

Situation Action
If you feel the product is broken and not working as intended… Contact Support
If you have a question you’d like to ask other experts… Create a discussion in the community: Directory Manager > Discussions & Questions
If you have a feature request… Let our product team know directly: Directory Manager > Ideas
If you have something cool to show… Show everyone what you built: Directory Manager > Show & Tell

What are your thoughts?

We are always happy to hear from our users on what you like, and what you hope to see in the future. Please, share your thoughts below!

Looks like a great update I’m excited to deploy. Do you have Exchange Subscription edition on the road map for support?

Thanks for raising this James, it’s a good question and something we’re starting to hear more frequently as customers evaluate their Exchange roadmap options.

At the moment, Exchange Subscription Edition is not formally listed as a supported messaging platform for Directory Manager. Current documented support covers Exchange 2010 through Exchange 2019.

That said, Microsoft has positioned Exchange SE as a continuation of Exchange 2019 rather than a completely new platform. The underlying architecture, protocols, and management model remain largely aligned with Exchange 2019, so from a technical perspective we would not necessarily expect major behavioural differences. However, Exchange SE has not yet gone through formal validation or certification with Directory Manager.

Exchange SE support is currently being tracked as a platform support consideration. If this is important to your planning, adding your vote through the Ideas Portal would help us prioritise it:

Also, if you’re actively planning an Exchange SE migration, any detail you can share around timelines or deployment plans is genuinely useful input for product planning and support prioritisation.

Dave

2 Likes

I did just want to mention that 2019 and everything before is end of life. We were forced to upgrade to Exchange SE do to this for compliance reasons. So, timeline wise I would hope that you have this on the road map asap. Exchange Server 2019 and 2016 End of Support Roadmap - Exchange | Microsoft Learn

1 Like