Home

Awesome


services: ARM and Azure Pipeline author: wviriya level: 300

FastTrack for Azure Live - How to deploy Azure services and infrastructure. Leverage Azure Pipeline for CI/CD.

Synopsis:

"Zero to Hero with ARM and IaC" How to create a Bicep template and deploy using Azure Pipelines.

Who should attend:

At the end of the session you should:

What are prerequisites:

Where are your team

Automation Maturity

About this sample

This sample is a guide for learning basic Bicep. The links in this document can you help better understand these services and tools.

What is Infrastructure as Code?

Why I should adopt Infrastructure as Code Practice? (Read John Downs' Blog)

Bicep

A language for declaratively deploying Azure resources. You can use Bicep instead of JSON for developing your Azure Resource Manager templates (ARM templates). Bicep simplifies the authoring experience by providing concise syntax, better support for code reuse, and improved type safety. Bicep is a domain-specific language (DSL), which means it's designed for a particular scenario or domain. It isn't intended as a general programming language for writing applications.

Azure Resource Manager (ARM) Template

A native infra-as-code solution for managing Azure resources using a declarative programming paradigm.

Concepts

Authoring tools and helps

CI/CD

Learning resources

Other orchestrators

Terraform with Azure

Ansible wiht Azure

FAQ

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.

When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

Trademarks

This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies.