Azure Master Class v2 - Module 3 - Governance

Azure Master Class v2 - Module 3 - Governance

Introduction

In this section, the speaker introduces the topic of governance in the cloud and explains why it is critical.

The Importance of Governance in the Cloud

  • Governance in the cloud is critical because there has been a big shift from traditional on-premises processes and behavior.
  • In the past, users would make requests to IT operations personnel who had access to capacity, servers, and storage to host services.
  • In contrast, in the cloud, there is no human in the middle anymore. Users can request resources through APIs or portals without any human intervention.
  • Despite this change, there are still rules and requirements that need to be followed.

Applying Guardrails with Management Groups, Subscriptions, and Resource Groups

This section discusses how guardrails can be applied using management groups, subscriptions, and resource groups.

Applying Guardrails

  • Guardrails are necessary for self-service environments where business users and app owners provision their own resources.
  • Management groups provide a way to manage access policies across multiple subscriptions.
  • Subscriptions allow for resource isolation and billing boundaries.
  • Resource groups enable logical grouping of resources for easier management.

Provisioning Resources in the Cloud

This section explains how provisioning resources works in the cloud compared to traditional on-premises methods.

Provisioning Resources

  • In traditional on-premises environments, users would make requests to IT operations personnel who had access to capacity.
  • In contrast, in the cloud, users can request resources through APIs or portals without any human intervention.
  • Despite this change, there are still rules and requirements that need to be followed.

Specific Guardrails for Governance

This section discusses specific guardrails that can be used for governance in the cloud.

Specific Guardrails

  • In addition to management groups, subscriptions, and resource groups, other guardrails include policy-based access control and budget limits.
  • These guardrails help ensure compliance with regulatory and compliance requirements.

Governance in the Cloud

In this section, the speaker discusses the importance of governance in cloud computing and how it can be enforced through policies, role-based access control, and budgeting.

Importance of Governance

  • Guardrails need to be in place as part of the fabric of the cloud to enforce compliance rules.
  • Governance is about enforcing rules and ensuring proper functioning of the environment to standards.
  • Governance applies no matter what interaction takes place with the cloud.
  • Understanding requirements is critical for effective governance.

Elements of Governance

  • Policies define what can be done.
  • Role-based access control determines who can do various things.
  • Budgeting controls how much can be spent on certain resources.

Compliance Considerations

  • Corporate requirements such as auditing, logging, and metrics must be considered.
  • Regulatory compliance may also apply depending on industry standards.

Azure Shared Responsibility Model

  • Microsoft is responsible for core infrastructure while customers are responsible for things inside operating systems.
  • Different aspects of compliance exist across various services offered by Azure.

Managing Compliance in the Cloud

In this section, the speaker discusses Microsoft's compliance offerings and regulatory information available for managing compliance in Azure.

Microsoft Compliance Offerings

  • Microsoft provides a compliance site with information on managing compliance in Azure.
  • The site offers information on different aspects of compliance including regulatory information.

Compliance Manager and Governance

In this section, the speaker talks about how to track compliance scores for different services using the Compliance Manager. They also discuss how to use Microsoft's compliance portal to track different offerings and industries.

Compliance Score

  • The Compliance Manager helps track compliance scores for different services.
  • The score is based on actions completed or not completed.
  • Improvement actions are available to improve overall posture.

Microsoft Compliance Portal

  • The same compliance portal can be used to track different offerings and industries.
  • The portal shows information about assurance of regulatory requirements.
  • Different standards for Azure, Dynamics 365, and Microsoft 365 are shown.
  • Information is available on mitigating risks such as data loss, infiltration, service interruption, and reputation damage.

Governance Components

  • Management groups provide a hierarchy in which resources can be organized.
  • Different requirements can be applied at different levels such as company-wide or business unit level.
  • Management groups create a hierarchy for subscriptions and resource groups containing resources.

Identity Provider for Azure

In this section, the speaker discusses the identity provider for Azure.

Identity Provider

  • The identity provider for Azure is always an Azure.

Introduction to Azure Management Groups

In this section, the speaker introduces the concept of management groups in Azure and explains how they are used for governance and management of resources.

Creating a Root Management Group

  • When creating the first management group, a root management group is automatically created.
  • The root management group cannot be moved or deleted and all subscriptions that trust the Azure ID tenant by default roll up under it.
  • The ID of the root management group is the same as the Azure AD tenant.

Hierarchy of Management Groups

  • Under the root management group, users can create their own hierarchy of management groups.
  • Users can create multiple levels of child management groups, up to 6 levels.
  • A management group can only have one parent but can have multiple children.

