This post was co-authored by Thomas Maurer, Senior Cloud Advocate, Azure.

Tailwind dealer1 is a retail company looking to adopt Azure as part of their IT strategy. The IT team is familiar with deploying the on-site infrastructure and is currently exploring what to do to run the workloads on Azure. In this blog post we will walk you through the Tailwind Traders experience to help run the workloads on Azure Cloud adoption framework and Azure Landing Zone Instructions.

What are landing zones?

Regardless of where you host your workloads, there are certain components that you will need to support those workloads. When you think of the local world, when starting a new data center, you need to make sure you have power, cooling, networking, and physical security before you can actually begin installing your servers or workloads. When you host your workloads in the cloud, there are certain things you need to install on your servers or workloads, such as: B. Network, surveillance, identity and access management, and subscription and tenant creation. When moving workloads to the cloud, you should also think about compliance and security requirements, as well as your disaster and backup plans. You don’t always have to be there from the start, depending on the company’s needs, but thinking about them can certainly make your journey a lot smoother. And that is exactly a landing zone. It helps you think about and build the foundation you need to host your workloads on Azure.

Tailwind Traders looks forward to learning more about landing zones and how to design and implement a suitable environment in which to run their workloads on Azure.

Selection of the landing zone

Upon examining the landing zones, tailwind traders found that there were multiple options. Start small and expand, Corporate scale, and Partner landing zones.

The launch / expansion landing zone is a great place to start for businesses just starting their cloud journey and needing a hand of leadership but not yet sure where their journey will take them.

The enterprise-scale landing zone is designed to help organizations find a quick deployment (6 to 8 weeks) and meet immediate security or compliance needs for their workloads.

Partner landing zones are offers from system integrators (SI), managed service providers (MSPs) or independent software providers (ISVs) who have developed a landing zone solution based on their extensive experience and the methods contained therein Cloud adoption framework.

Pick the right one

Tailwind Traders is excited to take the Azure journey and is excited that using landing zones is helping them make that journey faster. However, they are concerned about which wrong landing zone they will choose and what effect it will have on their trip in the longer term. If they choose the wrong landing zone, they could end up in the scenario of having to restart, or take longer to run than planned, or even run into qualification issues because they weren’t ready for some of the implementation techniques.

Tailwind traders need to think about a few important things before choosing a landing zone. Answering these important points can help you find the correct landing zone.

You should think about theirs Operating model;; How does the organization run its IT department? Are you running a decentralized model with each team focused on a workload or a single area? Maybe they’re running a traditional centralized operating model where a central IT team controls everything. Or they run an enterprise operating model where common utilities are shared, but departments or teams have some autonomy over specific workloads or areas. Knowing your current operating model and where you want to be when moving to the cloud can have a significant impact on the landing zone you choose.

You have to think about it too how fast they want to implement workloads in Azure. Is this project time sensitive and does it have to be delivered by a certain date? Understanding project delivery times can be key to the landing zone route. Tailwind traders go down.

Security, governance. and compliance requirements or requirements are also something they need to discuss and fully understand. Are there any regulatory compliance guidelines that must be in place? You don’t need to define complete safety and governance guidelines, but you definitely need to understand which direction you want to go and how it will affect your landing zone selection and design.

And the last thing to consider is Deployment Methods for the landing zone and workload. Tailwind traders should think about how they want to provision their workloads, do it manually, or take an automation approach. Again, you don’t necessarily need to know the full answer to this, but understanding the direction you want to go will help you choose the landing area.

If you already have some workloads in the cloud that may have been put there due to need or shadow IT, you may not have the luxury of starting from scratch like at Tailwind Traders. To help you in your journey, things like that Cloud Journey Tracker can help you understand where you are and where to look in the Cloud Adoption Framework for further guidance.

It is possible to select the wrong landing zone. However, once you understand your company’s operating model, project schedule, security, governance, compliance, and deployment needs, hopefully you need to choose the right one to begin your cloud journey.

We’ll be exploring Tailwind Traders and their cloud adoption journey in future blog posts. However, if you want to learn more about the Cloud Adoption Framework and how it can speed up your cloud adoption journey, then Azure Enablement Show is a great place to start.

1Tailwind Traders is a fictional company that we refer to in this blog post to illustrate how companies can leverage the Cloud Adoption Framework in real-world scenarios.


Source link

Leave a Reply