Book Image

Microsoft Identity Manager 2016 Handbook

By : David Steadman, Jeff Ingalls
Book Image

Microsoft Identity Manager 2016 Handbook

By: David Steadman, Jeff Ingalls

Overview of this book

Microsoft Identity Manager 2016 is Microsoft’s solution to identity management. When fully installed, the product utilizes SQL, SharePoint, IIS, web services, the .NET Framework, and SCSM to name a few, allowing it to be customized to meet nearly every business requirement. The book is divided into 15 chapters and begins with an overview of the product, what it does, and what it does not do. To better understand the concepts in MIM, we introduce a fictitious company and their problems and goals, then build an identity solutions to fit those goals. Over the course of this book, we cover topics such as MIM installation and configuration, user and group management options, self-service solutions, role-based access control, reducing security threats, and finally operational troubleshooting and best practices. By the end of this book, you will have gained the necessary skills to deploy, manage and operate Microsoft Identity Manager 2016 to meet your business requirements and solve real-world customer problems.
Table of Contents (22 chapters)
Microsoft Identity Manager 2016 Handbook
Credits
About the Authors
About the Reviewers
www.PacktPub.com
Preface
Index

Outbound synchronization rules


As you can see, inbound synchronization rules are associated with the connector space MA that we like to import information from. Outbound synchronization is very different! Because of the differences, many people choose not to have Inbound and Outbound Data Flow Direction in the same synchronization rule.

Outbound synchronization rules are associated with each object type (or resource to be consistent with MIM Portal naming conventions). There are two ways to apply an outbound synchronization rule: using an Outbound Synchronization Policy or by using an Outbound System Scoping Filter:

Note

You can only make this choice during the creation of the outbound synchronization rule. You cannot change it once the synchronization rule has been created.

In some scenarios, you will find that it is useful to have multiple outbound synchronization rules for one external system. In those cases, you might mix the two different ways of associating the rule to the object. You...