So if not functional reasons, why should we care about Share Point 2013? After all there’s no point making things more complicated than necessary, right?It all comes down to one thing, and that is Windows Server 2012.
However in the journey to the cloud this model is effectively being deprecated in favour of the loosely coupled, off box approach to customization (a.k.a. Of course aligning such disparate strategy across wildly different release cycles is impossible, and it’s both unfeasible and unnecessary for the FIM Portal to be re-implemented at this stage in line with the new world order.
The harsh reality is that Share Point 2013 in and of itself offers no value whatsoever in terms of functionality for the FIM Portal.
This is covered extensively elsewhere and should be familiar to you.
However the accounts guidance for Share Point as it relates to FIM is weak.
FIM 2010 R2 SP1 introduces support for Windows Server 2012, and this is something we definitely want to leverage for our Identity Management platform.
The problem is however that Share Point 2010 doesn’t run on Windows Server 2012 yet, for that we need to wait for Share Point 2010 Service Pack 2.
For many years this approach was promoted by Microsoft and leveraged across many products.
Instead of the FIM team building out their own hosting infrastructure and site plumbing, they built a bunch of customizations on top of Share Point.
As we know the FIM Portal is based upon Share Point and installs into an existing site collection, thus Share Point is a pre-requisite for the FIM Portal.