Book Image

Implementing Azure Solutions - Second Edition

By : Florian Klaffenbach, Markus Klein, Sebastian Hoppe, Oliver Michalski, Jan-Henrik Damaschke
Book Image

Implementing Azure Solutions - Second Edition

By: Florian Klaffenbach, Markus Klein, Sebastian Hoppe, Oliver Michalski, Jan-Henrik Damaschke

Overview of this book

<p>Microsoft Azure offers numerous solutions that can shape the future of any business. However, the major challenge that architects and administrators face lies in implementing these solutions. </p><p>Implementing Azure Solutions helps you overcome this challenge by enabling you to implement Azure Solutions effectively. The book begins by guiding you in choosing the backend structure for your solutions. You will then work with the Azure toolkit and learn how to use Azure Managed Apps to share your solutions with the Azure service catalog. The book then focuses on various implementation techniques and best practices such as implementing Azure Cloud Services by configuring, deploying, and managing cloud services. As you progress through the chapters, you’ll learn how to work with Azure-managed Kubernetes and Azure Container Services. </p><p>By the end of the book, you will be able to build robust cloud solutions on Azure.</p>
Table of Contents (14 chapters)

Working with ARM

We now know that ARM serves as the technical base for the provision of resources. How are we going to continue? First, we will deal with the basic workflows in ARM. Then, in the second part, we will look at working with templates.

Before we begin, I want to introduce some very important facts that are crucial for all workflows:

  • All of the resources in your resource group have the same life cycle. You will deploy, update, and delete them at the same time.
  • Each resource can only exist in one resource group.
  • You can add or remove a resource to a resource group at any time. You can also move a resource from one resource group to another.
  • A resource group can contain resources that exist in different locations.
  • A resource can interact with a resource in another resource group when the two resources are related, but do not share the same life cycle (for example, a web app connecting to a database).

OK, let's start with the first workflow.