Contents

Every journey, page and step. Pick a step to open the animation right at that moment — no need to start from the beginning.

Lab guides

Microsoft 365 Copilot

Open journey →11 pages
Hand off the work with Copilot Cowork10 stepsOpen
  1. 1Alex's week isn't one task
  2. 2Conversation, specialist or assignment?
  3. 3Open Cowork
  4. 4Write a request that works
  5. 5Cowork plans and works
  6. 6It asks when it needs you
  7. 7Nothing sends without you
  8. 8Review the results
  9. 9What did that cost?
  10. 10All in one: hand off the work
Meet Microsoft 365 Copilot11 stepsOpen
  1. 1Adding AI on top of Microsoft 365
  2. 2Copilot Chat — open to everyone
  3. 3How do I know I have the licence?
  4. 4Work IQ on or off — where the answer comes from
  5. 5It respects what you can already see
  6. 6Asking for it properly
  7. 7Choosing how Copilot thinks
  8. 8From chat to agents
  9. 9Researcher and Analyst at work
  10. 10Keep the work — Pages and export
  11. 11Microsoft 365 Copilot — All in One
Microsoft 365 Copilot in Excel7 stepsOpen
  1. 1Thousands of rows, not one conclusion
  2. 2Ask it the way you’d ask a colleague
  3. 3Turn twelve months into one picture
  4. 4The spike nobody had noticed
  5. 5Where the line is heading
  6. 6The four lines the executives actually read
  7. 7From a spreadsheet nobody read to a recommendation leadership can act on
Microsoft 365 Copilot in Outlook6 stepsOpen
  1. 1Three hundred unread, a week of the project inside
  2. 2Fifty messages, one decision
  3. 3Alex jots it, Copilot writes it
  4. 4Same message, different room
  5. 5Walking in already briefed
  6. 6From 300 unread to four answers and a plan
Microsoft 365 Copilot in PowerPoint8 stepsOpen
  1. 1The proposal is approved — now they want the deck
  2. 2Point Copilot at the file — and at the template
  3. 3Put it on the company template
  4. 4Ask for a slide that isn’t there yet
  5. 5Say less, land more
  6. 6Make the point visible
  7. 7Ask the deck before the room does
  8. 8From an approved document to a deck the committee will read
Microsoft 365 Copilot in Teams6 stepsOpen
  1. 1Twenty-three minutes late to your own project
  2. 2The meeting, written down while it happened
  3. 3Five actions left the room. Two of them are yours
  4. 4Approved: a four-week pilot, and the budget to run it
  5. 5A meeting you can ask questions
  6. 6From twenty-three minutes late to owning the pilot
Microsoft 365 Copilot in Word10 stepsOpen
  1. 1A blank page and a deadline
  2. 2Copilot lives inside Word
  3. 3Chat Only, or Allow Editing
  4. 4Ground the draft in your own files
  5. 5Rewrite it for the audience
  6. 6Turn one line into a section
  7. 7Read a 50-page document in seconds
  8. 8Ask the document questions
  9. 9A second pair of eyes
  10. 10From a blank page to an executive proposal
Microsoft Copilot — Free Personal AI (copilot.microsoft.com)4 stepsOpen
  1. 1Meet the free, personal Copilot
  2. 2Ask anything — web answers
  3. 3Response styles & Temporary chats
  4. 4Free Personal Copilot — All in One
One Copilot Across Microsoft 3657 stepsOpen
  1. 1It was the same Copilot the whole time
  2. 2Yesterday's conversation is still there
  3. 3Pick the conversation up wherever you already are
  4. 4Yesterday's proposal becomes today's deck
  5. 5A good answer should not scroll away
  6. 6Chat or Cowork
  7. 7One assistant. One week. One body of work
Why Microsoft 365 Copilot7 stepsOpen
  1. 1Writing used to begin with a blank page
  2. 2The deck came out of the document Alex had already written
  3. 3Alex asked the spreadsheet a question
  4. 4Three hundred unread, and a decision buried in them
  5. 5The meeting was worked once, not twice
  6. 6Delegated work
  7. 7This is the difference Copilot actually makes
Your First Day with Microsoft 3658 stepsOpen
  1. 1Your first day at Contoso
  2. 2Subscription, licence, account
  3. 3Signing in to the company tenant
  4. 4A day of work — and the data it creates
  5. 5Where does everything go?
  6. 6How the company protects it
  7. 7Desktop apps or just a browser
  8. 8Now meet Microsoft 365 Copilot

Copilot Studio

Open journey →4 pages
Copilot Studio — Copilot Studio in Action (Use Cases)7 stepsOpen
  1. 1Where Agents Pay Off
  2. 2Customer Support
  3. 3Employee Help Desk
  4. 4Sales & Store Info
  5. 5Extend Microsoft 365 Copilot
  6. 6Autonomous Back-Office
  7. 7Recap
Copilot Studio — Extend & Integrate7 stepsOpen
  1. 1Why Extend
  2. 2Connectors
  3. 3Custom Connectors
  4. 4MCP
  5. 5Agent Flows + Azure
  6. 6Autonomous & Multi-Agent
  7. 7Recap
Copilot Studio — What Makes an Agent8 stepsOpen
  1. 1Overview
  2. 2Knowledge
  3. 3Tools
  4. 4Agents
  5. 5Topics
  6. 6Measure
  7. 7Channels
  8. 8Recap
Copilot Studio — Why Copilot Studio (Foundations)7 stepsOpen
  1. 1The Problem
  2. 2What Copilot Studio Is
  3. 3What an Agent Is
  4. 4Who & Why
  5. 5Licensing & Pricing
  6. 6Build in Minutes
  7. 7Recap

AI Agents · Microsoft Foundry

