Book Image

Implementing DevOps with Microsoft Azure

By : Mitesh Soni
Book Image

Implementing DevOps with Microsoft Azure

By: Mitesh Soni

Overview of this book

This book will teach you all about the Visual Studio Team Services and Microsoft Azure PaaS offerings that support Continuous Integration, Continuous Delivery, Continuous Deployment, and execution in the cloud with high availability, disaster recovery, and security. You will first be given a tour of all the concepts and tools that Microsoft Azure has to offer and how these can be used in situations to cultivate the DevOps culture. You’ll be taught how to use and manage Visual Studio Team Services (VSTS) and about the structure of the sample application used throughout the book. You will become familiar with the nitty gritty of Continuous Integration and Continuous Development with VSTS and Microsoft Azure Apps. You will not only learn how to create App service environments, but also how to compare Azure Web Apps and App Service Environments to deploy web applications in a more secure environment. Once you have completed Continuous Integration and created the Platform for application deployment, you will learn more about the final stepping stone in achieving end-to-end automation using approval-based Continuous Delivery and Deployment. You will then learn about Continuous Monitoring, using the monitoring and notification options provided by Microsoft Azure and Visual Studio Team Services.
Table of Contents (17 chapters)
Title Page
Credits
About the Author
Acknowledgment
About the Reviewer
www.PacktPub.com
Customer Feedback
Dedication
Preface
More from the Author

Configuring role-based access for secure access of Azure Web Apps


Microsoft Azure Role-Based Access Control (RBAC) provides role-based authorization to access specific Azure resources or resource group. With Azure RBAC, we can provide access to resources based on need. For example, server-side developers get access to resources that are used to host the web application; the testing team will have access to only testing-related resources available in the Azure portal; the database team will have access to the SQL database.

There are three basic roles:

  • Owner: This has full access to all resources
  • Contributor: This is to create and manage all resources, but it has no privilege to grant access to others
  • Reader: This is to view available resources

Note

A few important things to note:

Microsoft Azure subscription has one Azure Active Directory (Azure AD) that has many users, groups, and applications associated with it. We can grant access to users and groups for available Azure resources at three different...