Microsoft Identity Lifecycle Manager "2" Policy Service

Identity Lifecycle Manager (ILM) “2” provides powerful end user self-service capabilities via Office and rich administrative tools and enhanced automation for IT professionals. In addition, ILM “2” is built on a .NET and WS-* based foundation for developers to build more customized and extensible solutions. [More info….] Inclusion of the ILM-PS into the Microsoft Identity […]

Identity Lifecycle Manager (ILM) “2” provides powerful end user self-service capabilities via Office and rich administrative tools and enhanced automation for IT professionals. In addition, ILM “2” is built on a .NET and WS-* based foundation for developers to build more customized and extensible solutions. [More info….]

Inclusion of the ILM-PS into the Microsoft Identity Lifecycle Manager "2" product is the realization of a concept that started with Microsoft Identity Lifecycle Manager 2007.  Prior to the release of Microsoft Identity Lifecycle Manager 2007, the Synchronization Engine component was the entirety of the product known as Microsoft Integrated Identity Server (MIIS).  At that time MIIS was, and still is, fantastic at what it does:  synchronize, provision, and deprovision data between heterogeneous data sources.  However, managing the lifecycle of this data was done externally through the external data stores.  In other words, the Synchronization Engine would only perform synchronization, provisioning, or deprovisioning actions when there was a data change in an external store to which it was connected through a Management Agent (MA).  Further, deploying and configuring of the Synchronization Engine was a complex task that often required contracting experts, especially if an enterprise's deployment required the authoring of custom one or more custom MAs.

Full Article