Skip to main content
TechWaymark
Market

Archived certification · retired

Azure Security Engineer Associate (AZ-500)

The certification, its exam and its renewal assessment were retired on 31 August 2026. SC-500 covers the nearest equivalent ground and is live, but Microsoft's AZ-500 pages do not state that it replaces AZ-500, so treat it as the current alternative rather than an announced successor. A held AZ-500 does not transfer.

Vendor record

Retired

The certification, its exam and its renewal assessment were retired on 31 August 2026. SC-500 covers the nearest equivalent ground and is live, but Microsoft's AZ-500 pages do not state that it replaces AZ-500, so treat it as the current alternative rather than an announced successor. A held AZ-500 does not transfer.

Current name
Azure Security Engineer Associate (AZ-500)
Exam code
AZ-500
Ongoing commitment

The certification and renewal assessment are retired. An earned or renewed credential remains active until its recorded expiry; further renewal is unavailable.

Renewal sources & exceptions

Renewal policy checked 2026-09-28. Check the linked provider policy for current fees and eligibility.

Source: Microsoft Learn · Read 22 September 2026

Sourced fields only; this does not mean every exam detail has been verified. Pricing and renewal policies have their own sources and check dates. Confirm the currency, tax and final booking total with the vendor.

Microsoft Certified: Azure Security Engineer Associate Microsoft exam pricing

Role-fit guidance is TechWaymark editorial interpretation. It is separate from the recorded vendor facts and does not measure hiring outcomes.

Existing candidates and holders

Check the vendor's booking and credential rules if you are already studying or hold this qualification. An exam retirement does not erase your previous learning. This page preserves the record and does not change any saved credential.

Practical exercise for existing holders
Certifications Project guide Home projects Back to certification

Home labs & practical projects

Review an inherited Azure security baseline

A project to do with your own tools, with guidance on what to create and capture.

Design project Suggested time: 90–120 minutesNo hardware required for the design

For existing holders and historical learning. Check the current credential before starting exam preparation.

01

What you could create

An existing AZ-500 holder is asked to review an older Azure environment with broad administrative access and incomplete security monitoring.

Example evidence format
Project evidence map (example)
Legacy baseline reviewScope and inputs
Prioritised remediation and validation registerDecisions and reasoning
Evidence record (example)
EvidenceWhat to capture
Legacy baseline reviewShow the inputs, scope and decisions behind this record. Each finding has evidence, an owner and a validation method.
Prioritised remediation and validation registerInclude the evidence supporting your conclusion. The review avoids treating an archived exam as current product guidance.
02

What you'll need

Document, spreadsheet or diagram tool

Invent a historical baseline containing one privileged group, a public storage exception and an unreviewed alert. Use current product documentation when assessing remediation.

Project record

Keep the working files for legacy baseline review and record assumptions as you go.

Current reference material

Use the linked provider resources to verify the features, access terms and version relevant to your project.

Access & cost

No paid platform is needed for the written version. Use a document, spreadsheet or diagram tool you already have.

The organisation and records are fictional. Write down assumptions; do not substitute confidential employer information.

03

Suggested milestones

  1. 1

    Plan and investigate

    Separate identity, network, data and monitoring findings.

  2. 2

    Develop your approach

    Prioritise corrections by business exposure and operational dependency.

  3. 3

    Verify and explain

    Write validation steps for each change and note where the old baseline needs current guidance.

04

Useful resources

Use these resources to deepen your understanding and check key details.

Official certification objectives

Review the current provider requirements and relevant subject areas.

Explore external learning resources

Find relevant providers and check features, access requirements and costs.

Turn the project into evidence

Keep your artefacts and reasoning together so you can explain what you did.

A useful starting point

Invent a historical baseline containing one privileged group, a public storage exception and an unreviewed alert. Use current product documentation when assessing remediation.

What a good result looks like
  • Each finding has evidence, an owner and a validation method.
  • The review avoids treating an archived exam as current product guidance.
  • Administrative access recovery is considered before restrictions are applied.

Finish the project

Keep the decision record and note unanswered questions. A written design is not evidence that a technical control has been tested.

Independent home-project guidance, not an official vendor lab or a claim of complete exam coverage. Use your own tools and label the work accurately.

Explore the certification library