{"id":9233,"date":"2024-12-22T10:06:17","date_gmt":"2024-12-22T18:06:17","guid":{"rendered":"https:\/\/www.microsoft.com\/insidetrack\/blog\/?p=9233"},"modified":"2025-02-04T20:44:59","modified_gmt":"2025-02-05T04:44:59","slug":"microsofts-cloud-centric-architecture-transformation","status":"publish","type":"post","link":"https:\/\/www.microsoft.com\/insidetrack\/blog\/microsofts-cloud-centric-architecture-transformation\/","title":{"rendered":"Microsoft’s cloud-centric architecture transformation"},"content":{"rendered":"
Here at Microsoft, we\u2019re building our\u00a0systems in the cloud to be agile, resilient, cost effective, and scalable\u2014this allows us to be proactive and innovative as we transform our IT and business operations. Microsoft Azure\u00a0resides\u00a0at the core of our architecture, and we\u2019re using the platform to automate our processes, unify our tools, and improve our engineering productivity. We\u2019re working toward a process driven by user experience, which changes the way we provision and manage our IT infrastructure.<\/p>\n For us, Microsoft Digital, the organization that powers, protects, and transforms the company, a modern cloud-centric architecture is foundational to our digital transformation. To fuel that transformation, we\u2019re building integrated, reliable systems, instrumented for telemetry, to gather data and enable experimentation. To learn more about how we\u2019re transforming, refer to Inside the transformation of IT and operations at Microsoft<\/a>.<\/p>\n Microsoft Azure is now the default platform that our IT infrastructure is built upon. Several years ago, Microsoft Digital created a vision for moving from on-premises datacenters to Azure as the \u201cfirst and best customer\u201d of our cloud services. We examined our infrastructure to understand usage practices and how we could best support application teams via Azure subscriptions and connectivity options. We reviewed on-premises datacenter assets and developed schedules to migrate or retire the assets and to close multiple datacenters.<\/p>\n Our leadership established plans at the strategic level to move applications, which trickled down to individual cloud migration and adoption plans for each part of the organization. Our cloud-centric approach thus created a functional and flexible platform for our services and processes.<\/p>\n We\u2019re using Microsoft Azure to enable a self-service model for users of the platform\u2014providing robust telemetry and reporting capabilities via Microsoft Azure Monitor and Application Insights and using Microsoft Azure ExpressRoute to facilitate enterprise-level connectivity to the cloud from our facilities and networks.<\/p>\n We\u2019ve moved more than 93 percent of our on-premises infrastructure to the cloud, and we\u2019re assessing our strategic initiatives around our cloud efforts. We\u2019ve fulfilled our goal of moving out of the datacenter. However, many services moved from virtual machines (VMs) running in a datacenter to infrastructure as a service (IaaS) VMs running in Microsoft Azure with very little change to those services. We thus recognize the opportunity to further optimize our presence in the cloud by creating more-refined and targeted strategic initiatives both for the company itself and as examples for external customers.<\/p>\n We need to modernize our application and service portfolio to take advantage of capabilities that were previously unattainable because of datacenter and support constraints. We need to examine how we manage our data and work toward a strategy that separates data from compute resources. We need to examine open-source big data platforms, event processing, other modern services that we can more effectively scale. Policies should enforce required controls for all configurations to improve safety regardless of the network involved. We also need to continue embracing modern engineering practices and pipelines and Microsoft Azure DevOps methods of managing services. We\u2019re capturing the transformation of cloud-centric architecture in the following investment areas:<\/p>\n As our services move to these modern designs, our architectures need to evolve. We need to build our solutions to adopt the advantages of Azure and to adapt as those advantages change and grow. We need to clearly understand that Zero Trust efforts will change how users access our solutions. Our network postures and zonal controls need to adapt as well. \u201cInternet first\u201d should be the goal of all solutions. We need to implement the governance of all corporate resources\u2014regardless of their network environments\u2014and recognize that user identity and data are the critical resources to keep under the proper controls. Through this continued transition to a more cloud-centric architecture, we need to remain cost effective and create clear guidance on how to transform from VMs and on-premises solutions to modern solutions.<\/p>\n Deploying workloads to the cloud introduces the need to develop and maintain trust in the cloud to the same degree that we have in our existing datacenters. In this model, we can apply isolation policies to help achieve the required levels of security and trust. To use the cloud as our trusted platform for our new cloud-centric architecture, we need to invest in plans for multiple areas:<\/p>\n The following sections detail the specific investments that combine to fulfill these requirements.<\/p>\n The Microsoft Azure fabric is a collection of programming interfaces that allows application engineering to interact with the underlying services and infrastructure. On one end of the spectrum is an application engineer connecting to the fabric and running a script to provision a VM. On the other end of the spectrum is automation connecting to the fabric, pushing data into a service, merging this data with external data sources, performing an analysis, and then publishing this data to a user interface for consumption.<\/p>\n The role of the IT infrastructure provider will be to supply security-enhanced, flexible, and reliable hosting in our corporate fabric for applications and data (whether in our private or our public cloud). From the perspective of an application engineering team, provisioning infrastructure will appear a lot like updating templates and running scripts that land code and data in VMs; in containers; or in purpose-built, platform as a service (PaaS) solutions, like Microsoft Azure SQL Database. The role of the core hosting provider will be to present a flexible, reliable, and safer fabric to these teams for interaction with their templates and scripts.<\/p>\n The role of the infrastructure team will be to enable frictionless and security-enhanced access to a fabric of APIs. A subscription will enable access to the scope of computing capacity that the subscriber can use. Subscriptions will connect to on-premises environments for hybrid scenarios, to added subscriptions for scaling out, and to third-party services for specialized processing. Our infrastructure team will need to do all of this in a security-enhanced manner, use standardized methods and building blocks, and maintain fiscal effectiveness. The team will need to conduct these interactions in a way that Microsoft deems appropriate.<\/p>\n The role of the fabric administrator will be to provision this fabric through subscriptions and to help ensure that each subscription has the required capacity and connectivity to meet the demands of the application in a security-enhanced and fiscally responsible manner. The fabric administrator will:<\/p>\n In many ways, our IT organization will function like a managed service provider or Azure service broker. The Microsoft Azure product group recognizes that a necessary gap exists between corporate application engineering and Azure services. We refer to this addressable gap as the corporate context. The corporate context<\/em> consists of the specific company\u2019s policies, standards, identity scenarios, and network connectivity scenarios. It\u2019s the role of the service broker or fabric administrator to apply the corporate context to the fabric to enable loosely moderated consumption by application engineering teams.<\/p>\n Within the IaC and Microsoft Azure DevOps area, we\u2019re building a more agile and flexible process for developing and deploying critical pieces of the cloud-centric architecture. Self-service and automation are paramount, driving the goal of empowering our engineers to quickly create and configure their solutions in an unencumbered manner.<\/p>\n Infrastructure as Code (IaC) is the process of managing and provisioning cloud infrastructure and its configuration through definition files that machines can process\u2014rather than through the configuration of physical hardware or the use of interactive configuration tools. IaC is about using scripts and templates to build or configure a connected landing place for applications and business data.<\/p>\n IaC doesn\u2019t involve building user-interactive portals or creating tickets for others to run automation. IaC instead involves supplying standardized, robust APIs to application engineering teams to integrate into their deployment automation. Beyond supplying APIs, the infrastructure team supplies standard, curated configuration templates and software images for application engineering teams to consume.<\/p>\n Within the Microsoft Azure Resource Manager framework, Azure contains recognized IaC that allows engineering teams to rapidly provision the underlying hosting platform for their applications.<\/p>\n We need to continue the push from fully centralized operations to a Microsoft Azure DevOps model. Specific efforts from infrastructure teams in partnership with business units need to continue and improve in the following ways:<\/p>\n Identity management and governance supply the guardrails that help protect our cloud-centric architecture. Identity is the new perimeter in modern networking and architecture, so it deserves high-priority consideration within the architecture to help ensure the security of our environment. Governance is also critical in the modern architecture, helping to guide and safeguard a largely self-service environment.<\/p>\n We need to simplify provisioning, entitlements, and access management. We also need to streamline account provisioning and management, helping ensure that all access is auditable and linked to an approved business justification. Finally, we need to ensure that all credentials will expire or be revoked when no longer required while maintaining the principle of least privilege for administrators and users. Our two primary efforts in identity management are:<\/p>\n Cloud-focused architectures still require proper guardrails and governance for two reasons: to help protect corporate data and assets from internal and external threats and to help ensure that the data and assets adhere to corporate and compliance standards. Much of our current governance is manual in nature, and some is our own intellectual property created to fill product gaps in Microsoft Azure. As Azure continues to add features, we need to embrace those native features that will help ensure we\u2019re properly governing the cloud:<\/p>\n The way we treat our apps and data has changed in cloud-centric architecture. With more user-design models becoming available, engineers no longer function as the only developers in our organization. Users are taking advantage of platforms and tools that offer no-code or low-code development methods to create business solutions. Through all of this and within our more traditionally developed apps, we need to drive consistent development and data usage and protection methods.<\/p>\n As more teams use Containers and Microsoft Azure Service Fabric, the infrastructure and security teams need to invest in creating the right guardrails for these new paradigms. This means that even more than previously, we need to track the Microsoft Azure subscription, make the correct policies and templates available, and then apply those policies and templates\u2014to help ensure that the more-transitory resources belonging to modern solutions immediately use the correct controls. Our priorities are as follows:<\/p>\n Managing our most-critical data assets will continue to be a top priority going forward. With more modern architectures, an increased ability to separate the compute and storage resources will exist, so managing the storage data will become a critical priority:<\/p>\n Our investment in the modern networks area involves all aspects of our networking environment. That is, we\u2019re investing in modern deployment and configuration practices to create and support a networking environment that supplies a solid foundation upon which the cloud-centric architecture rests. This includes adopting an internet first network model, increasing support for Software-Defined Networking, making more efficient use of Microsoft ExpressRoute connections, creating more intentional network segmentation, migrating to Internet Protocol version 6 (IPv6), and increasing Network Function Virtualization (NFV).<\/p>\n All clients have been moving to an internet first model over time\u2014first, by enrolling mobile devices with Microsoft Intune and, eventually, by connecting branch offices and some corporate offices primarily through the internet instead of through traditional on-premises network connectivity. Clients traversing a virtual private network (VPN) or similar solution for access to corporate applications won\u2019t offer the best model going forward. To become an internet first organization, we\u2019re focusing on the following:<\/p>\n With most clients moving to an internet first model over the next few years, we in Microsoft Digital need to examine where line-of-business applications place services going forward. With most clients moving outside the on-premises network boundary, it makes the most sense for the applications they use day to day to have a presence on the internet versus continuing to require a special network connection back to an on-premises network-based solution. To improve services placement, we\u2019re examining the following:<\/p>\n Within Microsoft Digital, the Zero Trust and internet first efforts will encourage teams to examine their on-premises, network-bound solutions by using ExpressRoute. Additionally, the Microsoft Azure ExpressRoute service will continue to grow, because a plethora of product teams are just starting to move their lab and build solutions to Azure. Over time, we want teams to examine hosting their solutions outside the traditional corporate network more and more\u2014that is, in a fully internet-based posture, in an appropriate Software-Defined Networking environment, and with defense-in-depth security controls applied.<\/p>\n To further embrace Software-Defined Networking and ExpressRoute, we\u2019re focusing as follows:<\/p>\n For us in Microsoft Digital, network segmentation is one of the largest components of the cloud-centric architecture. The corporate extranet network and the security zones that define it have existed for decades. In the modern cloud-environment era, we need to revise network segmentation by:<\/p>\n Internet Protocol version 4 (IPv4) address ranges continue to be challenging to manage because of the dwindling number of available addresses versus the growth of the environment. We need to accelerate IPv6 deployment to help ensure continued network capacity. IPv6 removes complications from network address translation and simplifies acquisitions. We\u2019re addressing the migration to IPv6 as follows:<\/p>\n Going forward, we need to heavily invest in Software-Defined Networking, including Network Function Virtualization (NFV). NFV has substantially improved and will continue to do so. By moving older network zones to the internet, we can increase the internet first mentality while still supplying adequate controls. Making applications self-contained within a specialized zone can help lock down both vertical and horizontal access, which makes solutions more secure. The NFV-related actions include:<\/p>\n Microsoft Azure is adding the ability to use service tunneling to access resources via VPNs, including ExpressRoute virtual networks. With this new model, teams might be able to use PaaS resources within a more-limited network and security boundary. To improve service tunneling, we\u2019re examining the following:<\/p>\n We\u2019re continually assessing our approaches to cloud-centric architecture to help ensure continued growth and reliable and optimized services. We have over 40 years of IT history and technical debt that we can\u2019t transform overnight. Our success will be determined by the fluidity of our users\u2019 experience and the level to which we can create an abstraction of our IT infrastructure via cloud-based platforms. This abstraction will create flexibility, usability, scalability, and resiliency for the entire business, which our cloud-centric architecture will support. We\u2019re exploring further transformation while staying dedicated to the effective operation of our entire service portfolio. We\u2019re finding common scenarios where we can optimize services and applications for the cloud, and we\u2019re automating and abstracting as many manual processes and tasks as possible. We\u2019re using the metadata across all our systems to digitally document our cloud infrastructure, creating software-defined templates for the deployment and configuration of infrastructure resources.<\/p>\n [Editor\u2019s note: This content was written to highlight a particular event or moment in time. Although that moment has passed, we\u2019re republishing it here so you can see what our thinking and experience was like at the time.] Here at Microsoft, we\u2019re building our\u00a0systems in the cloud to be agile, resilient, cost effective, and scalable\u2014this […]<\/p>\n","protected":false},"author":133,"featured_media":12719,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_hide_featured_on_single":false,"_show_featured_caption_on_single":true,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[1],"tags":[89,115],"coauthors":[646],"class_list":["post-9233","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized","tag-digital-transformation","tag-microsoft-azure","program-microsoft-digital-technical-stories","m-blog-post"],"yoast_head":"\n[Editor\u2019s note: This content was written to highlight a particular event or moment in time. Although that moment has passed, we\u2019re republishing it here so you can see what our thinking and experience was like at the time.]<\/em><\/p>\n
Building a foundation for digital transformation<\/h2>\n
Establishing a vision for cloud-centric architecture<\/h2>\n
\n
Designing for the future<\/h3>\n
Enabling the cloud-centric architecture<\/h2>\n
\n
Administering the Microsoft Azure fabric<\/h3>\n
\n
Using IaC and Microsoft Azure DevOps<\/h3>\n
IaC<\/h4>\n
Microsoft Azure DevOps<\/h4>\n
\n
Using identity management and governance<\/h3>\n
Identity management<\/h4>\n
\n
Governance<\/h4>\n
\n
Using modern apps and data solutions<\/h3>\n
Modern apps<\/h4>\n
\n
Modern data solutions<\/h4>\n
\n
Using modern networks<\/h3>\n
Internet first<\/h4>\n
\n
\n
Software-Defined Networking and ExpressRoute<\/h4>\n
\n
Network segmentation<\/h4>\n
\n
Migration to IPv6<\/h4>\n
\n
NFV<\/h4>\n
\n
Service tunneling<\/h4>\n
\n
<\/h2>\n
<\/h2>\n
\n