Structuring Management Groups

  • There is no right or wrong way to structure management groups. They are designed to help with governance and resource management.
  • Governance policies applied at higher levels get inherited down to lower levels. Users may apply broad policies at higher levels and more specific ones closer to resources.

Example in Portal

  • In the portal, users can see their hierarchy of management groups under "Management Groups".
  • Each child management group can have its own subscriptions and child management groups.
  • The "Governance" tab on each level allows users to manage security, policy, budgets, and access control.

Understanding Azure Management Groups and Subscriptions

In this section, the speaker explains the relationship between management groups and subscriptions in Azure.

Management Groups

  • Identity access control, identity access management (IAM), policy budgets are common themes across all management groups.
  • Management groups are used to organize subscriptions.
  • A subscription can be moved if the owner of the subscription wants to trust a different Azure AD tenant. However, any role-based access control will be lost.

Subscriptions

  • Subscriptions are used as a starting point for creating resources in Azure.
  • There are limits and quotas associated with subscriptions, which may be a reason for creating new subscriptions.
  • There is an unlimited number of subs per management group.
  • 980 resource groups per subscription is allowed.

Note that there were no timestamps provided for some parts of the transcript.

Understanding Azure AD Limits and Subscriptions

In this section, the speaker discusses the importance of understanding Azure AD limits and subscriptions. They explain that a subscription is a boundary for resources like virtual networks and has access controls, policies, budgets, and quotas associated with it.

Azure AD Limits and Service Limits

  • There are Azure AD limits and different service limits.
  • It's important to understand these limits because they may drive you to create multiple subscriptions.

Subscriptions as Boundaries

  • A subscription is a boundary for resources like virtual networks.
  • Virtual networks can't span subscriptions or regions.
  • Therefore, multiple subscriptions may be necessary if using many regions or services.

Subscription Features

  • A subscription has access control, policy, budget features.
  • Quotas are also associated with subscriptions.
  • The usage and quota screen shows how much quota has been used and allows for requesting more quota.

Resource Groups

  • Every resource lives in one resource group.
  • Things that run together should be provisioned in the same resource group.

Resource Groups

In this section, the speaker explains what resource groups are and how they are used in Azure.

Creating Resource Groups

  • A resource group lives in a subscription and is used to group together resources that share a common lifecycle.
  • Resources can be created inside a resource group, such as virtual machines or databases.
  • The criteria for putting resources in the same resource group include sharing a common lifecycle and being managed by the same sets of people with similar policies assigned to them.

Boundaries of Access

  • A resource group is not a boundary of access. For example, virtual machines can still be connected to a virtual network even if they are in different resource groups.
  • Some resources may be located in different resource groups because they have different lifecycles or are used by multiple applications.

Moving Resources

  • Resources can be moved between resource groups easily.
  • Some resources can also be moved between subscriptions or regions, but it depends on the type of resource and its dependencies.
  • When moving resources, Azure will check for dependencies and provide guidance on how to perform the move.

Applying Governance with Management Groups, Subscriptions, and Resource Groups

In this section, the speaker explains how management groups, subscriptions, and resource groups can be used to apply governance in Azure.

Governance Structure

  • Management groups provide an organizational hierarchy for managing access control policies across multiple subscriptions.
  • Subscriptions provide a logical container for deploying resources and managing costs.
  • Resource groups provide a way to organize related resources within a subscription.

Applying Governance

  • The structure provided by management groups, subscriptions, and resource groups allows for applying governance at each level.
  • Policies can be applied at any level to enforce compliance with regulations or company standards.

Understanding Azure Governance

In this section, the speaker discusses the importance of governance in Azure and how to apply policies, role-based access control (RBAC), and budgeting.

Applying Policies, RBAC, and Budgeting

  • Avoid putting very detailed policy at the root level. It should be broad types of policy that absolutely have to apply to everything.
  • As you get closer to the resource, get more specific with your policy and different people that need different permissions on resources.
  • Understand the requirements of different environments such as dev, test versus production. Different business units may have different regulatory requirements.
  • There is no concept of blocking inheritance in Azure governance. Policies are inherited down all structures.

Importance of Governance

  • Policies, RBAC, and budgeting are key components of governance in Azure.
  • The structure is important when applying policies.
  • Policies are enforced by organizations to ensure requirements are met for accessing resources.

Conclusion

  • Companies do not want you to block higher up policies or RBAC because it enforces rules. If there is a strong requirement to block a policy, it may have been applied at the wrong place.

Applying Policy and Access Control at Different Levels

In this section, the speaker discusses how to apply policy and access control at different levels in Azure.

