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)

Chapter 4: Azure Managed Applications

  1. For publishing an Azure service catalog managed application the following tools can be used
    • Azure CLI
    • Azure PowerShell
    •  Azure Portal
  2. To create an Azure managed application definition the mandatory files are
    • mainTemplate.json
    • createUiDefinition.json

 

  1. During the deployment of an Azure Managed Application two resource groups will be used. One resource group holds the application itself (Application Resource Group) and another resource group is used for the elements of the managed application (managed resource group)
  2. The mainTemplate.json file is the ARM Template for the Managed Application and defines the resources and dependencies of the Managed Application.
  3. The three elements automatically injected in the basic section of an UI Definition file are as follows:
    • The subscription
    • The resource group to deploy to
    • The location of the deployed resources
  4. The method of testing your UI Definition in the Azure Portal is called sideloading...