Training Documentation
The training documentation helps Azure architects learn the platform from a solutions design perspective rather than a feature reference perspective. It complements official Microsoft documentation by focusing on how resources fit together in real architectures, what properties matter when you are designing for production, and how to evaluate trade-offs between configuration choices.
Organization
Content is grouped into categories that follow the way most Azure work is scoped in practice: compute, networking, storage, database, web, data and analytics, and others. A dedicated Azure Fundamentals section covers cross-cutting concepts (resource hierarchy, identity, governance, regions and availability zones, pricing models) that apply across categories.
Inside each category, resources are listed individually. Every resource has its own page structured into six consistent sections, so once you are familiar with the layout, you can jump directly to the section you need.

Resource page structure
Each resource page is split into the following sections:
1. Introduction
An overview of the resource: what it is, its key characteristics, the model it follows (PaaS, IaaS, serverless, managed service), and the essential properties that define its behavior. The goal of this section is to give you enough context to understand where the resource fits within a solution before going deeper.

2. Architecture
How Azure implements and host this resource in the backend and the essential architectural properties that define its behavior. This section gives you detailed information about the core implementation and underlying technology to provide an understanding about the capabilities and limitations of this resource.
3. How to create
Every way the resource can be provisioned, with examples for each option:
- Azure REST API
- ARM templates
- Bicep
- Terraform
- PowerShell
- Azure CLI
- Azure SDKs (per supported language)
4. Important infrastructure properties
The infrastructure properties that materially affect how the resource behaves, scales, costs, or integrates with other services. Each property includes a deeper explanation of what it controls, when it matters, and what to consider when choosing a value. This is the section to read before deploying a resource in a context you are not already familiar with.
5. Child resources
The child resource types associated with the resource, how they relate to the parent, and the use cases each one solves. For example, the SQL server page covers databases, firewall rules, AAD admins, and auditing settings, along with when and why you would configure each.
6. How to use and administrate
Operational guidance for the resource once it is deployed: day-to-day usage patterns, common administrative tasks, monitoring and diagnostics, scaling and maintenance, and known operational pitfalls.
7. Practice
Hands-on learning material:
- Tutorial videos walking through specific scenarios.
- Hands-on labs you can run directly through Clophi's resource forms, so you can practice deploying and configuring without leaving the platform.
- Real-world use cases demonstrated through built-in architectures that you can inspect, deploy, and modify.



