If all you know is Microsoft, then that's all you can do, and the organization's technical direction will almost certainly model that initial decision.
However, if you have the luxury of choice -- and I think most people do -- I'd advise against it. The short and long-term costs of Microsoft lock-in are decidedly "non-trivial". The considerable investment in staff, licenses, and technologies make it very difficult to migrate to a non-Microsoft stack in the future.
The converse also applies. Granted, a competent engineer can learn anything, however you're initially inclined to pass on them because of the associated ramp-up time.
In my experience, you're entirely locking out engineers who use Linux and Mac OS X when you move to a Microsoft stack, but you're not necessarily locking out Windows engineers when you use a cross-platform stack.