1. Physical Components
1.1. Geographies
1.1.1. Meet data residency and compliance boundaries
1.1.2. Customers can select where their data is stored
1.1.3. Contains two or more **regions**
1.1.3.1. Region
1.1.3.1.1. Collection of **data centers**
1.1.3.1.2. Round
1.1.3.1.3. Provides flexibility and scale
1.1.3.1.4. Preserves data residency
1.1.3.1.5. Each region has **Region Pairs**
1.1.3.1.6. Tips
1.1.3.1.7. Special Regions
1.1.3.1.8. Has **Availability Zones**
1.1.3.1.9. Availability Sets
1.1.4. Putting Geography and Regions Together
1.1.4.1. Availability Zone in an Azure Region
2. Logical Components
2.1. Subscription
2.1.1. Azure Subscription
2.1.2. Logical container
2.1.3. Subscription links to Azure Active Directory (AAD) for authentication and authorization
2.1.4. Multiple subscriptions can be created by the account holder
2.1.4.1. Useful for?
2.1.4.1.1. To be able to report on resources used by specific groups of people
2.1.5. Subscription options
2.1.5.1. Pay-as-you-go
2.1.5.1.1. Billed monthly to a credit card
2.1.5.2. Free account
2.1.5.2.1. 12 months, $260 credits per month, over 25 free services
2.1.5.3. Member offers
2.1.5.3.1. Use monthly credits, monthly billing, and more
2.1.6. Subscription considerations
2.1.6.1. Be aware of the service limits for each subscription type
2.1.6.2. Pay-as-you-go subscription by default only allows for 20 vCPUs
2.1.6.3. Some limits can be raised
2.1.7. Subscription Billing Boundary
2.1.7.1. Subscription is applied to group
2.1.7.1.1. Isolate billing to specific group (e.g., specific special project)
2.1.8. Subscription Access Control Boundary
2.1.8.1. Subscriptions are applied to organizational departments
2.1.8.1.1. Departments billed individually
2.2. Management groups
2.2.1. Group Azure objects in a collection
2.2.1.1. Contains subscriptions or other management groups
2.2.1.1.1. Example
2.2.1.1.2. Example: Management groups organizing subscriptions and other management groups
2.2.1.2. Manage policies, access, and compliance for the entire group
2.2.2. Limitations
2.2.2.1. You're limited to a total of 10,000 management groups
2.2.2.2. A management group hierarchy can only support up to **six** levels
2.2.2.3. You cannot have multiple parents for a single management group or subscription
2.3. Resource groups
2.3.1. What is it?
2.3.1.1. Logical container for Azure services
2.3.2. What is it for?
2.3.2.1. Deploy, manage, and monitor resources in a group
2.3.2.1.1. Structure
2.3.2.1.2. Able to easily set up deployments using ARM template
2.3.3. Properties
2.3.3.1. Resources should have the same lifespan
2.3.3.2. Each resource can only exists in a single resource group
2.3.3.2.1. But resources can be moved between resource groups
2.3.3.3. Resources can be assigned to **different regions within the resource group**
2.3.3.4. Deleting a resource group deletes all the resources in the group
2.4. Azure Resource Manager (ARM)
2.4.1. Management layer that is used to access and manage Azure resources
2.4.2. Create, update, delete, organize, manage, control, and tag resources in the Azure subscription
2.4.2.1. Example?
2.4.2.1.1. When creating a new web app in Azure App Service, ARM will pass your request to *Microsoft.Web * **resource provider**, because it knows all about web apps and how to create them
2.4.3. Can be accessed using...
2.4.3.1. Azure Portal (Web UI)
2.4.3.2. Azure PowerShell (CLI)
2.4.3.3. Azure Command-Line Interface (CLI)
2.4.3.4. REST Clients
2.4.4. The tools, Azure API, ARM, Resource Provider, and Azure Resources
2.4.5. Benefits
2.4.5.1. ARM allows you to easily deploy multiple Azure resources at once
2.4.5.2. ARM makes it possible to reproduce any deployment with consistent results at any point in the future
2.4.5.3. ARM allows you to create **declarative templates** for deployment instead of requiring you to write and maintain complex deployment scripts
2.4.5.4. ARM makes it possible to set up dependencies so that your resources are deployed in the right order every time
2.5. Overview
2.6. Azure Marketplace
2.6.1. Partners, solution providers, and Independent Software Venders (ISVs) can offer customized solutions
3. Core Resources
3.1. Compute Resources
3.1.1. Common services for compute
3.1.1.1. Virtual Machines
3.1.1.1.1. IaaS
3.1.1.1.2. Physical computer that is virtualized
3.1.1.1.3. Includes...
3.1.1.1.4. Managed the same as physical machine
3.1.1.1.5. Susceptible to...
3.1.1.1.6. Availability Sets
3.1.1.1.7. Scale Set
3.1.1.2. Azure App Service
3.1.1.2.1. PaaS
3.1.1.2.2. Build enterprise-grade web, mobile, API apps on any platform
3.1.1.2.3. Azure provides a fully managed, secure, and scalable platform for the apps
3.1.1.2.4. Allows you to choose between a VM preconfigured with runtime stack (e.g., Java, .NET, etc.) or a Docker container
3.1.1.2.5. Azure Functions
3.1.1.2.6. How does it work?
3.1.1.3. Containers
3.1.1.3.1. Concepts
3.1.1.3.2. Azure Services for Containers
3.1.1.4. Windows Virtual Desktop (WVD)
3.1.1.4.1. Windows 10 desktop hosted in Azure
3.1.1.4.2. Support remote work
3.1.1.4.3. VMs are fully managed and scalable
3.1.1.4.4. Illustration
3.1.1.4.5. Creation
3.1.1.4.6. FSLogix
3.1.2. Provide compute resources
3.1.2.1. Disks
3.1.2.2. Processors
3.1.2.3. Memory
3.1.2.4. Operating Systems
3.1.2.5. Networking
3.1.3. On-demand service for running cloud-based apps
3.2. Networking Resources
3.2.1. Virtual Networks
3.2.1.1. Isolates and segments Azure resources within the network
3.2.1.2. Connects various Azure resources and on-premises
3.2.1.3. Provides filtering and routing of network traffic
3.2.1.4. Contained ONLY to one **Region**
3.2.1.4.1. Virtual networks CAN NOT span multiple regions
3.2.1.4.2. **Virtual Network Peering** or **VPN Gateway** can be used to connect different regions
3.2.1.5. Illustration
3.2.1.5.1. All of the resources in VNet A can communicate with each other
3.2.1.5.2. All of the resrources in VNet B can communicate with each other
3.2.1.5.3. The resources in VNet A **CAN NOT** communicate with the resources in VNet B, and vice versa
3.2.2. VPN Gateway
3.2.2.1. Traffic is encrypted
3.2.2.2. Only one VPN gateway is allowed per virtual network
3.2.2.2.1. workaround for this limitation?
3.2.2.3. Illustration
3.2.2.3.1. Add **VPN Gateway** to connect our resources in VNet A to our on-premises environments
3.2.2.3.2. We can also allow VPN clients to access our resources in Azure
3.2.2.3.3. It's also possible to connect VNet A to another virtual network in Azure (e.g., VNet B)
3.2.2.4. Three connection types
3.2.2.4.1. VNet-to-VNet
3.2.2.4.2. site-to-site
3.2.2.4.3. point-to-site
3.2.3. Network Peering
3.2.3.1. Virtual network peering
3.2.3.1.1. Connect virtual networks in the same region
3.2.3.2. Global virtual network peering
3.2.3.2.1. Connect virtual networks across regions
3.2.3.3. Traffic is private
3.2.3.3.1. Never transverses the internet
3.2.3.4. Traffic travels over Microsoft's backbone infrastructure instead of the Internet
3.2.3.4.1. ...but not encrypted!
3.2.4. ExpressRoute
3.2.4.1. Provide private connection to Azure and Microsoft 365
3.2.4.2. Connectivity provider
3.2.4.2.1. Data does not transverse the public internet
3.2.4.3. Lower latency
3.2.4.4. Higher bandwidth
3.2.4.4.1. up to a max of 10 Gbps (can be adjusted)
3.2.4.5. Microsoft calls an ExpressRoute connection a *circuit *
3.2.4.5.1. Typical ExpressRoute configuration MSEE = Microsoft Enterprise Edge
3.3. Storage Resources
3.3.1. Stores files, messages, and tables
3.3.2. Properties
3.3.2.1. Secure
3.3.2.2. Massively scalable
3.3.2.3. Highly available
3.3.2.4. Highly durable
3.3.3. Supported Data Types
3.3.3.1. Structured data
3.3.3.1.1. Has a schema
3.3.3.1.2. Rigid format
3.3.3.1.3. Relational data
3.3.3.1.4. Typical usage: **Database**
3.3.3.2. Semi-structured data
3.3.3.2.1. Ad-hoc schema
3.3.3.2.2. Non-relational format
3.3.3.2.3. Known as NoSQL data
3.3.3.2.4. Uses tags for data location
3.3.3.2.5. Typical usage: Tab delimited files, **CSV**, **XML**, and **JSON**
3.3.3.3. Unstructured data
3.3.3.3.1. No schema or data structure
3.3.3.3.2. examples
3.3.4. Storage Services
3.3.4.1. **Blob**
3.3.4.1.1. Used for **unstructured data**
3.3.4.1.2. Highly scalable
3.3.4.1.3. Microsoft recommends blob storage for most scenarios
3.3.4.1.4. Types
3.3.4.1.5. Means of storage
3.3.4.1.6. Tips
3.3.4.1.7. Common uses...
3.3.4.1.8. Tiers
3.3.4.1.9. Blob Storage Lifecycle
3.3.4.2. **Disk storage**
3.3.4.2.1. Provides persistent storage for Azure virtual machine disks
3.3.4.2.2. Attach a data disk to VMs for storing data
3.3.4.2.3. All Azure disks are backed by page blobs in Azure Storage
3.3.4.2.4. Types
3.3.4.2.5. Managed vs. unmanaged disks
3.3.4.3. **Azure Files**
3.3.4.3.1. Backed by Azure Storage
3.3.4.3.2. Uses **Server Message Block (SMB)** protocol
3.3.4.3.3. Fully managed **file share**
3.3.4.3.4. Lift and shift
3.3.4.3.5. Supports multiple connections
3.3.4.3.6. Example
3.3.4.3.7. Possible problem
3.3.4.4. Table
3.3.4.5. Queue
3.4. Database Resources
3.4.1. PaaS offerings
3.4.2. Fully managed
3.4.3. Types
3.4.3.1. NoSQL
3.4.3.1.1. Database Types
3.4.3.1.2. Cosmos DB
3.4.3.2. Relational
3.4.3.2.1. Azure SQL Database
3.4.3.2.2. Azure Database for MySQL
3.4.3.2.3. Azure Database for PostgreSQL
4. Azure Marketplace
4.1. A single repository containing services provided by **third-party vendors**
4.2. All templates in the Azure Marketplace are ARM templates that deploy one or more Azure services
4.2.1. Some templates deploy a single resource
4.2.1.1. e.g., Web App template
4.2.2. Other templates create many resources that combine to make an entire solution