Open journey →10 pages
Choosing Your AI SDK9 stepsOpen
  1. 1Three SDKs, One Application
  2. 2One Resource, Two Endpoints
  3. 3Azure OpenAI SDK
  4. 4Foundry SDK
  5. 5Microsoft Agent Framework
  6. 6How They Fit Together
  7. 7In a Real Application
  8. 8So Which One Do I Use?
  9. 9Pick Your Layer
Get Started with Azure AI Speech — Microsoft Foundry11 stepsOpen
  1. 1Why Give Software a Voice?
  2. 2Two Core Capabilities
  3. 3How Speech to Text Works
  4. 4Speech to Text in the Real World
  5. 5How Text to Speech Works
  6. 6The TTS API
  7. 7Speech-Capable Agents
  8. 8Speech-to-Speech Scenarios
  9. 9Voice Live
  10. 10How It Fits Together
  11. 11Get Started
Get Started with Computer Vision — Microsoft Foundry8 stepsOpen
  1. 1What Is Computer Vision?
  2. 2In the Real World
  3. 3What Vision Models Can Do
  4. 4Multimodal GPT
  5. 5The Foundry Catalog
  6. 6The Responses API
  7. 7Generating Images & Video
  8. 8Build a Vision App
Get Started with Content Understanding — Microsoft Foundry8 stepsOpen
  1. 1Why AI-Powered Extraction?
  2. 2In the Real World
  3. 3How It Works
  4. 4Define a Schema
  5. 5Analyzers Apply Your Schema
  6. 6Try It in the Portal
  7. 7Audio & Video
  8. 8Build with the API & SDK
Get Started with Text Analysis — Microsoft Foundry11 stepsOpen
  1. 1The Problem
  2. 2One Service, Many Capabilities
  3. 3Language Detection
  4. 4Key Phrases
  5. 5Entity Linking
  6. 6Sentiment
  7. 7PII Detection
  8. 8Summarization
  9. 9In the Real World
  10. 10Skills via MCP
  11. 11Get Started
Microsoft AI Foundry — Hub & Project Model7 stepsOpen
  1. 1Overview
  2. 2AI Hub
  3. 3Shared Resources
  4. 4Centralized Config
  5. 5Projects
  6. 6The Big Picture
  7. 7The New Foundry
Microsoft Foundry — New Experience5 stepsOpen
  1. 1The New Foundry Experience
  2. 2Resources
  3. 3Models
  4. 4Features
  5. 5Summary
Model Deployment vs Agent — Microsoft Foundry6 stepsOpen
  1. 1Why an Agent?
  2. 2Deployment
  3. 3Tokens
  4. 4Inference
  5. 5Chat Flow
  6. 6AI Agents
The Six Pillars of Responsible AI8 stepsOpen
  1. 1Six Pillars, One Question
  2. 2Fairness
  3. 3Reliability and Safety
  4. 4Privacy and Security
  5. 5Inclusiveness
  6. 6Transparency
  7. 7Accountability
  8. 8The Six Pillars Together
What Makes an Agent — Microsoft Foundry7 stepsOpen
  1. 1The Problem
  2. 2What Is an Agent?
  3. 3Instructions
  4. 4Knowledge
  5. 5Tools
  6. 6Memory
  7. 7Build It

AI-500 · Multi-agent AI solutions

Open journey →4 pages
AI-500 Course Introduction9 stepsOpen
  1. 1Hook
  2. 2Question
  3. 3AI-500
  4. 4Four verbs
  5. 5Ladder
  6. 6Who
  7. 7Approach
  8. 8Depth
  9. 9Recap
AI-500 Trainer Briefing7 stepsOpen
  1. 1Positioning
  2. 2Days
  3. 3Scope
  4. 4Mix-ups
  5. 5Delivery
  6. 6Check first
  7. 7FAQ
AI-500: The Course, the Exam, and How to Prepare6 stepsOpen
  1. 1The week
  2. 2Day to domain
  3. 3Exam facts
  4. 4Exam feel
  5. 5Prepare
  6. 6All in one
AI-500: The Four Domains8 stepsOpen
  1. 1Blueprint
  2. 2Decompose
  3. 3Remember
  4. 4Orchestrate
  5. 5Connect
  6. 6Prove
  7. 7Ship
  8. 8All in one

Databases for AI apps and architects

Open journey →11 pages
Contoso Ships the Assistant7 stepsOpen
  1. 1One question, two kinds of answer
  2. 2Cosmos DB remembers the conversation
  3. 3Find the tent by meaning
  4. 4Look up the order with a tool
  5. 5Fast and affordable on both engines
  6. 6Optional: zoom out to the architect view
  7. 7Contoso ships the assistant
Cosmos DB: Build and Query8 stepsOpen
  1. 1Why a document database?
  2. 2Account, database, container, item
  3. 3Partition key: where items live
  4. 4Connect with the SDK
  5. 5Create, read, replace, upsert, delete
  6. 6Point read or query?
  7. 7Query: filter and project
  8. 8All in one: build and query
Cosmos DB: Optimize Performance8 stepsOpen
  1. 1Measure before you tune
  2. 2The indexing policy decides what is indexed
  3. 3Composite index for filter + sort
  4. 4Pick a vector index by dataset size
  5. 5Every index trades read speed for write cost
  6. 6Consistency is a latency and RU dial
  7. 7Contoso tunes the product container
  8. 8Optimizing Cosmos DB, all in one
Cosmos DB: Vector Search8 stepsOpen
  1. 1Search by meaning, not keywords
  2. 2Tell the container about its vectors
  3. 3Keep the embedding on the item
  4. 4Rank items by similarity
  5. 5Narrow, rank, then match words
  6. 6Keep embeddings fresh
  7. 7One semantic search pipeline
  8. 8Vector search in Cosmos DB, all in one
