Azure Cloud Computing

Table of Contents

1. Introduction to Azure Cloud
2. Azure Core Concepts
   • Resource Groups
   • Regions and Availability Zones
3. Azure Services Overview
   • Compute Services
   • Storage Services
   • Networking Services
4. Getting Started with Azure
   • Creating an Azure Account
   • Azure Portal Overview
   • Using Azure CLI
5. Deploying Your First Virtual Machine (VM)
6. Conclusion
7. Managing Azure Cloud with Terraform
8. Azure Cloud Monitoring and Logging
9. Azure Cloud Security
10. Inroduction to Azure Devops

This module introduces you to cloud computing. It covers things such as cloud concepts, deployment models, and understanding shared responsibility in the cloud.

Introduction to Azure Cloud

Azure is a cloud computing platform by Microsoft, offering a wide range of services such as virtual machines, storage, networking, and databases. It enables businesses to build, deploy, and manage applications in a scalable, secure, and global environment.

Azure offers services under three primary models:

1. Infrastructure as a Service (IaaS)
2. Platform as a Service (PaaS)
3. Software as a Service (SaaS)

Azure Core Concepts

Resource Groups

A Resource Group is a logical container used to organize and manage Azure resources (like virtual machines, databases, and storage accounts). All the resources inside a resource group share the same lifecycle—meaning you can deploy, update, or delete them together.

Here’s how you can create a resource group:

az group create --name myResourceGroup --location eastus

Regions and Availability Zones

• Regions: Azure has data centers around the globe. A region is a specific geographical location where Azure resources are hosted. When you deploy resources, you must choose a region to locate them.

• Availability Zones: These are isolated locations within a region. They provide redundancy and protect resources from data center failures.

1. Availability Zones

• Definition: Availability Zones are unique physical locations within an Azure region, each comprising one or more datacenters with independent power, cooling, and networking.
• Purpose: They protect applications and data from datacenter failures within a region. Placing resources in different zones ensures applications stay available even if one zone fails.
• Use Case: Ideal for applications requiring high availability and low-latency replication, such as those with a 99.99% SLA or needing rapid failover.
• Fault Isolation: Each zone is isolated to prevent failure in one zone from impacting others.

2. Availability Sets

• Definition: An Availability Set is a logical grouping of VMs within a datacenter that allows Azure to understand how your application is built to provide redundancy.
• Purpose: Protects against hardware and software failures within a single datacenter. Azure distributes VMs in an Availability Set across multiple Update Domains and Fault Domains.
  • Fault Domain: A group of resources that share a common power source and network switch, isolated from other fault domains.
  • Update Domain: A set of resources that can undergo maintenance or updates independently from other update domains.
• Use Case: For workloads requiring a high degree of reliability within a single datacenter, with an SLA of up to 99.95% uptime.

Summary

• Availability Zones: Cross-datacenter redundancy within a region for ultra-high availability.
• Availability Sets: Redundancy within a single datacenter to protect against localized failures.

Cloud Computing Basics: AWS, Azure, Google, Oracle

Cloud computing is a way to get IT services like computing power, storage, and databases over the internet, paying only for what you use. Instead of buying and maintaining physical data centers and servers, you can access these services from various providers. To start learning cloud computing, you can choose from popular providers such as Amazon Web Services (AWS), Microsoft Azure, Google Cloud Platform (GCP), or Oracle Cloud.

Cloud computing has revolutionized the way we access IT services, offering a flexible, scalable, and cost-effective alternative to traditional IT setups. In this blog, we’ll explore the essentials of cloud computing, its benefits over traditional architecture, and guide you through choosing the right cloud service and deployment models.

What is Traditional Architecture?

Traditional IT infrastructure comprises physical hardware and software components, including data centers, servers, networking hardware, and enterprise applications. Maintaining such an infrastructure involves significant costs and challenges:

Problems With Traditional Architecture

• Recurring Costs: Ongoing expenses for data center rent can be significant.
• Operational Expenses: Costs for power supply, cooling, and maintenance can quickly add up.
• Hardware Management: Adding or replacing hardware can be time-consuming and complex.
• Scaling Challenges: Scaling up resources is often limited and can require substantial lead time.
• Infrastructure Monitoring: A dedicated team is needed to continuously monitor and maintain the infrastructure.
• Disaster Preparedness: How do you effectively manage disasters such as earthquakes, power outages, or fires?

How Cloud Computing Overcomes the Problems of Traditional Architecture

1. Lower IT Costs:
   The cloud allows organizations to offload many costs associated with maintaining on-premises infrastructure, including purchasing, installing, configuring, and managing hardware. This shift can lead to substantial savings, as businesses only pay for what they use, reducing capital expenditures and ongoing operational costs

