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)

Azure resource locks

What does this mean? As an administrator, you may need to lock a resource group or resource to prevent other users from accidentally deleting or modifying critical resources. ARM offers a mechanism with two levels (CanNotDelete or ReadOnly) to be able to make appropriate settings.

Let's take a look at this:

  1. In the portal, click on Resource groups, and then click on the Resource groups blade, then the acdppbook name, as shown in the following screenshot:
  1. In the navigation section on the Resource groups dashboard, click on the Locks button, then click on the Locks blade, followed by clicking on the Add button:
  1. Now, type ppbookdemo in the Lock name field, select a lock type, and click on the OK button:
  1. Your first lock is ready, as shown in the following screenshot:
Attention! In my example, I have put Read-only as a lock type on resource groups. This lock is automatically inherited to all subordinate resources. This has the consequence...