
Cybersecurity & IT
Azure Fundamentals in 14 Days: An Unofficial AZ-900 Study Guide
AZ-900 Cloud Concepts, Azure Architecture, Services, Security, Governance, and Management
by Todd Michael
Available nowPrepare for AZ-900 with a structured study guide that makes Azure concepts understandable and useful beyond exam day. Whether you are entering IT, moving into cloud work, or adding Azure literacy to a security role, this book connects foundational terminology to the choices organizations make when deploying and managing services.
Follow the day-by-day 14-day plan for an intensive preparation cycle, or use the 30-day alternative when you need more time. An objective map helps you organize your studies, while worked examples, original review questions with explanations, and key-term flashcards reinforce what you learn. Guided labs introduce the Azure portal, command-line references, resource organization, identity, monitoring, and cost controls, with attention to permissions and potential charges.
Across 24 chapters, you will explore cloud models, Azure architecture, compute, networking, storage, security, governance, and management. Each chapter also includes common pitfalls, exam tips, and practical interview questions to help turn knowledge into confidence.
This is an independent, unofficial guide. It is not affiliated with or endorsed by Microsoft.
Contents
- 1. AZ-900 Preparation and the Cloud Fundamentals Roadmap
- 2. Cloud Computing Concepts and Shared Responsibility
- 3. Cloud Deployment Models and Service Models
- 4. Benefits and Characteristics of Cloud Services
- 5. Azure Regions and Global Infrastructure
- 6. Azure Resources and Organizational Hierarchy
- 7. Azure Compute Services and Hosting Choices
- 8. Azure Virtual Networking and Connectivity
- 9. Azure Storage Services and Storage Accounts
- 10. Storage Movement and Migration
- 11. Azure Identity and Authentication
- 12. Azure Authorization and Access Protection
- 13. External Access and Network Security
- 14. Azure Cost Management and Pricing
- 15. Tags, Governance, and Resource Organization
- 16. Security Responsibilities and Defense in Depth
- 17. Microsoft Defender for Cloud
- 18. Azure Policy, Resource Locks, and Compliance
- 19. Azure Portal, Cloud Shell, and Command-Line Tools
- 20. Infrastructure as Code and Azure Resource Manager
- 21. Azure Monitoring and Service Health
- 22. Integrated Architecture and Service Selection
- 23. Objective-by-Objective Review and Practice
- 24. Final Readiness, Interview Practice, and Ongoing Reference
- Other Books by Todd Michael
Read a sample: 1. AZ-900 Preparation and the Cloud Fundamentals Roadmap
Azure Fundamentals is an entry point into cloud computing and Microsoft Azure. It asks you to recognize what cloud services do, distinguish common architecture and service choices, and understand how organizations manage, govern, secure, and monitor their environments. You do not need to become a specialist in every Azure product. You do need a reliable mental model for deciding which kind of service or management tool fits a given need.
That distinction shapes the way you should study. Memorizing that a virtual machine is a compute service is useful; explaining why an organization might choose one instead of a managed application platform is more useful. Similarly, recognizing the name Azure Policy is a start, but you should also know that it serves a different purpose from an access-control role or a resource lock.
This chapter establishes your route through the book. You will:
- Translate the broad AZ-900 subject areas into a chapter-by-chapter study map.
- Choose a 14-day intensive plan or a 30-day alternative.
- Set a baseline with original diagnostic questions and explanations.
- Prepare a safe, cost-aware approach to hands-on practice.
- Build a study routine that combines reading, recall, scenarios, and review.
The study plans are guides, not promises of a passing result. Your starting experience, available time, and familiarity with cloud terminology all matter. Treat an unfamiliar topic as a signal to investigate, not as evidence that you do not belong in technical work.
This is an unofficial study guide. Microsoft can change exam objectives, product names, interfaces, and policies. Before starting your schedule, find the official Microsoft Learn page for Exam AZ-900 and open its current study guide or skills outline. Verify the topics, their published emphasis, and any exam arrangements that matter to you. Repeat that check before your final review.
Use the map below as a bridge between this book and the official outline—not as a substitute for it. The left column groups the major AZ-900 topic areas under the familiar headings of cloud concepts, Azure architecture and services, and Azure management and governance. Compare each grouping with the wording and subtopics in the current official guide. If Microsoft adds, removes, or reorganizes a skill, annotate your study log and consult current Microsoft documentation for the difference.
The book’s chapter titles are learning aids. They are not an assertion that Microsoft uses the same chapter structure or assigns a particular number of questions to each topic.
Some subjects naturally cross these categories. Identity, for example, affects both service access and security governance. Use the chapter references to learn the concept; use the current official outline to confirm how Microsoft describes and organizes the skill.
A practical annotation might read: “Official outline calls for describing a service’s purpose; Chapter 21 compares it with related monitoring tools.” If the outline calls for a topic that you cannot locate in the map, add it to your log rather than assuming it is unimportant.
A fundamentals-level scenario often supplies a business need and asks you to recognize the best category of solution. The challenge is not usually to configure every setting. It is to identify the requirement, eliminate mismatched choices, and understand the responsibility that remains with the customer.
Consider an organization that expects an application’s demand to change over time. Scalability is the ability of a system to handle changes in demand by adjusting capacity. Elasticity is closely related: it emphasizes adjusting capacity as demand rises or falls, often dynamically. Elasticity is not a wholly separate alternative to scalability; it describes a way capacity can respond to changing demand.
Now consider a different requirement: the organization wants an application to remain available when a component fails. That is not the same problem as increasing capacity. A scalable design might have more instances, but resilience depends on how those instances and their dependencies are designed and deployed. Chapters 4 and 5 develop these distinctions.
When you read any scenario, ask:
1. What outcome is required? Lower operational effort, increased capacity, controlled access, spending visibility, or something else?
2. What is the scope? A sign-in, one resource, a group of resources, a subscription, or an application?
3. Who manages the relevant layer? The customer, the cloud provider, or both in different ways?
4. What is the closest fit? Choose based on the stated requirement, not on a product name that merely sounds familiar.
5. What remains uncertain? In practice, verify service features, regional availability, costs, and current documentation before implementation.
These questions work across the book. They also discourage a common mistake: treating every security, governance, or monitoring tool as interchangeable because all of them contribute to responsible operations.
A useful study session has four stages:
1. Preview. Look at the chapter’s objectives and terms. Decide what you expect to learn.
2. Learn. Read actively, making a brief note of distinctions that matter.
3. Retrieve. Close the book and explain the idea or answer a question from memory.
4. Apply and correct. Work through a scenario or lab, then compare your reasoning with the explanation.
Retrieval is important because recognition can be misleading. A page may feel familiar while you read it, yet you may struggle to explain the same concept without the text. A short, honest attempt from memory exposes that gap early.
Keep a study log with a line for each topic that needs another pass:
Record your reasoning, not just whether an answer was…