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)

Security and access of an Azure managed application

When an Azure managed application is rolled out to a tenant, it will use two resource groups. The first resource group is considered as application resource group, the second as managed resource group.

  • The application resource group contains the instance of our managed application. The consumer (or internal user) has full access to that resource group for managing the application life cycle. As the user has no access to the resources itself, access to the application resource group is given to gather outputs from the deployment (such as public IP addresses or DNS names) to use the deployed resources (like a VM).
  • The managed resource group contains the resources that are required by the Azure managed application itself. Only the specified admins, which are defined when a managed application definition is created, do have write access to this resource group:
Source: https://docs.microsoft.com/en-us/azure/managed-applications/overview...