-
Title
Enhancement Request - Active Roles and WDAC Enforcement Guidance -
Description
Customers running Active Roles in environments with Windows Defender Application Control enabled may see execution-related issues if WDAC/Code Integrity blocks required runtime components.
Active Roles may start successfully and connect to Active Directory, but workflows, policies, scripts, or automation tasks may fail if components such as .NET, PowerShell, or dynamic compilation tools are restricted.
-
Cause
An enhancement request (711832) has been created detailing the feature above.
Active Roles relies on Microsoft .NET, PowerShell, and dynamic runtime execution for several product functions. If WDAC blocks these components, Active Roles functionality can be impacted even though the service itself appears healthy.
-
Resolution
An enhancement/documentation request has been created for Development to publish official vendor guidance for Active Roles under WDAC enforcement, including:
- Expected behavior when WDAC is enabled
- Supported WDAC configuration guidance
- Required allowances or exceptions for Active Roles, .NET, PowerShell, and trusted scripts
STATUS
The product team will evaluate the request, and this feature may become available on a future release of the product.
Please refer to this article for updates or contact support referencing the Enhancement Request ID: 711832.
-
Change Request
711832 -
Additional Information
There are no guarantees that this specific enhancement request will be implemented in a future release. For more information regarding our Enhancement Request policy, refer to our Global Support Guide on the Support Portal at: Guide to One Identity Support.