Federated customers are those that often find themselves with too many cooks in the kitchen. In addition, business and IT may considerably differ in opinion about the value of integration, consolidation, and collaboration. As such, federated infrastructures push the limits of flexibility on Microsoft software, often negating best practices in favor of protecting fiefdoms, or more importantly, jobs. Federated infrastructures are quickly identified by their unnecessary complexity, customer pride in that complexity, split responsibility among groups that oppose one another, and a lack of service level agreements or accountability.
Although I might poke fun of such organizations, federations are part of life, particularly in governments. This blog is a journal of findings, recommendations, and musings that I encounter every day, working with federated customers. The goal is not so much to point out the flaws of such systems, but to show that Microsoft software can be and has been deployed under some of the most extreme conditions. With such deployments, however, come problems and this blog allows me to share those experiences with you in hopes of reducing your own times-to-resolution.