Databases for AI Apps: Journey Intro7 stepsOpen
  1. 1One database for every job?
  2. 2Specialist stores, one assistant
  3. 3The journey in one card
  4. 4Your route through the journey
  5. 5Same arc, two engines
  6. 6Two tracks, one data foundation
  7. 7All in one: your database journey
Design Data Integration and Data Lake9 stepsOpen
  1. 1Contoso’s data journey
  2. 2Azure Data Factory: the orchestrator
  3. 3Azure Data Lake Storage: raw data at scale
  4. 4Azure Databricks: Spark for big data
  5. 5Azure Synapse Analytics: one analytics service
  6. 6Hot, warm and cold data paths
  7. 7Azure Stream Analytics: insight from streams
  8. 8Which service for which job?
  9. 9All in One: Contoso’s data journey
Design Relational Data Storage9 stepsOpen
  1. 1Three ways to run SQL on Azure
  2. 2Azure SQL Database
  3. 3Azure SQL Managed Instance
  4. 4SQL Server on Azure VMs
  5. 5Recommend a scaling approach
  6. 6Recommend an availability tier
  7. 7Protect data in every state
  8. 8When relational is not the answer
  9. 9All in one: pick the right store
Pick Your Database for AI Apps6 stepsOpen
  1. 1One assistant, four kinds of data
  2. 2Documents and vectors: Cosmos DB
  3. 3Tables plus vectors: PostgreSQL
  4. 4Relational at scale: Azure SQL family
  5. 5Raw files and pipelines: the data lake
  6. 6Which one, when?
PostgreSQL: Build and Query8 stepsOpen
  1. 1Why PostgreSQL behind the assistant?
  2. 2A managed PostgreSQL, compute apart from storage
  3. 3Connect with a token, not a password
  4. 4Model orders and products as tables
  5. 5Page through orders the efficient way
  6. 6Call it from Python with psycopg
  7. 7The exercise: an agent tool backend
  8. 8PostgreSQL: build and query, all in one
PostgreSQL: Optimize Vector Search8 stepsOpen
  1. 1Where a vector query spends its time
  2. 2Tune PostgreSQL for pgvector
  3. 3Choose and configure the vector index
  4. 4Shape the table for vectors and filters
  5. 5Scale for high-volume workloads
  6. 6Pool connections and manage sessions
  7. 7Contoso’s product search, tuned
  8. 8All in One: Optimize vector search
PostgreSQL: Vector Search with pgvector8 stepsOpen
  1. 1Meaning search, plus relational joins
  2. 2Enable pgvector, add a vector column
  3. 3Three metrics, three operators
  4. 4Fast search: IVFFlat or HNSW
  5. 5Keep embeddings and the index fresh
  6. 6Semantic retrieval with a filter
  7. 7RAG: PostgreSQL is the retriever
  8. 8All in one: vector search in PostgreSQL

Azure Fundamentals

Open journey →12 pages
Cloud Concepts8 stepsOpen
  1. 1Busy days and quiet days
  2. 2What happens on quiet days?
  3. 3Pay for what you use
  4. 4Match the commitment to the workload
  5. 5Public, private, or hybrid
  6. 6Grow and shrink with demand
  7. 7Why organizations move
  8. 8Cloud Concepts - All in One
Cloud Service Models7 stepsOpen
  1. 1Who patches the server?
  2. 2Run it yourself
  3. 3Rent the infrastructure
  4. 4Use a managed platform
  5. 5Subscribe to finished software
  6. 6Some work stays with Contoso
  7. 7Cloud Service Models - All in One
Organize Your Resources7 stepsOpen
  1. 1Which resources belong together?
  2. 2Start with a resource
  3. 3Location is not ownership
  4. 4Group what shares a lifecycle
  5. 5One subscription holds the groups
  6. 6Management groups organize subscriptions
  7. 7Resource Hierarchy - All in One
Regions and Availability Zones9 stepsOpen
  1. 1Where should the shop run?
  2. 2Choose a region
  3. 3Look inside the region
  4. 4Separate the infrastructure
  5. 5One location is not redundancy
  6. 6What if a zone fails?
  7. 7The regional boundary matters
  8. 8Check the geography before committing
  9. 9Regions and Zones - All in One
Azure Compute Options8 stepsOpen
  1. 1How much do you want to manage?
  2. 2Take the whole machine
  3. 3Prepare the VM workload
  4. 4Package the app instead
  5. 5Let the platform run it
  6. 6React to an order
  7. 7Deliver desktops, not servers
  8. 8Compute Options - All in One
Azure Networking Basics9 stepsOpen
  1. 1An order needs the stock count
  2. 2Give the backend a private address
  3. 3Organize the address space
  4. 4Find inventory by name
  5. 5Connect privately to the database
  6. 6Reach the fulfilment network
  7. 7Keep the warehouse connected
  8. 8Consider a private circuit
  9. 9The order can reach inventory
Azure Storage Basics9 stepsOpen
  1. 1Where should the data live?
  2. 2Start with a storage account
  3. 3Pick the service per kind of data
  4. 4Separate work from records
  5. 5Plan the move
  6. 6Move and synchronize files
  7. 7Match the tier to how often you read
  8. 8Decide how many copies to keep
  9. 9Storage Basics - All in One
Identity and Security Basics9 stepsOpen
  1. 1Who are you, and what may you do?
  2. 2The directory holds the identities
  3. 3Prove who is asking
  4. 4Check the sign-in conditions
  5. 5Then allow the action
  6. 6Same person, different actions
  7. 7Assume nothing is safe by default
  8. 8Keep checking the security posture
  9. 9Identity and Security - All in One
Cost Management and Tags8 stepsOpen
  1. 1Where did the money go?
  2. 2What actually drives cost
  3. 3Estimate before you deploy
  4. 4Organize what you deploy
  5. 5Watch the real spending
  6. 6An alert is not a stop switch
  7. 7Find the cause, then act
  8. 8Cost and Tags - All in One
