AZ-900: Recent Updates to the Azure Fundamentals Certification Exam

An article describing AZ-900’s “recent updates” must distinguish the date of its original publication from the live examination blueprint. This page once discussed January 2024 changes. In October 2026, the current authoritative English skills measured are dated July 20, 2026. A candidate should not schedule a test on the assumption that a 2024 training-provider update represents the current exam.

Microsoft has not replaced Azure Fundamentals with a new examination simply because some features were renamed. Its current change log describes minor changes to subordinate compute/networking and deployment/management objectives while retaining the same three broad skill groups. The appropriate response is to reconcile material selectively, not to restart every cloud concept from zero.

Locate the actual effective date

Course publication dates, product renames and issuer exam-outline changes are separate events. A provider may launch a 2024 video while Microsoft changes an outline later. Confirm the exact AZ-900 exam code, the effective date of skills measured and the issuer’s change log. Microsoft also notes that localized examination versions may receive English updates later, so check the chosen testing language.

The historical January 2024 material highlighted terminology modernization and service categories. Its explanations may still teach useful concepts, but the old date should never be presented as “the new exam” in 2026. Treat screenshots and percentage tables from the older course as evidence of its era, not permanent examination rules.

Preserve the three current skill areas

The July 20, 2026 AZ-900 blueprint measures cloud concepts at 25–30%, Azure architecture and services at 35–40%, and management and governance at 30–35%. These are ranges, not a promise of a fixed question count per domain. A learner should cover every area rather than over-optimizing for an imagined total.

Cloud concepts include shared responsibility, cloud models, service models, consumption pricing and benefits such as scalability or reliability. Architecture includes regions, availability zones, resource hierarchy, compute, networking and storage categories. Governance includes Azure identity, RBAC, resource deployment, policy, costs and monitoring.

Microsoft’s 2026 change log highlights minor edits in some compute/networking and management/deployment subtopics. Review them against the current AZ-900 objective overview; do not invent a fourth scored domain or claim Azure fundamentals has become an administrator-level lab exam.

Interpret identity terminology and responsibilities

Microsoft Entra ID is the current product name for the identity service previously called Azure Active Directory. An older diagram may still label it “Azure AD.” Understanding the relationship prevents a candidate from assuming those are unrelated products, but a name change does not itself explain authorization.

Suppose an employee signs in to Azure but cannot modify a resource group. The next question is about role assignments at the relevant scope, not simply authentication. Azure RBAC controls Azure resource operations; Microsoft Entra directory roles address directory responsibilities. Identity policies, resource policy and monitoring tools solve different problems.

A useful learning note records both the historical term and the current service name, along with the purpose of the capability. This is more durable than treating every rebranding as a new concept.

Detect service lifecycle changes

A major current exception is Azure Blueprints (Preview). Microsoft announced its phased retirement: new definitions and versions stopped being created July 31, 2026; existing-definition modifications and new assignments are blocked from October 31; assignment changes from December 31; and final retirement is January 31, 2027. This timeline matters even though broader governance concepts remain useful.

For a new deployment, Microsoft recommends replacing relevant Blueprints functions with Azure Deployment Stacks and template specs. A discussion of historical Azure Blueprints governance should describe the migration, not promote a retiring preview feature as the current default.

Service lifecycle checks should be separate from domain weighting. A tool can be retired while its underlying principles—authorization, infrastructure as code, consistent configuration and policy—remain important to understanding Azure.

Keep current concepts that remain valid

A hybrid cloud still combines on-premises and cloud environments; using two cloud regions does not automatically make the design hybrid. Regions and availability zones still address distinct placement and failure boundaries. A budget alert does not stop all costs. Different service models still change customer responsibility.

These principles can be retained from older training when correctly explained. Replace outdated vendor labels and screenshots, confirm currently available services and avoid false assumptions about feature coverage in every region.

For example, a company needing geographic residency and zone resilience should check deployment location and supported availability features. One needing a repeatable configuration should examine declarative deployments and policy. An old note saying “always use Blueprints” is no longer sound in late 2026.

Update an existing study course efficiently

Mark each lesson current, historical but useful, or outdated. Compare Microsoft’s live outline with the material, then replace obsolete service descriptions rather than rewatching everything. The AZ-900 study order may help place the missing topics into the candidate’s schedule.

Take Microsoft’s free Practice Assessment to identify reasoning gaps and use its exam sandbox to explore the interface. Microsoft currently gives the fundamentals exam 45 minutes, while the number of questions may vary. Do not adopt a commercial mock-test score threshold as a guarantee of passing.

The sound interpretation of an AZ-900 update is precise: identify the new effective guide, preserve correct cloud principles, fix renamed or retiring tools, practice altered descriptions and verify examination arrangements with Microsoft.