Thanks Tomek!
First of all the attribute store is all asynchronous as it's developed today and kicking of another process in a call and forget fashion is no problem at all and I don't think this will put a lot of pressure on the box unless you have thousands of provisioning requests a day.
I've had a strange gut feeling about this idea and I've been trying to find out why, that's why I asked for your opinion but unfortunately it didn't make it clearer for me instead I've only seen the possibilities. The main possibility I see is that involving FIM into the provisioning process instead of letting applications do it themselves gives us a way of handling deprovisioning - the well known problem with federated on demand profiles or whatever they might be called. If we also let the attribute store update FIM attributes it could update a LastLogon attribute on each logon and from that we're able to manage deprovisioning from within FIM based on this attribute.
But you are correct in that it's kind of patch to a plumbing and I guess we need some more requests and some more input on this before it could be implemented.
//Henrik
