Introduction
This update fixes strong-name validation failures (0x8013141A) that could prevent the MIM Service and Portal package in build 4.7.13.0 from installing, and that could prevent Synchronization Service Key Management from generating or exporting encryption keys. It also includes all the fixes and improvements from hotfix rollup package build 4.7.13.0 (KB5134305). For more information, see the “Issues fixed and improvements added in this update” section.
We recommend that all customers apply this update to their production systems. For information about obtaining and installing the update, see the Microsoft Download Center and Prerequisites sections.
Update information
Microsoft Download Center
A supported update is available from the Microsoft Download Center. We recommend that all customers apply this update to their production systems.
Download Update for Microsoft Identity Manager 2016 (KB5136283)
Prerequisites
To apply this update, install the following prerequisites: Microsoft Identity Manager 2016 Service Pack 3 (SP3) build 4.7.6.0, 4.7.9.0, or 4.7.13.0. This hotfix applies to all three builds and brings them to the same version number, 4.7.15.0.
Before installing this update:
- Verify the currently installed MIM version and build number of each MIM component. If an earlier attempt to install build 4.7.13.0 (KB5134305) failed and rolled back, that component remains at its previous build.
- Review the components included in this update to select the files applicable to your environment.
- Back up the MIM databases and configurations.
- Plan for any required service interruptions or system restarts following installation.
Important: Customers upgrading from MIM 2016 SP3 should verify the supported upgrade path and any additional installation requirements before applying this update.
Important: Before applying this update, customers using MIM 2016 SP2 should upgrade to SP3 build 4.7.6.0 or 4.7.9.0. Follow the supported upgrade path in Upgrade Microsoft Identity Manager 2016 From Service Pack 2 to Service Pack 3.
Known issues
Issue 1: Outbound synchronization rule attribute flows that use IIF can fail
After you install MIMSyncService_x64_KB5134305.msp, outbound synchronization rule attribute flows that use the IIF function can fail during synchronization.
This issue can occur when an IIF expression uses a custom condition, such as Eq(<attribute>,"<value>"), a metaverse attribute as the true value, and a string constant as the false value.
When this issue occurs, FunctionLibrary.dll can throw Microsoft.MetadirectoryServices.FunctionEvaluationException with error 0x80230913 (E_MMS_SCHEMA_ATTRIBUTE_NOT_FOUND). The Application log can also contain FIMSynchronizationService Event IDs 6300 and 6312 with the same error. The error doesn't identify the affected attribute.
Restart requirement
You must restart the computer after you apply the add-ins and extensions package (MIMAddinsExtensions_x64_KB5136283.msp or MIMAddinsExtensions_x86_KB5136283.msp). You might also have to restart the server components.
After installing this update, it's recommended to have users clear the browser cache on all browsers that access the MIM Portal.
File information
The global version of this update has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it's converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
| File name | File size | Date | Time |
|---|---|---|---|
| MIMAddinsExtensions_x64_KB5136283.msp | 16,670,720 | 11/12/2026 | 21:53 |
| MIMAddinsExtensions_x86_KB5136283.msp | 8,921,088 | 11/12/2026 | 21:53 |
| MIMAddinsExtensionsLP_x64_KB5136283.msp | 9,326,592 | 11/12/2026 | 21:53 |
| MIMAddinsExtensionsLP_x86_KB5136283.msp | 3,321,856 | 11/12/2026 | 21:53 |
| MIMService_x64_KB5136283.msp | 187,543,552 | 11/12/2026 | 21:53 |
| MIMServiceLP_x64_KB5136283.msp | 19,300,352 | 11/12/2026 | 21:53 |
| MIMSyncService_x64_KB5136283.msp | 51,699,712 | 11/12/2026 | 21:53 |
Issues fixed and improvements added in this update
This update fixes strong-name validation failures in MIM 2016 SP3 components. When the issue occurs, the affected component reports “Strong name validation failed. (Exception from HRESULT: 0x8013141A)”, typically as a System.IO.FileLoadException or a System.Security.SecurityException. These failures can occur on SP3 build 4.7.6.0 or 4.7.9.0, before or after build 4.7.13.0 is applied.
MIM Service and Portal
Fixed an issue in which the MIM Service and Portal package in build 4.7.13.0 (MIMService_x64_KB5134305.msp) fails to install with Windows Installer error 1603, and the installation rolls back. The verbose installation log shows a strong-name validation failure (0x8013141A) for the Microsoft.IdentityManagement.PasswordResetCAs assembly during the GetIISVersionFromRegistry custom action.
- This issue occurs because the assembly isn't correctly strong-name signed. This update includes correctly signed assemblies, so the MIM Service and Portal package installs successfully and brings the MIM Service and Portal to build 4.7.15.0.
Microsoft Graph support for Exchange Online
Added support for Microsoft Graph API as an alternative to Exchange Web Services (EWS) for MIM Service email functionality with Exchange Online.
Microsoft Graph uses application-only OAuth authentication to support MIM email notifications and the processing of approval and rejection responses.
This functionality provides a supported replacement for the existing EWS-based integration as Microsoft retires EWS access in Exchange Online.
Microsoft Graph integration is optional and must be explicitly enabled. Installing this update doesn't automatically migrate existing EWS configurations or change the MIM Service's current email integration.
Existing EWS-based configurations can continue operating where EWS access remains available. Customers using Exchange Online should plan to transition to Microsoft Graph before their existing EWS access is discontinued.
Important: Customers who intend to use Microsoft Graph must configure the required Microsoft Entra application permissions and enable the Graph-based mail integration. Refer to the Microsoft Graph configuration guidance for MIM Service before making this change.
ExportConfig and RCDC file downloads
Fixed a regression introduced in MIM 2016 SP3 that could cause ExportConfig and Resource Control Display Configuration (RCDC) file downloads to fail or time out when initiated through the MIM Portal.
The issue occurred when portal cache validation and session or identity context handling incorrectly rejected otherwise valid download requests.
This update corrects the affected download handling behavior, allowing configuration exports and RCDC file downloads to complete successfully without being incorrectly rejected during request validation.
Outlook 2024 compatibility
- Added support for the Microsoft Identity Manager (MIM) Outlook client add-ins, enabling their use with Microsoft Outlook 2024 for processing MIM workflow approval, rejection requests, and notification delivery.
MIM Synchronization Service memory consumption
Fixed an issue in which Synchronization Service Key Management (miiskmu.exe) can't generate or export Synchronization Service encryption keys on MIM 2016 SP3 build 4.7.9.0. Key Management either doesn't start, or it starts and then fails in mcrypt after you enter the service account credentials. In both cases, it reports a strong-name validation failure (0x8013141A). The System log might also contain Event ID 7009, which reports a timeout while waiting for the Microsoft MIM KeyProtectService service to connect. Applying build 4.7.13.0 doesn't resolve this issue.
- This update corrects the strong-name signing of the affected Synchronization Service components, so Key Management can start and complete key generation and export operations.
Fixed an issue affecting the MIM Synchronization Service that could result in excessive memory consumption during synchronization operations following an upgrade to MIM 2016 Service Pack 3 (SP3).
In affected environments, memory utilization could increase significantly during synchronization run profiles and remain elevated after the operations completed, rather than returning to expected baseline levels.
This behavior could contribute to degraded synchronization performance, increased resource utilization, and potential service instability.
This update includes memory management improvements intended to correct the excessive memory consumption associated with this issue.
Synchronization Rule attribute flow — IsPresent()
- Fixed an issue affecting the IsPresent() function when used in a MIM Service Synchronization Rule attribute flow definition. When the function evaluated an attribute, whose value was null, the associated Management Agent could generate an AttributeNotInclusionListException, even though the attribute was included in the Management Agent configuration.
- This update corrects the behavior so that IsPresent() can evaluate null attribute values without triggering this exception solely because the attribute value is null.
Restored the Rules Extension logging namespace.
Resolved incompatibility issues affecting the following utility tools after upgrading to MIM 2016 Service Pack 3 (SP3), caused by the framework upgrade from .NET 3.5 to .NET 4.6.2.
Synchronization Service Key Management
Microsoft Identity Integration Server (MIIS) Warm Standby Activation Utility
Connector Space Export Utility
Management Agent Export Utility
Management Agent Packager Utility
Server Configuration Export Utility