Sign in
Microsoft.com
 
Resources for IT Professionals
 
 
 
Resources for IT Professionals > Forums Home > Identity Management Forums > Identity Lifecycle Manager > Users and Contacts
Ask a questionAsk a question
Search Forums:
 

AnswerUsers and Contacts

  • Thursday, October 29, 2009 12:09 PMAnu Melkote Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    I am trying to wrap my head around on how to efficiently handle provisioning of contact objects.

    In one test scenario, I created a separate contact object type in FIM portal bound with a subset of attributes I wanted associated to this object type and established flows to contact object type in MV. It could be done but I am not so sure that this is the way to go. Suggestions?

    A specific use case that I am testing - I want to be able to create users by default as mail enabled contacts in exchange. After AuthZ workflows in FIM have completed successfully, I want to move these contacts to users. Apply rules and create a mailbox for the user or keep the user to being mail enabled.... and so and so forth.

    So to flip between user and contact states what's the best design approach -use distinct object types in FIM or create a complex set that will drive provisioning of user vs contact or ....?

    Thanks.

    Thanks!

    Anu
     

Answers

All Replies