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)

The authentication and lock level section

In the AUTHENTICATION AND LOCK LEVEL section, you need to define who has access to your resources, as well as what the users deploying your managed application can view in their portal. The first Lock Level parameter is used to define the access level of users deploying your managed application. There are two options from which you can choose:

  • Read Only
  • None

There is no option to grant more rights than Read Only to users deploying your managed application, as the definition of an Azure managed application is that the publisher maintains the application. If you plan to grant your users a higher access level, you should consider an Azure Marketplace offer.

The table beneath the Lock Level parameter defines the roles and members, which have more access to your managed application:

Definition of users and groups for access to the managed application

You can define all preconfigured roles available in Azure and give access to users, as well as groups...