2. Improved Agility and Time-to-Value:
   With cloud computing, organizations can deploy enterprise applications almost instantly, significantly reducing the time needed to respond to IT requests. Instead of waiting weeks or months for hardware and software setup, users—particularly developers and data scientists—can provision resources on demand, enhancing productivity and innovation

3. Scalability and Cost-Effectiveness:
   The elasticity of cloud services enables businesses to scale their resources up or down based on current demand, effectively managing traffic spikes and dips without investing in excess capacity that may sit idle. This flexibility not only optimizes resource use but also ensures that organizations can adapt to changing business needs in real time

Characteristics of Cloud Computing

1. On-Demand Self-Service
   ![On-Demand Icon] Users can provision resources automatically as needed without requiring human interaction from the service provider.

2. Broad Network Access
   ![Network Access Icon]
   Cloud services are available over the network and can be accessed through standard mechanisms (e.g., mobile phones, tablets, laptops).

3. Resource Pooling
   ![Resource Pooling Icon]
   The provider’s computing resources are pooled to serve multiple consumers using a multi-tenant model, with different physical and virtual resources dynamically assigned according to demand.

4. Rapid Elasticity
   ![Elasticity Icon]
   Resources can be elastically provisioned and released to scale rapidly outward and inward commensurate with demand.

5. Measured Service
   ![Measured Service Icon] Cloud systems automatically control and optimize resource use by leveraging a metering capability at some level of abstraction appropriate to the type of service.

6. Security and Compliance
   ![Security Icon] Cloud providers implement robust security measures to protect data and comply with industry standards and regulations.

7. Cost Efficiency
   ![Cost Efficiency Icon] With a pay-as-you-go model, businesses can save on upfront capital costs and reduce the overall cost of IT infrastructure.

8. High Availability
   ![High Availability Icon] Cloud computing services are designed for high availability and reliability, ensuring minimal downtime for users.

Conclusion

Cloud computing offers flexible, scalable, and cost-effective solutions, enabling organizations to innovate faster and focus on core business activities rather than managing infrastructure.

Cloud Service Models

Cloud computing is categorized into three primary service models, each serving different business needs and technical requirements:

1. Infrastructure as a Service (IaaS)

IaaS provides virtualized computing resources over the internet. It offers the fundamental building blocks of computing, including:

• Compute: Virtual machines with various configurations.
• Storage: Options for data storage like block, file, and object storage.
• Networking: Virtual networks, load balancers, and firewalls.

Key Features:

• Scalability: Easily scale up or down based on demand.
• Control: Provides users with greater control over the infrastructure.

Example Providers: Amazon Web Services (AWS), Microsoft Azure, Google Cloud Platform (GCP).

2. Platform as a Service (PaaS)

PaaS offers a platform allowing customers to develop, run, and manage applications without the complexity of building and maintaining the underlying infrastructure.

Key Features:

• Development Tools: Integrated development environments (IDEs) and application hosting.
• Middleware: Services that help manage application operations.

Example Providers: Google App Engine, Microsoft Azure App Service, Heroku.

3. Software as a Service (SaaS)

SaaS delivers software applications over the internet, on a subscription basis. Users access the software via a web browser, eliminating the need for installation and maintenance.

Key Features:

• Accessibility: Accessible from any device with internet connectivity.
• Automatic Updates: Providers manage the infrastructure, security, and updates.

Example Providers: Salesforce, Google Workspace, Microsoft 365.

Conclusion

Understanding these cloud service models helps businesses choose the right solution based on their operational needs and technical requirements.

Cloud Deployment Models

Cloud deployment models define how cloud services are provided and utilized. The main types of cloud deployment models are:

1. Public Cloud

In a public cloud deployment, the services and infrastructure are provided off-site over the internet and shared across multiple organizations. The cloud provider manages everything, and users pay for the resources they consume.

Key Features:

• Cost-Effective: No capital expenditure, only operational costs.
• Scalability: Easily scalable to accommodate varying workloads.

Example Providers: Amazon Web Services (AWS), Microsoft Azure, Google Cloud Platform (GCP).

2. Private Cloud

A private cloud is dedicated to a single organization and can be hosted either on-premises or off-site. It offers more control over data security and privacy but requires a higher capital investment.

Key Features:

• Enhanced Security: Greater control over sensitive data and compliance.
• Customization: Tailored to specific business needs.

Example Use Cases: Enterprises with strict regulatory requirements or sensitive data management.

3. Hybrid Cloud

The hybrid cloud model combines both public and private clouds, allowing data and applications to be shared between them. This offers greater flexibility and more deployment options.

Key Features:

• Flexibility: Businesses can leverage both environments based on their needs.
• Cost Efficiency: Balance between cost and performance by utilizing both public and private resources.

Example Use Cases: Organizations that need to handle varying workloads and want to maintain control over sensitive data while leveraging public resources for other applications.

4. Community Cloud

