Management and Governance Flashcards
Factors that affect cost in Azure
- Azure shifts development costs from CapEx to an OpEx, as customer rent the infrastructure they need
- This OpEx cost can be affected by:
- Resource Type: the type of resource, its settings and the Azure region all impact how much a resource costs.
- Consumption: pay-as-you-go. Consuming more in one billing cycle will cost more. Reserved capacity can lead to discounts.
- Maintenance: customer’s ability to maintain their cloud environment (e.g. shutting down resources not being used anymore)
- Geography: Azure resources differ based on location, due to the differing costs of running datacenters in different locations.
- Network Traffic: Inbound and outbound traffic moving between billing zones
- Subscription type: certain subscriptions include free allowances, such as trial subscriptions.
- Azure Marketplace: let’s customers purchase Azure-based solutions from 3rd party vendors. Pay for the resources but also the expertise of the 3rd party
Pricing calculator vs TCO calculator
- Pricing calculator: designed to give customers an estimated cost for provisioning resources
- TCO calculator: helps customers compare the cost of running on-prem infra with their cloud setup
Microsoft Cost Management
- Provides the ability to quickly check Azure resource costs, create alerts based on resource spend, and create budgets that can be used to automate management of resources
Resource tags
Tags provide extra information, or metadata, about resources. They are useful for:
- Resource management - locate and act on resources that are associated with specific workloads, environments, business units and owners
- Cost management - group resources and report on costs, allocate to internal cost centers, track budgets etc.
- Operations management - group resources according to their criticality to the business. Helps for SLA formulation
- Security - classify data by its security level
- Governance & regulatory compliance - identify resources that align with governance or regulatory compliance requirements
- Workload optimisation/automation: visualise all of the resources that participate in complex deployments
Microsoft Purview
- Family of data governance, risk and compliance solutions that give a single, unified view of data across Azure, on-prem, multi-cloud and SaaS
- Purview risk and compliance: protect sensitive data, identify risks and manage regulatory requirements
- Purview unified data governance: map out entire data estate, classify data, end-to-end lineage, identify sensitive data, create a secure environment for customers to find valuable data, generate insights about how data is stored, manage access to the data securely and at scale
Azure Policy
- Create, assign and manage policies that control or audit resources. Policies are enforced across resource configurations to ensure those configs stay compliant with corporate standards.
- Evaluate resources and highlight those that aren’t compliant with policies, also prevent noncompliant resources from being created
- E.g. VMs in a certain environment are only allowed to be a certain size; all apps must be tagged with the AppName
- Azure Policy Initiatives is a way of grouping policies together (e.g. monitor: unencrypted SQL databases + OS vulnerabilities + servers with missing endpoint protection)
Resource Locks
- Prevents a resource from being accidentally deleted or changed
- Even with RBAC, there is a risk people will delete/change critical cloud resources. Resource locks prevent this. They can be applied to resources, resource groups, or an entire subscription
- Two types of resource locks:
- Delete: authorised users can read and modify a resource, but can’t delete it
- ReadOnly: authorised users can read a resource, but can’t change or delete it.
- To delete/update a locked resource, the lock must be removed first
Service Trust Portal
- A portal that provides access to various content, tools and other resources about Microsoft security, privacy and compliance practices
- Contains details about Microsoft’s implementation of controls and processes that protect their cloud services and customer data therein
Tools for interacting with Azure (4)
- Azure portal - web-based console. Can build, manage and monitor all resources, create dashboards of organisational resources, configure accessibility options
- Azure Cloud Shell - browser-based shell tool that allows for creation, configuration, and management of Azure resources using a shell. Supports both Powershell and Azure CLI (bash)
- Azure Powershell - a shell where users can run command-lets (cmdlets), which call the Azure REST API to perform management tasks.
- Azure CLI - same functionality as Powershell but uses Bash commands
Azure Arc
- Allows customer to extend Azure compliance and monitoring to a hybrid or multi-cloud environment
- Provides a centralised way to:
- Manage entire environment by projecting existing non-Azure resources into Azure Resource Manager (ARM)
- Manage multi-cloud and hybrid virtual machines, K8s clusters, and databases
- The following resource types (sitting outside of Azure) can be managed via Arc:
- Servers
- Kubernetes clusters
- Azure data services
- SQL Server
- Virtual machines
Azure Resource Manager (ARM)
- The deployment and management service for Azure. Provides the management layer that enables customers to create, update and delete resources in their Azure account. Anytime anything is done to Azure resources, ARM is involved.
- When a user sends a request from any of the Azure tools, APIs or SDKs, ARM receives the request, authenticates, authorises and sends the request to the Azure service.
- ARM allows for users to leverage Infrastructure as Code mechanisms such as ARM templates, Bicep and Terraform to deploy and manage resources
Azure Advisor
- Evaluates Azure resources and makes recommendations to help improve reliability, security, and performance
- Includes a dashboard on the Azure portal that provides a view of all resources and includes suggested actions that can be taken to, which saves time on cloud optimisation.
- Types of recommendations include:
- Reliability to ensure continuity of applications
- Security: detect threats and vulnerabilities
- Performance: improve the speed of applications
- Operational Excellence: help achieve process and workflow efficiency, resource manageability and deployment best practices
- Cost: optimise and reduce Azure spending
Azure Service Health
Helps customers keep track of Azure resources globally, both specifically deployed resources and the overall status of Azure.
- Azure Status: broad picture of Azure globally (e.g. outages, incidents etc)
- Service Health: provides a view of Azure services and regions being used by the customer
- Resource Health: tailored view of a customer’s actual Azure resources
Azure Monitor
- Platform for collecting data on a customer’s resources, analysing that data, visualising and acting on the results. Includes:
- Azure Log Analytics: tool where customers can write and run log queries on data gathered by Azure monitor
- Azure Monitor Alerts: automated way to stay informed when Azure Monitor detects a threshold being crossed.
- Application Insights: monitors customer’s web applications (either Azure, on-prem or other cloud). An SDK or Applications Insights agent is installed in the application, which can monitor app information such as: request data, response times, failure rates, page views and load times, user and session counts, performance counters from Windows/Linux servers