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)

Elements of an Azure managed application

An Azure managed application package consists of two required elements which are then packaged into a .zip file:

  • Resource template: The resource template (mainTemplate.json) is a .json file which has no differences to a standard ARM template as described in Chapter 2, Azure Resource Manager and Tools. This file describes the resources and their parameters for deployment.
  • User interface definition: The user interface definition (createUiDefinition.json) is used by the Azure portal to generate the user interface when users are deploying a managed application.
Be aware that the names of these files are case sensitive.

Besides those required parts, a managed application can contain optional elements and files necessary for the ARM template like images, scripts and other artifacts.

Those files are then packaged into a single .zip file. The ZIP file must contain the required files on top-level and can contain the optional files (also in folders):

...