Governance and Compliance8 stepsOpen
  1. 1Standards nobody checks
  2. 2Write the rule, then apply it
  3. 3First, observe with Audit
  4. 4Then enforce with Deny
  5. 5Protect what already exists
  6. 6The resource is not its data
  7. 7Govern the data too
  8. 8Governance - All in One
Manage and Deploy Azure8 stepsOpen
  1. 1Built by hand, twice
  2. 2Start in the portal
  3. 3Repeat it with commands
  4. 4Describe it as code
  5. 5Same definition, intentional differences
  6. 6The management request path
  7. 7Reach beyond Azure
  8. 8Manage and Deploy - All in One
Monitoring Tools9 stepsOpen
  1. 1Was it broken, or was it us?
  2. 2Collect the evidence
  3. 3Look inside the checkout request
  4. 4Store it where you can query it
  5. 5Follow the evidence
  6. 6Decide what is worth a phone call
  7. 7Improve before the next promotion
  8. 8Is Azure reporting an issue?
  9. 9Monitoring - All in One

Identity and governance

Open journey →7 pages
Your tenant is a house8 stepsOpen
  1. 1One key opens everything
  2. 2The house is your tenant
  3. 3Every house needs an address
  4. 4Who lives here
  5. 5House rules run the house
  6. 6Appliance keys are a second keyring
  7. 7The whole house — All in One
  8. 8The same house, in the Azure portal
Who lives here7 stepsOpen
  1. 1The family lives here. The register doesn’t know them.
  2. 2Give Noah his own record
  3. 3One group for the children
  4. 4Write his name, or write a rule
  5. 5Check who is really on the list
  6. 6Everybody has a key — to the house
  7. 7The register, in Microsoft Entra ID
The guest room7 stepsOpen
  1. 1The neighbour who needs to help
  2. 2Invite Alex over
  3. 3Alex accepts, using their own key
  4. 4One person, two house registers
  5. 5Access exactly one appliance
  6. 6A guest, not a resident
  7. 7The guest, in Microsoft Entra ID
The front door7 stepsOpen
  1. 1Unlocking the same door twice
  2. 2Reuse an eligible session
  3. 3Not every key is equally convincing
  4. 4A doorbell that decides how hard to check
  5. 5Getting in is not the same as being allowed
  6. 6Session, proof, policy, permission
  7. 7The front door, in Microsoft Entra ID
Running the house7 stepsOpen
  1. 1Three favours, three different jobs
  2. 2Hand over one chore, not the house
  3. 3A seat at the table has to exist
  4. 4Register the spare key before you need it
  5. 5Prove it is you, then cut a new key
  6. 6Help out without holding every key
  7. 7Running the house, in Microsoft Entra ID
Which room pays for this?7 stepsOpen
  1. 1One bill for the whole house
  2. 2Give each part of the house its own account
  3. 3A room for things that belong together
  4. 4Above every account sits the family
  5. 5What the family decides reaches every room
  6. 6Four levels — All in One
  7. 7The Contoso estate, end to end
The house rules on money8 stepsOpen
  1. 1Nobody said no
  2. 2Write the rule, then choose where it lands
  3. 3Stopped, or just written down?
  4. 4One rule is not a standard
  5. 5Label the receipt, then monitor spending
  6. 6Protect an existing resource
  7. 7Keyrings, rules, locks — All in One
  8. 8How it really looks in Azure

Azure Virtual Machines

Open journey →9 pages
Build Your First VM8 stepsOpen
  1. 1The shop needs OS control
  2. 2Start with an image
  3. 3Choose a size
  4. 4Give data a durable home
  5. 5Connect the private network
  6. 6Connect, then authenticate
  7. 7Stopped is not deallocated
  8. 8Your VM - All in One
Availability Sets7 stepsOpen
  1. 1One host, one point of failure
  2. 2Prepare another application instance
  3. 3Separate fault domains
  4. 4Separate update domains
  5. 5A hardware failure unfolds
  6. 6Know the boundary
  7. 7Availability Sets - All in One
VMs Across Availability Zones7 stepsOpen
  1. 1What if a whole zone fails?
  2. 2Place one VM in a zone
  3. 3Prepare VMs across zones
  4. 4Configure resilient routing
  5. 5Do not forget the data
  6. 6A zone goes unavailable
  7. 7Zonal VMs - All in One
Virtual Machine Scale Sets8 stepsOpen
  1. 1Demand changes
  2. 2Manage a group of VMs
  3. 3Choose an orchestration mode
  4. 4Configure a bounded scaling policy
  5. 5Combine scaling with zone placement
  6. 6Separate routing health from repair
  7. 7Scale in with the application in mind
  8. 8VM Scale Sets - All in One
Back It Up, Prove the Restore7 stepsOpen
  1. 1Someone deletes the orders folder
  2. 2Create the vault
  3. 3Write the policy
  4. 4One run, two phases
  5. 5Restore only what you need
  6. 6Deleting a backup is a separate risk
  7. 7VM Backup - All in One
Disks That Hold the Data7 stepsOpen
  1. 1The catalogue outgrows its disk
  2. 2Three disks, three jobs
  3. 3Match the disk to the work
  4. 4Grow it, never shrink it
  5. 5Freeze a point in time
  6. 6Encrypt at the host
  7. 7VM Disks - All in One
Move It Without Breaking It6 stepsOpen
  1. 1It landed in the wrong place
  2. 2Move between resource groups
  3. 3Move between subscriptions
  4. 4Changing region is a rebuild
  5. 5Check before you commit
  6. 6Moving - All in One