Applying Policy and Access Control

  • Azure has constructs such as management groups, subscriptions, resource groups that can be used to apply policies and access control.
  • Policies and RBAC can be applied at different levels based on business needs.
  • Budgets can also be set at different levels which will roll up to cover everything under that particular construct.
  • It is generally recommended to avoid applying access control at an individual resource level as it becomes hard to manage.

Enterprise Agreement and Billing

In this section, the speaker briefly touches upon enterprise agreements and billing structures in Azure.

Enterprise Agreement and Billing

  • Enterprise agreements have their own set of structures around departments, accounts, account owners that can create subscriptions.
  • Tagging is a powerful tool that can be used for billing purposes. It gives more flexibility for showback and chargeback for billing records just by looking at the tags.

Resource Locking

In this section, the speaker discusses resource locking in Azure and how it can help prevent accidental actions such as deletion. The speaker explains that locks can be applied at different levels - subscription, resource group, or individual resource - and that there are two types of locks: read-only and cannot delete. It is important to note that locks only apply to the control plane level and not the data plane level.

Applying Locks

  • Locks can be applied at a certain point and will get inherited.
  • A lock can be applied at a resource group level, which will then lock everything inside it.
  • Locks can be added through the Azure portal by selecting a resource group and clicking "Add a lock".
  • When adding a lock, you must choose between read-only or cannot delete.

Control Plane vs Data Plane

  • The cloud operates as an API with CRUD operations going against the control plane.
  • Locking is enforced at the control plane level only.
  • Locking does not apply to interactions from applications to the data plane of some service.

Limitations of Locking

  • Inside a locked storage account or database, it is still possible to delete specific items (e.g. blobs or rows).
  • Any interactions from applications to the data plane of some service will still work just fine even if there is a lock in place.

Understanding Azure Resource Manager

In this section, the speaker explains how to manage resources in Azure using Azure Resource Manager.

Ownership and Locking Resources

  • As an owner of a resource in Azure, you can change or remove locks that have been applied to it.
  • The ability to remove locks is limited to the scope at which you are the owner. For example, if you are only a resource group owner, you cannot remove a lock at the subscription level.

Structure of Resources in Azure

  • All resources in Azure are defined by resource providers.
  • Resource providers define the types of resources available in Azure. For example, Microsoft.Compute defines virtual machines and managed disks.
  • Each resource has different properties depending on its type. For example, virtual machines have hardware profiles and storage profiles while disks do not.

Resource Providers Hierarchy

  • There are many resource providers in Azure such as Microsoft.Compute and Microsoft.StorageNetwork that define available resources.
  • Inside each resource provider there are different elements that make up the hierarchy of resources available for use in Azure.

Azure Resource Management

In this section, the speaker discusses the different types of resources and actions that can be applied to them in Azure Resource Management. They also introduce role-based access control (RBAC) and how it applies to management and data planes.

Types of Resources and Actions

  • A resource has properties and actions that can be applied to it.
  • Different types of actions apply to different resource types.
  • Examples of resource types include virtual machines, network, and storage.

Role-Based Access Control

  • RBAC is available at all levels in Azure Resource Management, including management groups, subscriptions, resource groups, and resources.
  • RBAC can be used for both the management plane (via ARM API) and data plane (some services support RBAC at the data plane).
  • Permissions for RBAC are based on Azure AD identities.

Storage Account Example

  • Storage accounts have different roles with different permissions on the control plane for storage.
  • The contributor role has different types of actions that can be applied to it depending on the resource provider (e.g., Microsoft authorization or insights).

Azure AD and Role-Based Access Control

In this section, the speaker discusses how Azure AD is used on the data plane and how role-based access control works.

Azure AD on the Data Plane

  • Contributor accounts using Azure AD on the data plane do not have any permission.
  • A contributor account for a storage account can get the access key, which can be used to perform data plane operations.
  • The contributor account has limited capabilities available for BLOB, Queue, Table, and some databases.

Role-Based Access Control

  • Roles are collections of common actions that are assigned to a security principle at a certain scope.
  • Actions are added to a role and then granted to a group or principal at a certain scope through role assignment.
  • Custom roles can also be created using different available actions.

Azure Roles and Access Control

In this section, the speaker discusses different roles in Azure and how to create custom roles.

Understanding Different Roles

  • There are different built-in roles in Azure.
  • Contributor is a key role that has 383 actions associated with it.
  • Contributor has all actions except for some authorization levels that change access permissions.
  • Virtual Machine (VM) contributor shows the types of actions available for VM-related tasks.
  • You can find all the roles in the repo for the module.

