This article describes the deprecated features of Microsoft Identity Manager 2016 SP2. Where the feature is still present in Microsoft Identity Manager, it is still supported. Features are not recommended for new deployments, as they may be removed in a future hotfix or service pack release. For developers, we recommend not utilizing deprecated features in any new applications or solutions.
For more information on the new support options for MIM, see support options for Azure AD Premium customers.
Microsoft does not recommend customers start new deployments of the Microsoft BHOLD Suite components. Existing deployments of BHOLD will continue to be supported. Azure AD now provides access reviews, which replaces the BHOLD attestation campaign features, and entitlement management, which replaces the access assignment features.
Service and Portal
|Programmatic Configuration of sync||Web Service configuration interface(ma-data and mv-data)||The ability to configure the MIM synchronization service, through MIM service web service, may be removed in a future hotfix or service pack.|
The following MAs have been removed in MIM 2016: 1. MA for FIM Certificate Management 2. MA for Lotus Notes 3. MA for SAP R/3 The Lotus Notes and SAP R/3 MAs have been replaced with new connectors. For more information, see Latest Connector Version Release History & Download.
The ECMA1/XMA extensibility framework has been replaced by ECMA 2.0. Updating existing ECMA1 management agents with ECMA2.0 connectors is required.
|Management Agents||Running Connectors out-of-proc||The synchronization service will always call the connector in the same process. It is the responsibility of the connector to start and manage the other process.|
|Management Agents||Configure partition display name||This option was only used to provide an alternative name for a partition in the WMI interfaces.|
|Run profiles||Combined profiles||The combined profiles delta import/sync, full import/delta sync, and full import/sync may be removed. Use run profiles with two steps instead.|
You should keep combined run profiles only in environments where the performance would be impacted by a large number of existing disconnectors.
|Attribute Precedence||Multi- mastery/equal precedence||Equal precedence may be removed. You should configure manual precedence instead. You can continue to use this feature if your environment has a FIM Service management agent deployed. This management agent does not provide manual precedence to avoid export-not-precedent for declarative provisioning.|
|Join Rules||Join on “Any” object type||All join rules should explicitly define the metaverse object type they are trying to join to.|
|Attribute flows||Unselect “allow nulls” for exported values||“Allow Nulls” will always be selected, so make sure that you have “Allow Nulls” selected in your current environment.|
|Attribute flows||“Do not recall attributes”||Attributes will always be recalled, which is the best practice.|
|Rules Extension||Running metaverse and ma rules extension out- of-proc||The metaverse and attribute flow rules will run in the same process as the synchronization engine.|
|Rules Extension||Transaction properties||Avoid passing data between inbound, provisioning, and outbound synchronization using this utility class.|
|Rules Extension||ExchangeUtils: Create55* methods||The methods to create objects for Exchange 5.5 servers may be removed.|
|Interface||Mms_Metaverse||All ClmUtils class members may be removed in a future hotfix or service pack.|
Learn more about:
- Microsoft Identity Manager is still closely related to its predecessor, Forefront Identity Manager. If you still use FIM, or want to refer to additional documentation, take a look at the FIM 2010 R2 Documentation Roadmap.
- Topology considerations for deploying MIM This article introduces multiple deployment topologies that you may consider implementing.
- Capacity planning guide You can use this guide, along with test environments, to understand the appropriate scope for your deployment.