Right-Size the Machine6 stepsOpen
  1. 1The invoice arrives
  2. 2Pick the family first
  3. 3The size sets the ceiling
  4. 4Resizing restarts the machine
  5. 5Quota limits what you can deploy
  6. 6Right-Sizing - All in One
Watch It and Keep It Patched7 stepsOpen
  1. 1Checkout feels slow
  2. 2Host signals need no agent
  3. 3Inside the guest needs an agent
  4. 4Compare guest performance
  5. 5Turn a threshold into action
  6. 6Patch on a schedule
  7. 7Monitoring - All in One

Azure PaaS Compute

Open journey →4 pages
App Service · Your Web App, Fully Managed8 stepsOpen
  1. 1intro
  2. 2deploy
  3. 3slotsIntro
  4. 4slots
  5. 5auth
  6. 6security
  7. 7traffic
  8. 8recap
App Service Networking · Inbound & Outbound6 stepsOpen
  1. 1intro
  2. 2inbound
  3. 3privateendpoint
  4. 4outbound
  5. 5nat
  6. 6recap
App Service Plan · The Engine Room7 stepsOpen
  1. 1intro
  2. 2tier
  3. 3instances
  4. 4platform
  5. 5scale
  6. 6autoscale
  7. 7recap
Function App · Serverless & Event-Driven6 stepsOpen
  1. 1intro
  2. 2triggers
  3. 3scaling
  4. 4plans
  5. 5compare
  6. 6recap

Azure Containers

Open journey →6 pages
Azure Container Apps — Azure Containers8 stepsOpen
  1. 1problem
  2. 2replica
  3. 3httpscale
  4. 4revision
  5. 5ingress
  6. 6serverless
  7. 7control
  8. 8recap
Azure Container Instances — Azure Containers7 stepsOpen
  1. 1what
  2. 2config
  3. 3pull
  4. 4run
  5. 5reach
  6. 6limit
  7. 7recap
Azure Container Registry — Azure Containers7 stepsOpen
  1. 1dockerhub
  2. 2acr
  3. 3tasks
  4. 4tiers
  5. 5features
  6. 6advanced
  7. 7recap
Azure Kubernetes Service — Azure Containers12 stepsOpen
  1. 1arch
  2. 2nodepools
  3. 3pod
  4. 4scale
  5. 5service
  6. 6svcCip
  7. 7svcNp
  8. 8svcLb
  9. 9ingress
  10. 10why
  11. 11monitor
  12. 12recap
Azure Red Hat OpenShift — Azure Containers12 stepsOpen
  1. 1stack
  2. 2resp
  3. 3arch
  4. 4hcp
  5. 5projects
  6. 6s2i
  7. 7routes
  8. 8operators
  9. 9security
  10. 10day2
  11. 11vsaks
  12. 12recap
Why Docker? — Azure Containers9 stepsOpen
  1. 1problem
  2. 2drift
  3. 3wrap
  4. 4layers
  5. 5vmvc
  6. 6ports
  7. 7oci
  8. 8targets
  9. 9recap

Azure Networking

Open journey →10 pages
Azure Naming Convention — Names that tell you what they are7 stepsOpen
  1. 1Six months later, nobody knows
  2. 2Five parts, always in the same order
  3. 3The abbreviations are already decided
  4. 4What it looks like across the estate
  5. 5Where a name has to be unique
  6. 6What does not belong in the name
  7. 7A name that answers the question
Azure Virtual Network — VNet, Subnets, NICs & NSGs7 stepsOpen
  1. 1Start With a Virtual Network
  2. 2Segment It Into Subnets
  3. 3Place a Virtual Machine
  4. 4The NIC Holds the IPs
  5. 5Filter Traffic With an NSG
  6. 6One NSG for the Whole Subnet
  7. 7The Whole Picture
Azure Virtual WAN9 stepsOpen
  1. 1The hub you built by hand
  2. 2Azure Virtual WAN
  3. 3What may live in the hub
  4. 4One network, two regions, every branch
  5. 5Four paths you get for nothing
  6. 6Secured virtual hub
  7. 7Basic buys almost nothing
  8. 8Managed hub, or one you own
  9. 9The same shape, someone else's problem
Choosing a load balancer13 stepsOpen
  1. 1One name, many servers
  2. 2Two questions decide it
  3. 3Four services, four quadrants
  4. 4Azure Load Balancer
  5. 5Contoso, balanced at Layer 4
  6. 6Application Gateway
  7. 7One hostname, three back-end pools
  8. 8Traffic Manager
  9. 9One global profile, many regions
  10. 10Azure Front Door
  11. 11One edge in front of the whole world
  12. 12They stack, they do not compete
  13. 13Scope first, then protocol
Monitoring the network — Network Watcher and Azure Monitor9 stepsOpen
  1. 1"It cannot connect"
  2. 2Network Watcher
  3. 3Three tools, in this order
  4. 4Virtual network flow logs
  5. 5Traffic Analytics
  6. 6Connection Monitor
  7. 7Azure Monitor Network Insights
  8. 8Which one answers your question
  9. 9Diagnose now, or watch always
NSG & ASG — filter by name, not by address11 stepsOpen
  1. 1A network security group is a rule list
  2. 2Anatomy of one rule
  3. 3The rules you never wrote
  4. 4Subnet, NIC — or the order they run in
  5. 5The app tier keeps spreading
  6. 6An application security group is a label
  7. 7One network, two subnets
  8. 8Name the machines, attach the filter
  9. 9The rule, written in names
  10. 10A new subnet costs nothing
  11. 11Filter by intent, not by address
Public DNS, Private DNS and Private Link9 stepsOpen
  1. 1A name, and who is allowed to use it
  2. 2Azure DNS public zones
  3. 3Azure Private DNS zones
  4. 4Private endpoint
  5. 5What the lookup actually does
  6. 6The link is the whole mechanism
  7. 7Same shape, opposite purpose
  8. 8It still resolves to a public IP
  9. 9Publish, resolve, or reach