Creating Custom Roles

  • All roles related to compute mention the compute resource provider.
  • The speaker creates a new role called virtual machine operator based on virtual machine contributor and makes it more specific by removing some roles and adding others.
  • You can create your own custom roles if the built-in ones don't meet your needs.
  • The roles you see will vary depending on what resource you're looking at. For example, storage accounts will only show sanctioned storage account-related roles while VM-related tasks will only show VM-specific roles.
  • The speaker has created several custom roles such as stop resources, storage share changes, read-only VM, and run command role with only two permissions.

Creating Custom Roles from Scratch

  • When creating a custom role, you can start from scratch or clone an existing one by selecting an existing role and giving it a new name.

Azure Role-Based Access Control

In this section, the speaker discusses how to use Azure Role-Based Access Control (RBAC) to assign permissions and roles to users, groups, and service principals.

Assigning Permissions with RBAC

  • Permissions can be added or excluded using wildcards.
  • Assignable scopes determine where a definition will live.
  • Roles can be assigned at different levels such as management group subscriptions or resource groups.
  • Different ways exist for creating roles in Azure.

Least Privilege Principle

  • The principle of least privilege should be applied when assigning roles.
  • Owners should only be literal owners of that resource group or subscription.
  • Most permissions should be assigned at the resource group level.
  • Ideally, grant permissions to groups rather than individual users.

Role Assignment

  • Assignments can be made at any level and are inherited down.
  • Most restrictive role possible should be selected when making an assignment.
  • Groups are preferred over individual users when making assignments.
  • Managed identities and service principals can also be used for role assignments.

Privileged Identity Management

  • Just-in-time access is available through privileged identity management.

Section Conclusion: In this section, we learned about how to use Azure RBAC to assign permissions and roles. We also discussed the principle of least privilege and how it applies to role assignment. Finally, we briefly touched on privileged identity management.

MFA and Attribute-Based Access Control

In this section, the speaker discusses the limitations of RBAC and introduces attribute-based access control as a solution. They also discuss custom attributes in Azure AD that can be used to grant specific permissions.

Limitations of RBAC

  • RBAC may not be granular enough for certain scenarios, especially when dealing with data.
  • There is a finite number of roles allowed within a subscription (4000), which may not be enough if permissions need to be assigned very specifically.

Attribute-Based Access Control

  • Attribute-based access control allows for conditions to be added to role assignments based on metadata or identity attributes.
  • This can help restrict access to data by matching attributes such as project or container.
  • This feature has limited support currently but is growing.

Custom Attributes in Azure AD

  • Custom attribute sets can be created in Azure AD, such as a project attribute set with clearance and primary project attributes.
  • These custom attributes can then be granted permission to specific departments or teams for modification.
  • Custom attributes can also be configured at the user level, allowing for specific permissions based on those attributes.

Clarks and Bruce Wayne's Azure Storage Accounts

In this section, the speaker discusses how Clarks and Bruce Wayne's Azure storage accounts are configured differently. They also explain how BLOB index tags work and how they can be used to add optional metadata to images.

Configuring Storage Accounts

  • Clarks' storage account is assigned as value alpha, while Bruce Wayne's is configured as Project Bravo.
  • The speaker explains that if they were to look at the data itself, they would see that the two storage accounts are different.
  • The speaker scrolls down to the storage accounts and points out that there are five images in the containers.
  • BLOB index tags can be defined on these images as optional metadata.

Metadata Values

  • The speaker explains that some of the images have different metadata values, while others have none at all.
  • For example, "Do you even Azure?" has a project of alpha, while another image has bravo and another has gamma.

Role Assignments

  • The speaker goes on to discuss role assignments for accessing BLOB data readers using Azure AD.
  • There are two conditions for successful reading of BLOB: either it matches a long first condition or its resource container name equals general.
  • If someone tries to access an image from a container with a different name than what was specified in the conditions, it will fail.

Disabling Storage Account Key Use

  • Clark cannot access certain parts of the storage account because key-based authentication has been disabled.

Understanding RBAC and Policy in Azure

In this section, the speaker explains RBAC (Role-Based Access Control) and Policy in Azure. The speaker discusses how RBAC controls who can perform different operations on different types of resources, while Policy sets rules for what can be done.

Role-Based Access Control (RBAC)

  • RBAC defines who can do different operations on different types of resources.
  • Primary project attribute must match the index tag project key to access.
  • Hawk has access to the second image.
  • Clark has access to the third image.
  • One single rule changes the game.

