Azure Cloud Foundations & Identity-Centric Infrastructure – Day 1 Overview

Chapter 1 – Introduction & Business Context

  • Instructor greets learners and sets expectations for multi-day program.

  • Goal of Day 1: provide a full roadmap of the topics that will be covered, from fundamentals to advanced automation.

  • Key metaphor: any modern company (e.g.

    • Amazon (.ca, .in)
    • Facebook
    • A proposed AI-driven learning platform) is ultimately “an application running somewhere in the backend.”
  • Basic business pipeline:

    • Company develops an app ➜ hosts it on servers ➜ customers consume it ➜ company earns revenue.
    • Example SaaS plan for the instructor’s own AI learning platform: customers pay subscription fees; solution is hosted in instructor’s data-center; customers only receive a secure URL.
  • Role of infrastructure/operations (“infra ops”) engineers:

    • Keep applications highly available, secure, and resilient whether on-prem, AWS, Azure, or other.

Chapter 1 (cont.) – What an On-Premises Environment Looks Like

  • Typical on-prem layout drawn on virtual whiteboard:

    • Application tier examples:
    • Web Server (IIS, Apache, NGINX, etc.)
    • Database Server (SQL, Oracle, MySQL, etc.)
    • Infrastructure tier examples:
    • Windows Server or Linux VMs on VMware/Hyper-V (virtual) or bare-metal (physical).
    • Firewalls.
    • File servers and numerous ancillary servers.
    • Identity & Security core: Active Directory Domain Services (AD DS)
    • Every employee receives a user account in AD.
    • Corporate laptops are domain-joined; only domain-joined devices can access internal resources.
    • AD handles Authentication (who are you?) and Authorization (are you allowed?).
  • Implicit prerequisite for any new company: deploy AD DS first.


Chapter 1 – Challenges of Staying On-Premises

  • Capital & operational expense (CapEx & OpEx):

    • Building/renting data-centers, buying hardware, refresh cycles, disposal.
  • Limited elasticity:

    • Hard to upscale/ downscale quickly.
  • Asset liquidation difficulty when projects end.

  • Therefore many organizations plan or are in process of cloud migration.


Chapter 2 – Cloud-Hosted & SaaS Applications

  • Real-world example of third-party SaaS: ADP\text{ADP} payroll portal.

    • Users often juggle separate credentials for every external service.
  • Desire: “1 set of corporate credentials everywhere.”

    • Achieved via cloud Identity providers & federation (e.g., SAML 2.0, OIDC).
  • Microsoft solution stack terminology:

    • Azure Active Directory (Azure AD) → renamed Entra ID (Instructor may still say “AAD” casually).
    • Entra ID is the “heart” of all Microsoft cloud services.
    • Any Azure subscription, Microsoft 365 (Office 365), SharePoint Online, etc., automatically creates/uses an Entra tenant.
  • Advantages of Entra ID for SaaS & SSO:

    • Single Sign-On (SSO) to thousands of SaaS apps.
    • Central MFA, conditional access, risk-based policies.

Chapter 2 – First Tasks in a New Azure Tenant

  1. Tenant creation / Trial sign-up.
  2. Receive default Microsoft-hosted domain name: <tenant>.onmicrosoft.com\text{<tenant>.onmicrosoft.com}.
  3. Custom Domain Verification:
    • Purchase vanity domain from registrar (e.g., GoDaddy).
    • Add DNS TXT record ➜ Verify inside Entra ID.
    • End-user UPN becomes e.g., akash@vreachidtech.com (better branding & trust than onmicrosoft domain).
  4. Branding the Sign-in Page:
    • Add corporate logo, background, footers to avoid confusion (“Why is Microsoft logo here?”)

Chapter 3 – Securing the Cloud Identity Layer

  • Threat model: stolen/guessed credentials → attacker can fully compromise tenant.

  • Mandatory controls:

    1. Multifactor Authentication (MFA) for ALL users, incl. executives (no exceptions).
    • Phone call, SMS, Microsoft Authenticator push, FIDO2 keys, etc.
    1. Strong password policies & complexity rules.
    2. Account lockout settings (after nn failed attempts).
    3. Identity Protection:
    • User Risk policy.
    • Sign-in Risk policy (e.g., impossible travel: Canada ➜ India in 1 hour).
    1. Alerts & ticketing integration; cloud engineers must investigate anomalies.

