Breyta

Deila með

Platform automation and DevOps

  • Grein

Platform automation and DevOps evaluate opportunities to modernize your approach to environmental deployment with infrastructure as code options.

Design area review

Involved roles or functions: Platform automation and DevOps might require support from one of the following functions or roles to make decisions: cloud platform and cloud center of excellence.

Scope: The goal of platform automation and DevOps is to align your desired DevOps principles and practices to Azure Landing Zone lifecycle management. This goal includes provisioning, management, evolution, and operations through extreme automation and Infrastructure as Code.

Design area overview

The scale, agility, and flexibility part of cloud technologies leads to opportunities for new ways of working and modern approaches to service delivery.

Many traditional IT operating models aren't compatible with the cloud and must undergo operational transformation to deliver against enterprise migration targets. You can evaluate using DevOps processes and tools for application and central teams.

Platform automation

The ability to make changes at scale through a prescribed automated process provides direct benefits to the organization's ability to expand beyond the baseline configuration, which comes from security, governance, and management.

Platform automation is directly applicable to the outcomes associated with implementing a landing zone, and supports the concept of building repeatable, scalable environments.

  • Automation focuses on tools and techniques that enable the streamlining of automation tasks for Azure Landing Zone development, deployment, provisioning, and operations using automation tools such as Azure DevOps Services or GitHub.

DevOps

These resources address platform automation for DevOps.

  • DevOps considerations explores the need to have a clear and common understanding of DevOps in the organization. This resource also describes DevOps principles, practices, and capabilities that apply to workloads and to landing zones.
  • DevOps teams topologies describes how teams can be organized to own the end-to-end lifecycle of the Azure Landing Zone. Learn how these teams collaborate with other teams in the organization responsible for the end-to-end lifecycle of workloads deployed to Azure.

Development strategy

These resources address development strategy.

  • Development lifecycle explores key design considerations and recommendations for the creation of a landing zone by using automation. This resource discusses the repository, branch, automated builds, deployment, and rollback strategy.
  • Infrastructure as Code explains the benefits of implementing Azure Landing Zones by using Infrastructure as Code. Learn about considerations around code structure, tools, and technology.
  • Environments explains the purpose of multienvironments to build, test, and release code with greater speed and frequency. This approach makes deployment as straightforward as possible.
  • Test-driven development addresses how to use unit testing to improve the quality of new features and improvements in the Azure Landing Zone code-base.

Security considerations

These resources address security considerations in platform automation.

Next steps

Automation