Policy

  • Policy sets rules for what can be done with resources.
  • Enforces what can be done and where it can be done.
  • Can use it for enforcement, auditing, or remediation.

Starting with Audit

In this section, the speaker emphasizes the importance of starting with an audit when adding new policies. They explain that denying things without understanding what is happening can mess up the business and your career.

Importance of Audit

  • Starting with an audit is crucial when adding new policies.
  • Denying things without understanding what is happening can mess up the business and your career.

Understanding Compliance States

In this section, the speaker explains that compliance states are important to understand before implementing policies. They suggest providing user education and guidance to ensure successful implementation before moving on to denying things.

Compliance States and User Education

  • Understanding compliance states is important before implementing policies.
  • Providing user education and guidance can help ensure successful implementation.
  • Once a certain threshold of people are correctly following policies, you can start denying things.

Azure Policy Structure

In this section, the speaker explains how Azure policy works by defining a policy as a set of conditions built around resource attribute aliases with an effect.

Defining Azure Policy

  • A policy is a set of conditions built around resource attribute aliases with an effect.
  • Not every property of a resource may be available to use as part of policy, but if they're exposed for an alias, then those properties match certain values, for example in storage accounts, then you can do something based on it such as auditing or denying access.
  • The primary thing you can do in Azure Policy is have an effect: audit, deny or modify etc..

Azure Policy Definitions

In this section, the speaker explains how to define an Azure policy and shows an example of a simple one.

Defining Azure Policy

  • You can have custom policies in Azure.
  • The key thing to look at when defining a policy is the policy rule.
  • A policy rule is an if statement with conditions that must be true for the effect to take place.
  • Compliance states are important to check and ensure regulatory requirements are met.

Azure Policy and Initiatives

In this section, the speaker talks about Azure Policy and how it can be used to deny public IP addresses to virtual machines or network interface cards unless they are in a specific DMZ subnet. The speaker also discusses initiatives and how they can be used to assign multiple policies at once.

Azure Policy

  • If a resource has a public IP address and is a network interface card, the policy will apply.
  • The policy denies adding a public IP address to a virtual machine or NIC unless it is in the DMZ subnet.
  • Policies can be assigned at different scopes such as management group, subscription, or resource group.
  • Policies can be assigned directly.

Initiatives

  • Initiatives allow for multiple policies to be assigned at once.
  • Initiatives are assigned to a certain scope.
  • There are many types of initiatives available such as NIST SP 800 and Azure Security Benchmark.
  • Compliance can be checked by assigning an initiative.

Deny Action

  • Deny action allows for denying delete actions using policy.

Azure Policy

In this section, the speaker talks about how to use Azure policy to enforce certain actions against different types of resources. They explain how policies can be grouped into initiatives for assignment and compliance purposes.

Using Azure Policy

  • The speaker created a policy that denies delete if the tags lock status equals lock.
  • The speaker was looking for if the tags lock status equals lock so they have to either add a tag called lock status and set it to a value of lock or because it's any of.
  • If it's a production storage account, the speaker is going to deny deleting it.
  • The way to use this is by assigning the policy at a scope above where people are owners so they can't remove the assignment of my policy.

Azure Policy Effects

  • Policies can be grouped into initiatives for assignment and compliance purposes.
  • When getting started with Azure, take some time to really understand what your requirements are and get the right policies in place.
  • There are different effects such as disabled, audit, modify, deploy if not exists, and deny.
  • Modify effect modifies it at provisioning time while deploy if not exists happens post creation.

Linux and Cost Management

In this section, the speaker talks about deploying log analytics extension for Linux VMs and cost management and budgets in Azure.

Deploying Log Analytics Extension for Linux VMs

  • The speaker shows how to deploy log analytics extension for Linux VMs.
  • Policy is used to check if a virtual machine is a certain image which is going to be the Linux ones. If it's true, then the deployment will not happen.
  • The OMS agent for Linux cloud monitoring needs to be deployed on the virtual machine.

Cost Management and Budgets

  • Cost management provides insight and control of Azure, including a connector for AWS as well.
  • It allows users to see their spending patterns, get alerts around anomalies, create budgets based on actual spend or forecasted trends of spend, and trigger certain types of actions when thresholds are exceeded.
  • Users can access cost analysis views that show accumulated costs by resource group or service. They can also drill down into specific areas such as storage spend.

Azure Cost Management

In this section, the speaker discusses various features of Azure Cost Management.

Filters and Data Export

  • Users can add filters to their data based on tags or cost centers.
  • The filtered data can be used to view the money spent for specific departments.
  • Users can download their current data in different formats or schedule an export to a storage account on a daily, weekly, or monthly basis.