Chapter 3 – Planning Roles & Access in Azure (RBAC)

  • On-prem equivalents:

    • DBA, Server Admin, VMware Admin, Network Admin…
  • Azure needs similar—but cloud-native—roles via Role-Based Access Control (RBAC).

  • Example role definitions brainstormed live:

    1. Cloud Users (Read-Only) – project managers, app leads, VPs; can view VMs, backups, networks.
    2. Cloud Ops L3 – senior engineers; full deploy/manage rights (VM, network, backup, DR, automation).
    3. Cloud Ops L2 – handle day-to-day run-books.
    4. Command Center / NOC – first-line triage & ticket routing.
    5. Cloud DB Team – manage PaaS DB services only.
    6. Cloud Security L1/L2/L3 – exclusive rights over Entra ID, Conditional Access, app registrations.
    7. Cloud Engineering / Architecture – design blueprints, DMZs, networking, automation; build once then handoff.
  • Key process:

    • Define role ➜ Map required Azure built-in or custom permissions ➜ Implement via Groups not direct user assignment.

Chapter 4 – Group-Based Administration Workflow

  • Create security groups (on-prem AD or Entra ID): e.g., SG-Cloud-Security-Admins.

  • Assign RBAC role to group.

  • Join users to group ➜ permissions flow automatically.

  • Sync options:

    • Cloud-only identities (≈ 20–30 % of orgs): groups & users created directly in Entra ID.
    • Hybrid identities (≈ 70–80 %):
    • On-prem AD remains authoritative.
    • Azure AD Connect synchronizes users/groups ➜ Entra.
    • Optional: AD domain controllers can be on-prem or run as IaaS VMs in Azure.
  • Benefit: onboarding/offboarding stays inside familiar on-prem process; permissions appear in cloud automatically.


Chapter 4 – Governance & Subscription Design Fundamentals

  • Hierarchy:

    1. Management Groups – logical top-level containers (e.g., Production, Non-Prod, Sandbox).
    2. Subscriptions – billing & quota isolation.
    3. Resource Groups – life-cycle boundary for related resources.
  • Governance artefacts:

    • Naming standards (VM, NIC, RG prefixes).
    • Tags for cost, owner, environment.
    • Azure Policy for compliance (e.g., allowed regions, disallowed SKUs).
    • RBAC inheritance at appropriate scope.

Chapter 4 – Infrastructure Deployment & Automation Roadmap

  • Manual proof-of-concept ➜ realize need for automation.

  • Toolchain instructor will teach:

    1. Terraform (Infrastructure as Code) – create VNet, VMs, NSGs, RBAC, etc.
    2. Ansible – OS-level post-build tasks: patching, agent installs, service configs.
    3. Azure DevOps Pipelines – orchestrate Terraform + Ansible; CI/CD for infra.
    4. PowerShell – ad-hoc scripting; collect VM inventory, remote commands, workflow glue.
  • Full life-cycle targeted: plan ➜ code ➜ deploy ➜ configure ➜ monitor.


Chapter 5 – Identity Sync Resiliency Scenario

  • Student Q&A: “What if on-prem AD goes down?”
    • Password Hash Sync keeps credential hashes in Entra ID.
    • Even if AD offline, cloud auth still works; demonstrated later in lab (power off AD VM + test access).

Chapter 6 – Course Logistics

  • First two days on Zoom; afterwards sessions move to Microsoft Teams.
  • Each learner receives individual Teams credentials.
  • Daily sessions: 1–1.5 hours; shorter initially so students can digest new terms.
  • Recordings:
    • Uploaded to Google Drive (Day 1 & 2) then SharePoint for paid participants.
  • If Zoom meeting auto-ends (40-minute limit), re-join with same link.

Chapter 6 – Tools Confirmed for Syllabus

  • Terraform – basic to advanced modules.
  • Azure PowerShell – automate daily tasks, VM inventory, remote ops.
  • Ansible – configuration management & post-build automation.

Chapter 7 – Closing & Next Steps

  • Instructor will spin up on-prem AD (either local lab or Azure VMs) and grant students delegated access.
  • Emphasis on repetition: watch recordings multiple times to master terminology.
  • Encourages students to bring questions; interactive style.
  • Reminder: see you tomorrow via same link; expect incremental deep-dives into Entra ID, RBAC, Terraform, etc.