A community cloud is shared among several organizations with similar requirements, often within the same industry. It can be managed internally or by a third-party provider.

Key Features:

• Cost Sharing: Organizations share the costs of infrastructure and services.
• Collaboration: Facilitates collaboration among organizations with shared interests or requirements.

Example Use Cases: Government agencies or educational institutions sharing resources for collaborative projects.

Conclusion

Understanding the different cloud deployment models allows organizations to choose the right mix of solutions based on their business needs, security requirements, and budget constraints.

Well-Architected Framework

The Well-Architected Framework (WAF) is a set of best practices created by Amazon Web Services (AWS) to assist cloud architects in building secure, high-performing, resilient, and efficient infrastructure for their applications. The framework is divided into five key pillars:

1. Operational Excellence

• Focus: Emphasizes running and monitoring systems to deliver business value and continuously improve processes and procedures.
• Key Practices: Implement automation, monitoring, incident response, and evolve procedures based on feedback.

2. Security

• Focus: Protects data, systems, and assets while delivering business value through risk assessments and mitigation strategies.
• Key Practices: Implement strong identity and access management, use encryption for data protection, and maintain compliance with regulations.

3. Reliability

• Focus: Ensures a workload performs its intended function correctly and consistently when expected.
• Key Practices: Design systems for failover and recovery, implement backups, and use redundancy to minimize the impact of failures.

4. Performance Efficiency

• Focus: Utilizes IT and computing resources efficiently to meet system requirements and maintain that efficiency as demand changes and technologies evolve.
• Key Practices: Select the right resource types and sizes, monitor performance, and adjust resources dynamically to meet demand.

5. Cost Optimization

• Focus: Avoids unnecessary costs by understanding where money is spent and eliminating unneeded expenses.
• Key Practices: Monitor and analyze costs, implement resource optimization strategies, and use pricing models effectively.

Conclusion

By following the Well-Architected Framework, organizations can enhance their cloud architectures’ resilience, efficiency, and security. AWS provides a Well-Architected Tool that helps review workloads against these best practices, offering insights and recommendations to improve architecture.

For further details, check the official AWS Well-Architected Framework documentation.

Pillars of Cloud Computing

The pillars of cloud computing refer to essential principles that guide the design, deployment, and management of cloud services. Below are the primary pillars:

1. Cost Efficiency

• Organizations can reduce costs associated with hardware and software by utilizing cloud services, which operate on a pay-as-you-go model. This allows businesses to scale resources based on demand without significant upfront investments.

2. Scalability

• Cloud computing offers the ability to scale resources up or down quickly based on usage. This elasticity is crucial for businesses that experience variable workloads, enabling them to accommodate peak demands without overprovisioning.

3. Performance

• Cloud providers typically offer robust infrastructure and high availability, ensuring that applications run efficiently and with low latency. They also provide various tools for monitoring and optimizing performance.

4. Security

• Security is a critical pillar, as cloud providers implement a range of security measures to protect data and applications. This includes identity and access management, encryption, and compliance with industry regulations.

5. Reliability

• Cloud services are designed to be reliable, with built-in redundancies and backup solutions to ensure continuity. This minimizes downtime and enhances the overall resilience of applications.

6. Flexibility

• The cloud allows organizations to deploy applications and services quickly without the constraints of physical infrastructure. This flexibility supports innovation and rapid experimentation.

Conclusion

Understanding these pillars is essential for organizations looking to leverage cloud computing effectively. They serve as a foundation for building cloud strategies that optimize resources and improve overall operati

AZ-104: Microsoft Azure Administrator Exam Table of Contents

1. Manage Azure identities and governance

• Azure Active Directory (Azure AD)
• Managing users and groups
• Implementing role-based access control (RBAC)

2. Implement and manage storage

• Azure Storage accounts
• Blob storage and file shares
• Data protection strategies

3. Deploy and manage Azure compute resources

• Configuring virtual machines (VMs)
• Azure App Services
• Azure Kubernetes Service (AKS)

4. Configure and manage virtual networking

• Virtual networks
• Network security groups (NSGs)
• Azure DNS and VPN gateways

5. Monitor and maintain Azure resources

• Azure Monitor
• Azure Security Center
• Troubleshooting issues

AZ-305: Designing Microsoft Azure Infrastructure Solutions Exam Table of Contents

1. Design identity and security

• Design identity and access management solutions
• Design security for applications and services
• Design security for data and networks

2. Design data storage solutions

• Design data storage solutions for relational data
• Design data storage solutions for non-relational data
• Design for data retention and archiving

3. Design business continuity solutions

• Design backup and disaster recovery solutions
• Design high availability solutions

4. Design infrastructure solutions

• Design virtual networks
• Design network security
• Design compute solutions

5. Design monitoring and management solutions

• Design monitoring solutions for applications and infrastructure
• Design management solutions for Azure resources