Microsoft Azure Basics

Introduction

• Overview of core building blocks in Microsoft Azure: Tenants, Subscriptions, and Resource Groups.
• Importance of understanding these elements for building a strong foundation in Azure.
• Focus on Infrastructure-as-a-Service (IaaS) but will touch on Platform-as-a-Service (PaaS).

Microsoft Azure Overview

• Microsoft Azure: A cloud platform providing both IaaS and PaaS components.
• Emphasis on IaaS products: VMs, disks, networks, virtual network cards.
• PaaS includes server-less offerings like Azure Files and Azure SQL.

Structure of Azure

Tenant/Directory

• Tenant (also called Directory) is the top-level structure in Azure.
  • Format example: @nerdio1013.onmicrosoft.com.
  • Each tenant has a unique ID (global uniqueness).
  • Associated with Azure Active Directory (AD), which integrates with all Microsoft Services, including Office 365.

Subscriptions

• Subscriptions allow users to leverage Azure resources.
• Types of subscriptions:
  • CSP Subscription: Provided by resellers, lacks cost visibility for end-users.
  • Free Trial Subscription: $200 credit for Azure.
  • Pay As You Go Subscription: Charges based on consumption.
  • Enterprise Agreement (EA): Negotiated and paid upfront.
• Subscriptions serve as a billing structure; resources must reside within a subscription.

Resource Groups

• Resource Groups are created to organize resources within a subscription.
  • Functionally focused grouping for related resources (e.g., applications).
  • Visual representation: Subscription > Resource Groups > Resources.
• Billing occurs at the subscription level, resources are segregated within resource groups.

User Access and Roles

• Users are managed at the tenant level in Azure AD.
• Access to subscriptions is controlled through role assignment (e.g., ownership roles).
  • Example: User must be an owner to provision NFA.

Deployment Models: Hoteling vs. Single Stack

Hoteling Model

• Shared Active Directory environment with segregations.
• Allows for shared resources but increases complexity and risk.
• Pros and Cons:
  • Pros: Cost-effective resource sharing.
  • Cons: Risk of impacting multiple customers with changes.

Single Stack Model

• Completely independent deployments for each customer.
• Pros:
  • Elimination of complexity and risk.
  • Complete isolation between customers.
  • Easier management with NAP (No Application Protection).
  • Improved compliance for audits.
  • More flexibility in architecture and pricing.
• Cons:
  • Increased infrastructure costs due to separate resources.
  • Learning curve for managing separate environments.

Conclusion

• Understanding tenants, subscriptions, and resource groups is critical for effective Azure deployment.
• Choosing between hoteling and single stack has significant implications on cost, complexity, and operational risks.