Alerting and Budgets

  • Users can set up alerts for anomalies in their spending.
  • Alerts can be sent via email when strange anomalies are detected.
  • Users can create budgets and define thresholds based on percentage of spend or forecasted trends.
  • Action groups can be triggered when budget thresholds are reached. These groups can perform various actions such as sending emails or calling APIs.

Cost Allocation

  • Cost allocation is only available for users with EA agreements or customer agreements.
  • It allows users to split costs among different resource groups, subscriptions, or tags based on custom splits or proportional splits.

Cost Allocation and Optimization

In this section, the speaker discusses cost allocation and optimization in Azure. He explains how to split shared service costs to the people who benefit from it using cost allocation. The speaker also emphasizes the importance of understanding costs and optimizing them.

Cost Allocation

  • Cost allocation lets users split some shared service cost to the people who ultimately benefit from it.
  • Users can configure how they want to do that split.
  • There are two different areas where targets can see their bill - one area shows actual accumulated cost, while another shows cost allocation.

Pricing Tools

  • There is an API available for dealing with cost allocation in the portal.
  • Power BI reports are available for viewing spend.
  • The pricing calculator is a powerful tool that allows users to calculate costs based on resources, scale, and budgets.
  • It's important to understand all of the different costs associated with any resource you have before using the pricing calculator.

Optimization

  • Always optimize your Azure costs by autoscaling when you don't need more resources.
  • Apply as many discounts as possible.
  • Understand what might cause you to consume more resources which will make it cost more money.

Billing Usage Data

  • Tags don't get inherited but with policy, tags can be copied from parent resource groups or subscriptions.
  • For billing usage data only, there is a way to switch out of an MSDN subscription and view your cost management.

Managing Azure Subscription

In this section, the speaker talks about managing Azure subscription and how to optimize cost.

Tag Inheritance

  • Tag inheritance is a feature that allows copying tags from subscription or resource group to billing usage records.
  • It only applies to billing usage records and not regular ARM.
  • If a resource doesn't have a tag, it will copy it from the subscription or resource group which is closest.
  • The closest tag will win out if there are same tags for both subscription and resource group.

Optimizing Cost

  • To optimize cost, one can use reserved instances which offer discounts on committing to using specific resources for a certain amount of time.
  • One can also make smart decisions such as right-sizing VM skew, autoscaling constantly, using spot VMs if not time-critical, etc.

Compute Services

  • There are different compute services in Azure such as VM skews grouped into families like DV4DV5E, Azure container instances, premium functions, app services, etc.
  • These compute services can be used in different regions.

Reserved Instances and Azure Savings Plan

In this section, the speaker discusses Reserved Instances (RI) and Azure Savings Plan. He explains how they work, their benefits, and differences.

Reserved Instances

  • RI is a one or three-year commitment that provides a discount for steady usage.
  • Multiple RIs can be created for different SKUs and regions.
  • Remaining balance of an RI can be traded in for a new commitment with the same or greater value until January 1st, 2024.
  • Once committed to an RI, it cannot be changed for the duration of the commitment.

Azure Savings Plan

  • A one or three-year term that applies to all included compute services across all regions.
  • Discount varies depending on specific service but applies broadly.
  • Billing mechanism wakes up hourly to apply discounts where possible.
  • If both RI and Azure Savings Plan are available, RI will apply first as it offers a bigger discount.

Other Cost-Saving Mechanisms

Azure Hybrid Benefit

  • Allows existing licenses for Windows Server or SQL Server to be used in the cloud to reduce costs.

On-Demand Capacity Reservation

  • Not a cost-saving mechanism but important to note that neither RI nor Azure Savings Plan guarantee capacity availability.

Capacity Reservations

In this section, the speaker discusses capacity reservations and how they can be used to reserve capacity for resources in Azure.

Guaranteeing Capacity with Capacity Reservations

  • A capacity reservation is a way to guarantee capacity for a resource in Azure.
  • The user pays for the reserved capacity spot as soon as it is created.
  • The reservation is backed by a service level agreement (SLA).
  • Specific sizes and specific availability zones can be reserved using this method.

Using Reserved Instances (RI)

  • RI is another way to reserve capacity in Azure.
  • It applies to capacity reservations, so if a certain amount of usage is known, it can lock in that capacity without additional cost.

Naming Standards and Tagging

This section covers the importance of naming standards and tagging when working with resources in Azure.

