SCRUM template follows some of SCRUM terminology and artefacts. You have sprints instead of iterations, you have user stories instead of requirements, tasks, burndown charts etc. But in my opinion TFS is hard to use because it is not very productive.
We are using similar non MS template for Visual Studio TFS 2008. During my first SCRUM project we used directly TFS and Excel to collect user stories, to prepare tasks etc. It was extremely slow. Just creating tasks for 4-5 developers and 4 weeks sprint (I will never use such long sprint again) took me always about two days. Such a waste. Moreover there was no build in support for printing cards for taskboard. Another disadvantages of non MS template (not sure if this is the same for MS one) is that each reported bug is immediately added to product backlog (it is new user story), there is no way to collect constraints, user stories don't have predefined field for acceptance criteria and tasks don't have field for real time spent on task completion (good for retrospective of estimates). Fields can be probably added if you have TFS under your control but it is not my case.
I still have to use TFS (company policy) but I'm working with user stories and task as much as possible outside the TFS - pen and paper works best. Still TFS is good for tracking sprint progress and automatically generated burndown charts but you have to find good balance between number of tasks, complexity of tasks and sprint length.