VNet Peering & Azure Bastion — Private reach, no public IPs9 stepsOpen
  1. 1Two problems, one afternoon
  2. 2Peering joins two networks privately
  3. 3What peering asks of you
  4. 4Peering is not transitive
  5. 5Now, how do you get in?
  6. 6Azure Bastion is the managed front door
  7. 7Four SKUs, four different answers
  8. 8One bastion, every peered network
  9. 9Private reach, and a door you did not build
VPN Gateway and ExpressRoute9 stepsOpen
  1. 1Two networks that cannot talk
  2. 2Site-to-site VPN
  3. 3Point-to-site VPN
  4. 4ExpressRoute
  5. 5Three edges make the circuit
  6. 6One circuit, two peerings
  7. 7Five questions settle it
  8. 8Run both, on purpose
  9. 9Encrypt the internet, or avoid it
Web Application Firewall and Azure Firewall10 stepsOpen
  1. 1Two firewalls, two different jobs
  2. 2Web Application Firewall
  3. 3Detection logs. Prevention blocks.
  4. 4Azure Firewall
  5. 5Nothing reaches the firewall by accident
  6. 6Three rule collections, one order
  7. 7The distinction, in one table
  8. 8In a hub, they sit in series
  9. 9The mistakes that cost you
  10. 10One reads requests, one reads traffic

Azure Storage

Open journey →9 pages
Azure Storage Account — Tiers, Services & Types6 stepsOpen
  1. 1Overview
  2. 2Standard vs Premium
  3. 3Four Data Services
  4. 4Three Kinds of Blob
  5. 5Access Tiers
  6. 6Recap
Azure Storage Data Protection & Encryption8 stepsOpen
  1. 1goal
  2. 2encrypt
  3. 3softdelete
  4. 4versioning
  5. 5immutable
  6. 6restore
  7. 7recap
  8. 8spec
Azure Storage Identity & RBAC8 stepsOpen
  1. 1goal
  2. 2identity
  3. 3token
  4. 4role
  5. 5scope
  6. 6assign
  7. 7recap
  8. 8spec
Azure Storage Network Security & Private Link8 stepsOpen
  1. 1goal
  2. 2firewall
  3. 3pe
  4. 4dns
  5. 5lockdown
  6. 6connect
  7. 7recap
  8. 8spec
Azure Storage Redundancy — LRS · ZRS · GRS · GZRS6 stepsOpen
  1. 1Overview
  2. 2LRS
  3. 3ZRS
  4. 4GRS and RA-GRS
  5. 5GZRS and RA-GZRS
  6. 6Summary
Azure Storage SAS Tokens & Stored Access Policy8 stepsOpen
  1. 1The Players
  2. 2The Keys
  3. 3Generate a Token
  4. 4Inside the Token
  5. 5The User Gets In
  6. 6Stored Access Policy
  7. 7The Whole Picture
  8. 8SAS Types & Scope
Build Apps on Azure Storage8 stepsOpen
  1. 1goal
  2. 2connect
  3. 3io
  4. 4azurite
  5. 5events
  6. 6feed
  7. 7recap
  8. 8spec
Move & Optimize Azure Storage8 stepsOpen
  1. 1goal
  2. 2tiers
  3. 3lifecycle
  4. 4replication
  5. 5azcopy
  6. 6inventory
  7. 7recap
  8. 8spec
Storage for AI8 stepsOpen
  1. 1goal
  2. 2store
  3. 3index
  4. 4vectorize
  5. 5retrieve
  6. 6secure
  7. 7recap
  8. 8spec

Azure Security

Open journey →5 pages
Azure App Configuration — Azure Security Journey7 stepsOpen
  1. 1Every service must find the others
  2. 2One store for every setting: App Configuration
  3. 3Scattered settings become organized key-values
  4. 4One key, many labels — versions & environments
  5. 5Flags and secret references, by content type
  6. 6Consume live: managed identity + dynamic refresh
  7. 7All in one: central, versioned, live configuration
Azure Key Vault — deep dive · Azure Security Journey7 stepsOpen
  1. 1Every connection needs a secret, key or certificate
  2. 2Static secrets in appsettings.json
  3. 3Centralize in Azure Key Vault
  4. 4How your material is protected
  5. 5Standard vs Premium vs Managed HSM
  6. 6Migrate a key into Key Vault — without exposing it
  7. 7Azure Key Vault — the whole picture
Managed Identity — Azure Security Journey7 stepsOpen
  1. 1Where we start: an app that needs a database
  2. 2That login ships inside the app — in plain text
  3. 3Managed identity solves it — a role, not a password
  4. 4Turn it on — enable the managed identity
  5. 5The catch — one identity per resource
  6. 6One identity, shared — user-assigned
  7. 7Recap — System-assigned vs User-assigned
Service Principal & Federated Credentials — Azure Security Journey7 stepsOpen
  1. 1Ship Contoso from GitHub to Azure
  2. 2GitHub and Azure are two different platforms
  3. 3Trust starts with an identity
  4. 4App Registration defines the identity
  5. 5GitHub signs in as the Service Principal
  6. 6Where federation shines
  7. 7From GitHub to Azure — secretless, end to end
Zero Trust Security Architecture — Azure Security Journey6 stepsOpen
  1. 1Start from the assembled Contoso design
  2. 2Add Private Endpoint to the sensitive services
  3. 3Disable the public path too
  4. 4Separate duties with Azure RBAC
  5. 5Assume breach operationally
  6. 6The hardened Contoso design — end to end

Azure Integration & Messaging