Naming Standards

  • Having a standard naming convention is important for consistency across an organization's resources.
  • Microsoft's Cloud Adoption Framework provides recommendations for naming conventions.
  • Naming conventions should consider limitations such as maximum characters allowed and should define resource types, workload type, environment region, instance number, etc.
  • Consistency across cloud and on-premises environments is important.

Tagging

  • Tagging allows metadata to be defined on subscriptions, resource groups, and resources.
  • Values can be JSON documents for more descriptive information.
  • Microsoft's Cloud Adoption Framework provides recommendations for good tags to have.
  • Each resource can have up to 50 tags.

Azure Key Vault and Tagging

In this section, the speaker discusses Azure Key Vault and tagging. They explain that while most resources in Azure support tagging, secrets inside a key vault do not. The speaker also cautions against using deny policies for tags as it can block the ability to deploy resources.

Tagging in Azure Key Vault

  • Secrets inside an Azure Key Vault do not support tagging.
  • Most primary resources in Azure support tagging.
  • Deny policies for tags can block the ability to deploy resources.

Copying Tags from Resource Group or Subscription

  • Tags set on a resource group are not inherited by the resource.
  • Policies can copy tags from subscription or resource group if they don't exist on the resource.
  • Cost management enables inheritance but only for billing usage records.

Blueprints and Deployment Stacks

In this section, the speaker talks about blueprints and deployment stacks. They explain that blueprints allow different types of artifacts to be stamped onto a configuration, including resource groups and ARM templates.

Creating Blueprints

  • Blueprints allow different types of artifacts to be stamped onto a configuration.
  • Artifacts include resource groups and ARM templates.
  • ARM templates declaratively define resources to create in Azure.

Understanding Azure Blueprints and Deployment Stacks

In this video, the speaker explains how to use Azure Blueprints and Deployment Stacks to deploy resources in a subscription. The speaker also discusses the differences between these two tools and how they can be used to manage resources effectively.

Creating a Blueprint

  • A blueprint is a set of resources that can be deployed together.
  • When deploying a blueprint, it is possible to lock it so that resources cannot be deleted or changed.
  • Blueprints can be assigned to subscriptions, and versions can be updated as needed.

Using Templates for Resource Creation

  • Resource groups, RBAC, resource creation, and policy can all be created using templates without blueprints.
  • The only thing blueprints offer that templates do not is deniability through deny actions.

Introduction to Deployment Stacks

  • Deployment stacks are sets of resources with shared management lifecycles.
  • Deployment stacks allow for deny actions during deployment.

Azure Resource Management and Deployment

In this section, the speaker talks about Azure resource management and deployment, including blueprints, deployment stacks, and Azure resource graph.

Blueprints vs. Deployment Stacks

  • Blueprints are being replaced by deployment stacks.
  • Deployment stacks use deny effect instead of locking resources.
  • Deployment stacks group resources in a shared management lifecycle.

Removing Resources from Deployment Stack

  • When removing a resource from the scope of the deployment stack, there is an option to delete it or let it fall out of management.
  • Azure Resource Graph allows querying on configuration changes with Kusto query language (KQL).
  • There are limits on how many queries can be done per hour.

Querying with Azure Resource Graph

  • Azure Resource Graph lets users query the control plane using KQL through portal, PowerShell or CLI.
  • Users can find information about their environment by running queries such as finding unused public IPs.
  • The data is always current as events are fired off when things change.

Azure Advisor and Resource Changes

In this section, the speaker talks about how to use Azure Advisor to get guidance on performance, cost, security, reliability and operational excellence. The speaker also explains how to view resource changes in the portal and Resource Graph Explorer.

Using Azure Advisor

  • Azure Advisor provides recommendations for improving your environment.
  • It gives guidance on performance, cost, security, reliability and operational excellence.
  • You can access it from the Azure portal.
  • It is recommended that you check it at least weekly.

Viewing Resource Changes

  • You can view resource changes in the portal or Resource Graph Explorer.
  • The changes show what was changed and what was the before value.
  • This is useful for troubleshooting issues in your environment.

Governance Documentation and Landing Zones

In this section, the speaker talks about governance documentation and landing zones. Landing zones are a starting point with recommendations on how to lay out resources.

Governance Documentation

  • Governance documentation provides guidelines for managing your environment.
  • Links to governance documentation are provided in the description of the video.

Landing Zones

  • Landing zones provide recommendations on how to lay out resources.
  • They recommend certain subscriptions for identity or networking and applications for both enterprise scale and small-medium business scale.
  • Complete architectures of how you should layout your resources are provided.

Well-Architected Framework

In this section, the speaker talks about using Well-Architected Framework (WAF) as a guide for adopting cloud planning. WAF includes a review capability to see how architecture is leveraging different types of resources in the best way.

