{"id":3231,"date":"2023-11-02T09:00:42","date_gmt":"2023-11-02T16:00:42","guid":{"rendered":"https:\/\/www.microsoft.com\/insidetrack\/blog\/?p=3231"},"modified":"2023-11-07T11:25:07","modified_gmt":"2023-11-07T19:25:07","slug":"learnings-pitfalls-compromises-operations-expedition-cloud","status":"publish","type":"post","link":"https:\/\/www.microsoft.com\/insidetrack\/blog\/learnings-pitfalls-compromises-operations-expedition-cloud\/","title":{"rendered":"The learnings, pitfalls, and compromises of Microsoft\u2019s expedition to the cloud"},"content":{"rendered":"
Our expedition to the cloud started some time ago, well before moving to the cloud was a twinkle in Microsoft\u2019s eye.<\/p>\n
Yes, only a handful of us at Microsoft have been around long enough to hold coveted treasures like a 5\u00bc Windows NT release boot disk or a full set of long, shiny hair displayed on a 90\u2019s Microsoft badge. But as exciting as those early computing times and hairstyles were, I\u2019m finding what\u2019s more invigorating is the remarkable odyssey my team and I have recently embarked on as we move from on-premises datacenters into the cloud.<\/p>\n
Welcome to our blog series \u201cOperationalizing the Cloud.\u201d My team in Microsoft Digital, the organization that powers, protects, and transforms Microsoft, is the primary horizontal infrastructure group and we\u2019re responsible for ensuring our internal customers have servers, storage, and databases, all the hard-crunchy bits of hosting, to run the critical applications that make Microsoft operate internally.<\/p>\n
Who are you?<\/p>\n
You\u2019re me, only working for another company (and probably with the full set of hair that I no longer have). You\u2019re a decision maker, technical subject matter expert, or both. You have either been thinking about moving your company to the cloud or have been given the direction by management to start doing so.<\/p>\n
You\u2019ve also been told to make sure everything runs as smoothly, or better, than before. Maybe you\u2019ve already started kicking the tires with cloud, you\u2019ve got some production running and are ramping it up, or maybe you\u2019re just starting to consider all the overwhelming intricacies that a cloud infrastructure involves. You\u2019re wondering what the heck that\u2019s going to mean for your operations, the various roles for your team, and what sort of issues you\u2019re going to encounter that you haven\u2019t even thought of yet.<\/p>\n
That\u2019s where I come in.<\/p>\n
For the last seven-plus years we\u2019ve been working on this inside Microsoft\u2014we\u2019ve gone from zero resources in Microsoft Azure to nearly 80 percent hosted in the cloud. I\u2019ve been involved for most of that effort, including helping decide our direction technically and operationally and determining how our operational framework needed to change over time to support a hybrid environment. We went down some paths that we had to back out of (or are still trying to back out of in some cases). And we also had to go back to our internal customers and really listen to what they wanted, compromise, and iterate our services to enable them to get to the cloud more easily.<\/p>\n One of the foremost examples of a compromise we had to make was moving applications into the cloud in a modern way to meet pressing timelines. Ideally, if you\u2019re looking for the most efficient way to move an application, you would consider refactoring it into a microservice or cloud native architecture. However, in our case, we had some strict deadlines to meet on existing datacenters and not necessarily enough budget to invest in a massive refactor of all the applications that had to go out.<\/p>\n Because of that, we employed the popular lift-and-shift migration strategy that took our applications from systems in the on-premises to the Microsoft Azure datacenter as IaaS virtual machines. As a colleague properly illustrated: it\u2019s like taking boxes out of your garage and putting them into an offsite storage without having to unpack or rearrange them. It got the desired datacenters closed on time, and we can go back and revisit the applications over time and as budget allows.<\/p>\n As we trekked further into our expedition to the cloud, we found we needed to rethink the way we handled our management and monitoring as well as how the Microsoft Azure subscription service was delivered. We quickly embraced the agile methodologies other parts of our organization were moving to for software development and started using them for our service engineering and operations.<\/p>\n In the next few blogs, I\u2019m going to dive a little deeper into each of these processes to give you an idea of where we were and where we got to with our Microsoft Azure service, with only a few bumps and bruises along the way. Hopefully we can save you some time, and headache, as you embark or move along your cloud computing journey. Meet me back here in a few weeks and let\u2019s keep talking cloud.<\/p>\n Visit our content library for more\u00a0Microsoft Azure scenarios and datacenter transformation\u00a0content.<\/a><\/p>\n