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)

RBAC

Azure identity management is set as AAD. All user configuration and permissions rely on directory roles. You can see all enabled roles when looking at the user itself in Azure AD:

Around 70 default directory roles are available and can be enabled easily. This list may vary, depending on the enabled resource provided:

By showing the permissions of a role, you will see all features a role member can fulfill in Azure:

Configuring roles in Azure is quite easy, as you will need to set them up through the Access control (IAM) entry for a resource or resource group. If your requirement for a role is not available in Azure, you have the chance to set up your own role definition as RBAC. For example, if you will need to have a role that is a contributor, not all features that are allowed by default need to be enabled (for instance, deleting a virtual machine). Therefore, setting up the custom role is a configuration need:

The following JSON shows an example for a custom RBAC...