Open journey →5 pages
Episode 1 · The Black Friday Bottleneck6 stepsOpen
  1. 1Black Friday breaks the checkout
  2. 299% of a checkout is spent waiting
  3. 3Maya cuts the wire
  4. 4Meet the Azure Storage queue
  5. 5The same night, buffered
  6. 6Episode 1: buffer the work, keep the sale
Episode 2 · The VIP Transaction Disaster6 stepsOpen
  1. 1The cancellation beat the order
  2. 2What a simple queue does not give you
  3. 3Sessions put the VIP back in order
  4. 4Peek-lock, and a cell for bad messages
  5. 5One order, three teams, zero coupling
  6. 6Episode 2: Service Bus is the safe lane
Episode 3 · The Sensor Tsunami6 stepsOpen
  1. 1The telemetry flood drowns the queue
  2. 2Stop delivering. Start recording.
  3. 3Partitions turn one pipe into parallel lanes
  4. 4Offsets and consumer groups: read it twice
  5. 5Capture archives the stream without consumer code
  6. 6Episode 3: Event Hubs is the firehose
Episode 4 · The Reactive Smart Store7 stepsOpen
  1. 1Nobody is streaming. Everyone is knocking.
  2. 2Let the event announce itself
  3. 3A tiny envelope, and rules about who opens it
  4. 4At least once, and a schedule to prove it
  5. 5When the handler cannot be reached, pull instead
  6. 6Four services, one question each
  7. 7Episode 4: Event Grid is the nervous system
Episode 5 · The Serverless Glue7 stepsOpen
  1. 1Four brokers, and a thousand lines of plumbing
  2. 2Exactly one trigger. Any number of bindings.
  3. 3A trigger for every service in the series
  4. 4Stop shipping secrets to production
  5. 5The backlog drives the instance count
  6. 6At least once means expect it twice
  7. 7Episode 5: Functions are the wiring

AZ-305 · Design Azure infrastructure solutions

Open journey →10 pages
Design governance: structure, policy and compliance8 stepsOpen
  1. 1One subscription, no structure
  2. 2Management groups: rules that flow down
  3. 3Subscriptions: billing, limits and isolation
  4. 4Resource groups: one shared lifecycle
  5. 5Tags: decide what, then let policy apply them
  6. 6Azure Policy: pick the effect for each rule
  7. 7Compliance: who answers which question
  8. 8All in one: Contoso’s landing zone
Design hybrid identity and on-premises access8 stepsOpen
  1. 1Two directories, one workforce
  2. 2Sync: Cloud Sync or Connect Sync?
  3. 3Sign-in: who checks the password?
  4. 4Single sign-on: no repeat prompts
  5. 5Legacy apps: managed domain or your own DCs?
  6. 6On-premises apps: reach them without a VPN
  7. 7Conditional Access: one policy layer
  8. 8All in one: Contoso’s hybrid identity
Design access: roles, PIM and access reviews9 stepsOpen
  1. 1Contoso: who has access to what?
  2. 2Azure roles vs Microsoft Entra roles
  3. 3Workloads: use a managed identity
  4. 4Secrets, keys and certificates
  5. 5Privileged access: eligible, not always on
  6. 6Access reviews: does anyone still need this?
  7. 7Entitlement management: access packages
  8. 8Lifecycle workflows: joiner, mover, leaver
  9. 9All in one: which tool answers which question
Design logging and monitoring9 stepsOpen
  1. 1An outage, and logs in five places
  2. 2Azure Monitor: metrics and logs
  3. 3Log Analytics: one workspace or many?
  4. 4Table plans: pay for the query you need
  5. 5Route logs with diagnostic settings
  6. 6Application Insights and VM insights
  7. 7Alerts and action groups
  8. 8Microsoft Sentinel: the SIEM on your workspace
  9. 9All in one: from signal to action
Design for recovery: RTO, RPO and the right tool8 stepsOpen
  1. 1Recovery objectives: RTO, RPO and SLA
  2. 2Tier the workloads by what they cost to lose
  3. 3Azure Backup: restore data from a point in time
  4. 4Azure Site Recovery: fail over the workload
  5. 5Backup or replication?
  6. 6Choose where the second copy lives
  7. 7Protect on-premises servers too
  8. 8All in one: recover to the objective
Keep data available: HA and DR for databases and storage8 stepsOpen
  1. 1Zone redundancy: survive a zone failure
  2. 2Across regions: geo-replication or failover group?
  3. 3Backups: pick the restore for the problem
  4. 4SQL Server on VMs: availability groups
  5. 5Azure Cosmos DB: replicate and choose consistency
  6. 6PostgreSQL flexible server: layers of recovery
  7. 7Storage redundancy: one decision row
  8. 8All in one: pick by RTO and RPO
Pick the right compute8 stepsOpen
  1. 1Control or effort: choose your spot
  2. 2Six questions that decide
  3. 3Virtual machines: when, which size, how many
  4. 4Containers: four services, one choice
  5. 5Serverless: code that runs when something happens
  6. 6Batch: a pool of VMs for the nightly job
  7. 7Five workloads, five services
  8. 8All in one: pick the simplest service that fits
Front the app: APIs, caching and deployment8 stepsOpen
  1. 1API Management: one front door
  2. 2API Management: choose the tier
  3. 3Caching: check the cache first
  4. 4Caching: what belongs in memory
  5. 5Messaging and events: pick by the message
  6. 6Configuration: keep settings out of the code
  7. 7Deployment: ship safely, roll back fast
  8. 8All in one: a fast, safe partner API
Design a migration to Azure9 stepsOpen
  1. 1Plan the move: 120 servers, one method
  2. 2Discover and assess with Azure Migrate
  3. 3Dependencies decide the move groups
  4. 4Pick a strategy for each workload
  5. 5Migrate servers: replicate, test, cut over
  6. 6Migrate the order database
  7. 7Migrate files and images
  8. 8Cut over with a way back
  9. 9All in one: the migration route
