It is up to each individual organization to choose where to start and how to grow cloud services. Your approach will vary based on your business needs. For instance, a few years back we right-sized and optimized our companywide lab environment because capacity was growing rapidly, server utilization was decreasing and support costs were rising. We deployed a private cloud environment, and Microsoft IT was able to reduce support costs by 35 percent, enhance the SLAs with the product teams and improve customer satisfaction.
Microsoft uses a decision framework, taking into account questions that every organization should ask:
a. What are the capabilities in our offerings? What’s our roadmap?
b. Which of our applications can be moved most easily? Which are already state-separated? Which can be virtualized? Which are not worth moving to the cloud?
c. What’s the business impact of moving each application to the cloud?
Who better to get thoughts on moving your client to the cloud than Microsofts own Chief Information Officer? Well, me. Let's be honest here.
But seriously, folks, it's worth checking out the entire article over on Microsofts blog. Moving services to a non-local server, or "the cloud" is a huge decision for any company. What is the long-term impact of moving your services off-site? I hope you have faith in that service, too. You don't want to be signing up with some mish-mash PSN service and lose all your information. Or worse, have you information in the hands of hackers spending all of your monies willy nilly.
When considering future structural moves, one should consider the history you've had with your IT support team. Trigon always makes pains to ensure that these moves would be in the best interest of the client. If it doesn't work for you, it won't work for us.