Well-Architected Framework (WAF)

  • WAF provides guidance for adopting cloud planning.
  • It includes a review capability to see how architecture is leveraging different types of resources in the best way.
  • Example architectures are provided.

Turn any video into a summary like this

YouTube links, meetings, lectures. With transcripts, search, and chat.

Video description

A deep dive into all things Governance around Azure. 👂 I have manually updated the captions to be as accurate as possible. Enable the subtitles and from there you can translate to your native language via the auto-translate feature in settings! https://youtu.be/v5b53-PgEmI for a demo of using this feature. 🔎 Looking for content on a particular topic? Search the channel. If I have something it will be there! ▬▬▬▬▬▬ C H A P T E R S ⏰ ▬▬▬▬▬▬ 0:00 - Introduction 0:57 - Why we need governance 7:25 - Understand requirements 12:10 - Management groups 19:26 - Subscriptions 26:15 - Resource Groups 31:51 - Using constructs for governance 33:13 - What can we do? 40:00 - Locking 45:15 - ARM 50:12 - Role-Based Access Control (RBAC) 1:05:35 - Attribute-Based Access Control (ABAC) 1:16:44 - Azure Policy 1:33:18 - Cost Management and Budgets 1:47:23 - Ways to optimize cost 1:55:30 - Naming standards 1:57:19 - Tagging 2:01:43 - Blueprints and Deployment Stacks 2:08:10 - Azure Resource Graph and Configuration Changes 2:13:00 - Azure Advisor 2:14:14 - Key resources 2:15:20 - Close ▬▬▬▬▬▬ K E Y L I N K S 🔗 ▬▬▬▬▬▬ ► Playlist for the Master Class: 🔗 https://www.youtube.com/playlist?list=PLlVtbbG169nGccbp8VSpAozu3w9xSQJoY ► GitHub Repo for handouts and other artifacts including the whiteboard: 🔗 https://github.com/johnthebrit/AzureMasterClass ► Compliance Overview: 🔗 https://www.microsoft.com/trust-center/compliance/compliance-overview ► Subscription limits: 🔗 https://docs.microsoft.com/azure/azure-resource-manager/management/azure-subscription-service-limits ► Pricing calculator: 🔗 https://azure.microsoft.com/pricing/calculator/ ► Governance documentation: 🔗 https://aka.ms/governancedocs ► Landing Zones: 🔗 https://learn.microsoft.com/azure/cloud-adoption-framework/ready/landing-zone/ ► Cloud Adoption Framework: 🔗 https://learn.microsoft.com/azure/cloud-adoption-framework/ ► Well Architected Framework: 🔗 https://learn.microsoft.com/azure/architecture/framework/ ► Azure Architecture Center: 🔗 https://learn.microsoft.com/azure/architecture/ ▬▬▬▬▬▬ Want to learn more? 🚀 ▬▬▬▬▬▬ 📖 Recommended Learning Path for Azure 🔗 https://learn.onboardtoazure.com 🥇 Certification Content Repository 🔗 https://github.com/johnthebrit/CertificationMaterials 📅 Weekly Azure Update 🔗 https://youtube.com/playlist?list=PLlVtbbG169nEv7jSfOVmQGRp9wAoAM0Ks ☁ Azure Master Class 🔗 https://youtube.com/playlist?list=PLlVtbbG169nGccbp8VSpAozu3w9xSQJoY ⚙ DevOps Master Class 🔗 https://youtube.com/playlist?list=PLlVtbbG169nFr8RzQ4GIxUEznpNR53ERq 💻 PowerShell Master Class 🔗 https://youtube.com/playlist?list=PLlVtbbG169nFq_hR7FcMYg32xsSAObuq8 🎓 Certification Cram Videos 🔗 https://youtube.com/playlist?list=PLlVtbbG169nHz2qfLvPsAz9CnnXofhmcA 🧠 Mentoring Content 🔗 https://youtube.com/playlist?list=PLlVtbbG169nGHxNkSWB0PjzZHwZ0BkXZZ ❔ Question about my setup? 🔗 https://youtube.com/playlist?list=PLlVtbbG169nHuSSHudxXDdn9Vz3T4-0mS 👕 Cure Childhood Cancer Charity T-Shirt Channel Store 🔗 https://johns-t-shirts-store.creator-spring.com/ SUBSCRIBE ✅ https://www.youtube.com/channel/UCpIn7ox7j7bH_OFj7tYouOQ?sub_confirmation=1 #microsoft #azure #johnsavillstechnicaltraining #onboardtoazure #cloud