Looking at the BHOLD FIM Provisioning guide here: http://technet.microsoft.com/en-us/library/jj134098(v=ws.10).aspx at the end in the "Next Steps" it says to create the four SQL MA's. I created the four sql MAs linking to the tables in the technical reference, but I don't see any other details regarding any synchronisation rules I need to configure or attribute flows? Seems like a lot is missing from this documentation, or I may just be missing something. Can anyone shed some light on the SQL MAs and the rest of the configurations steps to complete the install of the BHOLD FIM Provisioning?

Hi Paul, You don't actually need 4 MAs, you just need 3. I do it like this: BHOLD OU MA - provisions OUs to FIMOrgUnit. Check out the table structure to see what it needs, basically an OU needs a name and a parent for BFSS to create a hierarchy BHOLDEmployees MA - provisions employees to FIMEmployee. Again, check out the table structure to see what attributes are needed. BHOLDAuthorizations - provisions groups and users to tblObjects and reads memberships of groups back in again using tblReferences as the multi-value table. I then use classic provisioning extensions and simple attribute flows to populate the basic attributes needed by each table. If I get the time I will try and get this into a blog post or something. Cheers DaveDave Nesbitt | Architect | Oxford Computer Group

Thanks Dave. So you don't use any synchronisation rules within the FIM Portal? it's all extensions and attribute flows direct on the MA?

You could use Portal sync rules - I just prefer to use classic methods for some tasks. I don't have to think about EREs, MPRs and Workflows, I can debug in Visual Studio, use source control for my code, deploy .dlls into production and can test without having to export to the FIM Portal first. Call me an old unreconstructed MIIS guy if you like ;)Dave Nesbitt | Architect | Oxford Computer Group

Fair enough. I always worry about going too custom and the next guy that comes along won't know what they're looking at :)