Learning Paths¶
Use this page to choose a reading path based on your role and goal. Each path is numbered, so read the pages in order for the best result. Every path ends with a checklist of concrete outcomes you should be able to demonstrate.
Pick one primary path first
If you fit multiple roles, pick the one that matches your current goal, complete that path, then read a second path opportunistically. Trying to follow every path in parallel dilutes progress.
Choose Your Path¶
| Role | Goal | Time Budget | Start With |
|---|---|---|---|
| Beginner | Understand storage accounts, services, and tiers | 1-2 hours | Overview, Storage Services at a Glance |
| Developer | Read and write data from apps using SDK or REST | 2-3 hours | Platform Hub, Reference Hub |
| Operator | Configure redundancy, lifecycle, backup, and monitoring | 3-4 hours | Scenario Router, Operations Hub |
| Troubleshooter | Diagnose access, throttling, and replication issues | 2-4 hours + on-call reference | Troubleshooting Hub |
Recommended Sequence¶
mermaid flowchart TD A[Start Here] --> B[Platform Concepts] B --> C{Choose your path} C --> D[Beginner: Accounts and Services] C --> E[Developer: SDK and Auth] C --> F[Operator: Redundancy and Lifecycle] C --> G[Troubleshooter: Access and Perf] D --> H[Production Readiness] E --> H F --> H G --> H
Beginner Path¶
Understand what an Azure Storage account is, how the four services (Blob, File, Queue, Table) differ, and how to create your first container or share.
Time: 1-2 hours
mermaid flowchart TD A[Overview] --> B[Services at a Glance] B --> C[Storage Account Basics] C --> D[Choose a Service] D --> E[First Container or Share]
Read in order:
- Overview
- Storage Services at a Glance
- Platform Hub — storage account, blob, file, queue, table basics
- Scenario Router
- Reference Hub — glossary and service selection guide
Outcomes¶
- You can name the four storage services and pick the right one for a use case.
- You can create a storage account with the right redundancy (LRS, GRS, ZRS) for your requirement.
- You can upload a blob and set an access tier (Hot, Cool, Cold, Archive).
- You know where to find the storage service selection guide.
Microsoft Learn anchors¶
Developer Path¶
Read and write data from applications using the Azure SDK, REST APIs, or AzCopy. Focuses on access models, authentication with managed identity, and SDK ergonomics.
Time: 2-3 hours
mermaid flowchart TD A[Access Models] --> B[Managed Identity or SAS] B --> C[SDK or REST] C --> D[AzCopy for Bulk] D --> E[Security Best Practices]
Read in order:
- Platform Hub — focus on access models and authentication
- Reference Hub — access methods cheatsheet
- Operations Hub — configure access and identity, AzCopy usage
- Best Practices Hub — security patterns (RBAC, SAS, encryption)
- Storage Services at a Glance — pick the right service for the workload
Outcomes¶
- You can authenticate to Storage with managed identity from a workload.
- You can generate a user-delegated SAS token with least-privilege scope.
- You can read and write blobs, files, or queues using the Azure SDK.
- You can move bulk data with AzCopy and choose between synchronous and async patterns.
Microsoft Learn anchors¶
Operator Path¶
Configure and operate storage accounts in production: redundancy, lifecycle policies, backup, private connectivity, and monitoring.
Time: 3-4 hours
mermaid flowchart TD A[Redundancy Choice] --> B[Lifecycle Policies] B --> C[Backup and DR] C --> D[Private Endpoints] D --> E[Monitoring and Alerts]
Read in order:
- Scenario Router
- Operations Hub — create account, network rules, private endpoints, lifecycle, backup, monitoring
- Best Practices Hub — redundancy, lifecycle, cost, networking, performance
- Platform Hub — redundancy and durability, networking and private access
- Reference Hub — redundancy options and networking cheatsheet
Outcomes¶
- You can pick between LRS, ZRS, GRS, and GZRS for a workload SLA target.
- You can define a lifecycle policy that tiers blobs from Hot to Cool to Archive.
- You can restrict a storage account to a Private Endpoint and validate DNS.
- You can set up alerts for throttling, availability, and cost anomalies.
Microsoft Learn anchors¶
Troubleshooter Path¶
Diagnose access denied, throttling, replication lag, and lifecycle-policy failures on Azure Storage.
Time: 2-4 hours + on-call reference
mermaid flowchart TD A[Symptom Triage] --> B[First 10 Minutes] B --> C[Decision Tree] C --> D[Playbooks] D --> E[Post-Incident Notes]
Read in order:
- Troubleshooting Hub
- First 10 Minutes runbooks: Access, Performance, Security
- Decision Tree and Mental Model
- Playbooks Hub — blob access denied, throttling, replication lag, lifecycle
- Reference Hub — access methods and storage networking cheatsheets
Outcomes¶
- You can run the First 10 Minutes runbook for an access, performance, or security symptom.
- You can distinguish RBAC failures from SAS failures from Firewall failures.
- You can interpret Storage metrics to prove or refute throttling as a cause.
- You can select the right playbook from a symptom description.
Microsoft Learn anchors¶
- Monitor, diagnose, and troubleshoot Azure Storage
- Troubleshoot blob storage authorization
- Scalability and performance targets for Blob storage
Track Selection Matrix¶
| Situation | Start with | Then continue to |
|---|---|---|
| First storage account in a subscription | Beginner Path | Operator Path |
| Wiring an application to Storage | Developer Path | Operator Path |
| Preparing for launch | Operator Path | Troubleshooter Path |
| Active incidents | Troubleshooter Path | Operator Path (hardening) |
Urgent access failure? Skip the path.
If a workload is currently failing on 403 or throttled requests, jump directly to Troubleshooting Hub and the First 10 Minutes runbooks.
See Also¶
- Overview
- Storage Services at a Glance
- Scenario Router
- Repository Map
- Platform Hub
- Operations Hub
- Best Practices Hub
- Troubleshooting Hub