Case study: design the Contoso platform8 stepsOpen
  1. 1Read the brief: requirements and constraints
  2. 2Identity and governance: pick the sign-in method
  3. 3Data: match the SQL target to the need
  4. 4Business continuity: meet the RTO and RPO
  5. 5Compute: the least to operate that fits
  6. 6Network: private link, global front door
  7. 7Migration: the lightest route per workload
  8. 8All in one: the Contoso platform

GitHub · Contoso Delivery

Open journey →8 pages
Branch with Intent13 stepsOpen
  1. 1Nobody Pushes Straight to main
  2. 2Three Tiers, Not Two
  3. 3Clone It — and All You Have Is main
  4. 4Cut the Epic Branch, Then the Feature Branch
  5. 5A Commit Is a Set of Changes
  6. 6Write the Issue Number Into the Commit
  7. 7One Number, Three Places
  8. 8Open the Pull Request Into the Epic
  9. 9The Checks Decide, Not the Author
  10. 10When the Epic Is Whole, Promote It
  11. 11Epic 1, From Cut to Merge
  12. 12How It Actually Played Out
  13. 13One Issue, One Branch, One Safe Merge
Build It with Copilot8 stepsOpen
  1. 1Not Autocomplete. A Pair Programmer.
  2. 2What Is Free, and What You Pay For
  3. 3AI Credits: What Actually Costs You
  4. 4Who Picks the Model
  5. 5Copilot in VS Code
  6. 6Ask, Plan, Agent
  7. 7Hand Sub-task 1.2 to the Coding Agent
  8. 8You Get a Draft, Not a Decision
Plan the Work9 stepsOpen
  1. 1One Issue Nobody Can Pick Up
  2. 2Cut It Into Four Epics
  3. 3Split Each Epic Into Sub-Tasks
  4. 4What Goes Inside a Sub-Task
  5. 5Make the Hierarchy Real
  6. 6Say What Blocks What
  7. 7Your Turn: Generate This Backlog
  8. 8Twelve Issues — and No Way to Work Them
  9. 9From One Idea to Work You Can Assign
Set Up Your Repo5 stepsOpen
  1. 1Start With an Empty Repository
  2. 2Who Owns the Repository?
  3. 3Install the GitHub CLI
  4. 4Sign the CLI Into Your Account
  5. 5Your Repository Is Ready
Shift Left10 stepsOpen
  1. 1What You Have, and What Is Missing
  2. 2The Later You Find It, the More It Costs
  3. 3What the Pipeline Does — and Why You Want One
  4. 4The Machine That Actually Runs It
  5. 5What a Pipeline Actually Is
  6. 6Tests That Run Themselves
  7. 7Let GitHub Read the Code for You
  8. 8Keep the Dependencies Honest
  9. 9Where Secrets Are Allowed to Live
  10. 10Every Change Arrives Already Proven
Ship It to Azure7 stepsOpen
  1. 1One Pipeline, Two Halves
  2. 2Build It Once, Ship the Small Half
  3. 3GitHub Is Not Inside Azure
  4. 4Give the Workflow an Identity
  5. 5Deploy Without a Password
  6. 6The Job That Actually Releases It
  7. 7From a Rainy Afternoon to Running Code
Track It on a Board10 stepsOpen
  1. 1An Unorganized List of Issues
  2. 2One Board, Five Columns
  3. 3Status Is a Column, Not a Comment
  4. 4Tell the Board What Kind of Work This Is
  5. 5Put the Work in a Timebox
  6. 6Group the Board by Parent
  7. 7Your Turn: Create the Board
  8. 8Your Turn: Put the Issues on It
  9. 9Your Turn: Split the Board by Epic
  10. 10Now the Team Can See the Work
Why Contoso Is Building This8 stepsOpen
  1. 1When It Rains, Contoso Loses Money
  2. 2The Same Rain, Two Different Days
  3. 3Sell What the Weather Calls For
  4. 4Storm Day Free Shipping
  5. 5Three Channels, Three Sets of Problems
  6. 6One API, One Source of Truth
  7. 7What We Are Actually Building
  8. 8Weather In, Revenue Out

Lab · Build and extend an AI agent

2 pages
Build & extend an AI agent — Azure Animations6 stepsOpen
  1. 1The problem
  2. 2Lab at a glance
  3. 3The blueprint
  4. 4How the pieces fit together
  5. 5Explore each task
  6. 6One assistant, six tasks
Build & extend an AI agent — Lab overview0 stepsOpen

Lab · Explore Microsoft 365 Copilot

1 pages
Explore Microsoft Copilot — Azure Animations6 stepsOpen
  1. 1You have an idea, not a business
  2. 2Five tasks, one business
  3. 3What you walk away with
  4. 4Where all of this happens
  5. 5Explore each task
  6. 6From one document to a funded pitch

Lab · PL-7008 Copilot Studio

1 pages
PL-7008 Copilot Studio labs — Azure Animations6 stepsOpen
  1. 1Describing an agent is easy
  2. 2Five labs, four hours
  3. 3One agent, five moving parts
  4. 4Where the pieces live
  5. 5Explore the labs
  6. 6What you can do at the end

Lab · MS-4018 Draft, analyze and present

1 pages
Draft, analyze and present with Microsoft 365 Copilot — Azure Animations5 stepsOpen
  1. 1Five jobs, five blank pages
  2. 2Setup once, then five labs
  3. 3What you walk away with
  4. 4Explore each lab
  5. 5What you can do afterwards

Copilot/Hospitality

Open journey →3 pages
Hospitality · Outlook + Teams: Run My Day0 stepsOpen
Hospitality · PowerPoint: Tell the Story0 stepsOpen
Hospitality · Word + Create + Work IQ0 stepsOpen