Training course
This is a free, self-paced reading course for SC-500: Microsoft Certified: Cloud and AI Security Engineer Associate, the associate-level credential that replaces AZ-500 and widens the job scope beyond Azure alone to the whole surface a security engineer defends. SC-500 asks you to design and operate controls across Microsoft Entra, Azure, Microsoft 365, and the AI stack, so the course is written to be read straight through before you start drilling practice questions: it builds the vocabulary and the control model first, so a wrong answer later becomes a gap you can name rather than a fact you memorize.
The course is organized as one module per official exam domain, in the order Microsoft publishes them, and each module carries the domain’s published weight. That structure matters more on SC-500 than on most exams, because the weights are not flat: securing storage, databases, and networking is the single heaviest domain, and the other three sit a band below it. Reading in weighted order keeps you from spending your first week on the AI-security material simply because it is the newest part of the blueprint. Every lesson ends with its key terms and suggested further reading, so the course works as a reference after the first pass as well as a syllabus during it.
What the course covers
Manage identity, access, and governance
Module 1 · 20-25%Microsoft Entra ID identity protection and Conditional Access with authentication strengths, phishing-resistant MFA, multifactor, and passwordless; Privileged Identity Management for just-in-time role activation with approval workflows; workload identities and Entra Agent ID for governing AI-agent identity; Continuous Access Evaluation; Entra ID Governance access reviews and access packages; Azure RBAC and ABAC with the condition builder; Azure Policy at management-group scope with restricted exemption rights; and Microsoft Purview data governance touchpoints. This module sets the identity foundation the other three build on, an admin-role misassignment tends to defeat every downstream control in the chain.
Secure storage, databases, and networking
Module 2 · 25-30%The heaviest domain, and the one to budget the most time for. Storage account hardening with private endpoints, disabled shared-key and anonymous access, a TLS 1.2 minimum, and customer-managed keys in Key Vault or Managed HSM; immutable blob storage with locked time-based retention; Azure Files authentication modes across AD DS, Entra Kerberos, and Entra Domain Services; Azure SQL Database and Managed Instance security (Always Encrypted with secure enclaves, Defender for SQL, and TDE with CMK) plus Cosmos DB CMK and private endpoints; Azure Firewall Premium with IDPS in alert-and-deny mode and TLS inspection; Azure Virtual Network Manager security admin rules that supersede subnet NSGs; Front Door Premium WAF with bot protection and rate limiting, and Application Gateway WAF; private endpoints and Private Link Service for partner-tenant access; ExpressRoute encryption using MACsec at layer 2 on ER Direct ports and IPsec-over-ExpressRoute at layer 3; and Azure DNS Private Resolver for hybrid resolution.
Secure compute (including AI workloads)
Module 3 · 20-25%Where SC-500 diverges most sharply from the SOC-analyst track (SC-200, which continues). Microsoft Defender for Endpoint with direct-sensor onboarding; Defender for Servers Plans 1 and 2, where Plan 2 unlocks agentless machine scanning, full Defender Vulnerability Management, and just-in-time VM access; Azure Bastion Premium with session recording to a Log Analytics workspace; JIT VM access replacing scheduled NSG jobs; Trusted Launch VMs with Secure Boot and vTPM measuring the boot chain; Azure Confidential Computing VMs on AMD SEV-SNP or Intel TDX for memory-encrypted TEE workloads; Azure Machine Configuration applying Defender for Cloud baselines to Arc machines; Container Registry supply-chain security with content trust and signed-image admission policy; AKS ingress and egress control through internal-only environments, private endpoints for ACR, and a kubelet identity holding AcrPull. Then the AI-security stack: Microsoft Defender for AI Service for prompt-injection and credential-leak detection, Purview Data Security Posture Management for AI to surface oversharing before a broad Copilot rollout, Purview real-time protection for Copilot Studio, Foundry content filters and safety systems with custom categories, Azure API Management LLM policies such as llm-token-limit and llm-emit-token-metric used as an AI gateway, and Entra Agent ID with Conditional Access to govern AI-agent sign-in.
Manage and monitor security posture
Module 4 · 20-25%Microsoft Defender for Cloud secure score and the split between foundational and paid Defender CSPM, where the paid tier adds attack path analysis, agentless secret scanning, and sensitive data discovery; the regulatory compliance dashboard and adding standards such as NIST SP 800-53 R5, ISO 27001, HIPAA HITRUST, PCI DSS 4.0, and NIST 800-171; Defender EASM for discovering forgotten public assets; MDVM findings across endpoints and servers; multicloud onboarding through the AWS connector with its CloudFormation stack and STS role, and the GCP connector; Microsoft Sentinel workspace design for multi-region residency with Azure Lighthouse projecting cross-workspace query rights; Sentinel roles: Responder for triage, Contributor for rule authoring, Reader for read-only; Content hub solutions that bundle connectors and analytic rules; Azure Monitor Agent with data collection rules in place of the retired Log Analytics agent; automation rules for incident-creation actions and playbooks authenticating with managed identity; interactive versus archive retention with Search jobs for long-tail queries; Defender XDR Advanced Hunting across the AuditLogs schema; and Microsoft Security Copilot workspaces provisioned with Security Compute Units, including Security Store agents that run inside those workspaces and consume SCU capacity.
How to use it
Read a module, then work the matching portion of the SC-500 practice exam rather than saving all the questions until the end. SC-500 items are scenario-based, so reading a domain and immediately testing it exposes the gap between recognizing a service name and knowing which control the scenario actually calls for, whether a given requirement wants a private endpoint or a service endpoint, Defender for Servers Plan 1 or Plan 2, a Sentinel Responder or a Contributor. Weight your reading the way the blueprint does: module 2 alone can carry up to 30% of the exam. The course modules themselves open once you are signed in to a free Certifym account.
The AI-security material in module 3 is the part with the least available hands-on practice, so treat it deliberately, if you have never looked at a Foundry content filter, a DSPM for AI oversharing report, or an API Management token-limit policy, open them in a tenant while you read rather than trusting recall. For exam logistics (item count, working time, the scaled 700 cut score, cost, prerequisites, and the free annual renewal) see the SC-500 certification guide.
Private endpoints, Private Link Service, and DNS
Private Link is the mechanism by which a platform service stops being an internet endpoint and becomes an address inside your network. It is the single most heavily used networking control on SC-500, and most of the difficulty in it is not the endpoint — it is DNS.
What a private endpoint actually is
A private endpoint is a network interface in one of your subnets, holding a private IP address from that subnet's range, mapped to a specific instance of a platform service — this storage account, that SQL server, that key vault. Traffic to the private IP is carried over the Microsoft backbone to the service instance. The service instance is the private link resource, and each one exposes one or more sub-resources or target groups: a storage account exposes blob, file, table, queue, web, and dfs separately, so an account that needs both blob and file access privately needs two private endpoints.
That per-sub-resource detail is a reliable exam point. A scenario where blob access works privately but file access still fails is describing a missing second private endpoint.
Two important properties follow from the design:
- The endpoint is instance-specific. Unlike a service endpoint, which opens a subnet to a whole service, a private endpoint reaches one resource. Data exfiltration to an attacker's storage account in another subscription is not possible through your private endpoint.
- The endpoint is reachable from anywhere that can route to the subnet — peered virtual networks, ExpressRoute circuits, VPN gateways, and on-premises networks. This is why private endpoints, not service endpoints, are the answer for on-premises access to PaaS.
DNS is where deployments fail
The service's public name — account.blob.core.windows.net — resolves publicly to a public IP. When you create a private endpoint, Azure creates a CNAME from that public name to a privatelink alias, account.privatelink.blob.core.windows.net. Your clients must resolve that privatelink name to the private IP. If they do not, they resolve the public IP and the connection fails or, worse, silently takes the public path.
The mechanism is a private DNS zone named for the service — privatelink.blob.core.windows.net, privatelink.database.windows.net, privatelink.vaultcore.azure.net, and so on — containing an A record for the endpoint, linked to the virtual networks whose clients need to resolve it. The portal offers to create and wire this up when you create the endpoint, and in a single-network deployment that is sufficient.
In a hub-and-spoke or hybrid estate it is not. The requirements become:
- One private DNS zone per service type, ideally centralized in a hub or platform subscription rather than duplicated per spoke.
- Virtual network links from that zone to every virtual network whose workloads must resolve the name. Links are not transitive across peering — a spoke peered to a hub does not inherit the hub's zone links.
- A resolution path for on-premises clients, which cannot query Azure private DNS zones directly. Historically this meant DNS forwarder virtual machines; the supported answer now is Azure DNS Private Resolver, covered in its own lesson.
- Azure Policy to create the DNS zone group automatically when a private endpoint is created, so a team cannot deploy an endpoint without the record.
When a scenario says a private endpoint was created but clients still connect over the public internet, or a name resolves to a public address from on-premises, the defect is DNS, not the endpoint.
Closing the public door
Creating a private endpoint does not disable the public one. You must also set the service's public network access to disabled — on the storage account, the SQL logical server, the key vault, the Cosmos account. Until you do, the private path is an addition rather than a replacement, and a client outside the network can still reach the service subject only to authorization.
Network policies on the endpoint subnet
By default, network security groups and user-defined routes did not apply to private endpoint traffic, because the endpoint's NIC had network policies disabled. Subnets now support enabling private endpoint network policies so that NSGs and UDRs do apply, which lets you filter traffic to endpoints and force it through a firewall. Where a scenario requires inspection of traffic destined for a private endpoint, this setting is the prerequisite. Verify the current default and supported combinations in Microsoft's documentation.
Private Link Service: the other direction
Private endpoints consume a service. Private Link Service publishes one. If you run a workload behind a Standard internal load balancer, you can front it with a Private Link Service and let consumers — including consumers in entirely different tenants — create private endpoints to it. The consumer never gains network reach to your virtual network; they get a single endpoint to your published frontend.
Key properties:
- Requires a Standard SKU internal load balancer; it is not something you attach directly to a virtual machine.
- Uses a dedicated subnet with NAT IP configuration for source address translation.
- Connection requests can be set to auto-approve for named subscriptions or to manual approval, giving the provider a gate over who may connect. The alias you share with a consumer is what they use to request the endpoint.
- The TCP Proxy v2 protocol option preserves the consumer's source information for the backend, which matters if you need to attribute traffic to a specific consumer.
Private Link Service is the answer whenever a scenario says a partner or customer in another tenant must reach your application privately without network peering, without VPN, and without exposing it to the internet. Peering would give them routing into your address space; Private Link Service does not.
A short decision list
- Your workload needs private access to a PaaS service — private endpoint, plus DNS, plus public access disabled.
- On-premises needs the same — private endpoint plus a DNS resolution path over the hybrid link.
- You want a cheap subnet-level restriction and public exposure is acceptable — service endpoint.
- You publish a service others consume privately — Private Link Service behind a Standard internal load balancer.
- You must inspect traffic to a private endpoint — enable private endpoint network policies and route through a firewall.
Frequently asked questions about the SC-500 training course
Is the SC-500 training course free?
Yes. The course costs nothing to read and opens once you are signed in to a free Certifym account, no payment and no card.
How is the course structured?
One module per official SC-500 exam domain, in Microsoft’s published order, with each module weighted to the domain’s published percentage range. There are four modules, matching the four domains. Within each module the material is broken into short lessons, followed by key terms and further reading.
Does this replace Microsoft’s official training?
No. Microsoft Learn publishes the authoritative SC-500 skills outline and free official learning paths. This course is an independent study companion, written to be read quickly and to slot alongside practice questions, not a substitute for the official study guide.
Do I need any prerequisites before starting?
SC-500 has no formal prerequisites, but Microsoft recommends SC-900 first. The course assumes you can already manage identity and access in Microsoft Entra and are comfortable with Azure storage, networking, and compute as an administrator would use them, it teaches how to secure those surfaces, not how they work from scratch. If that grounding is thin, read the SC-900 course or the AZ-104 course first.
What should I do after finishing the course?
Move to the SC-500 practice exam and work it until you are clearing 75% consistently across all four domains rather than leaning on your strong ones. The 700 out of 1000 pass mark is a scaled score, so the extra margin is deliberate headroom, not perfectionism.
Is the course current with the latest SC-500 outline?
The course is built against the four-domain outline Microsoft publishes for SC-500, with the weights as published. SC-500 is a new credential replacing AZ-500, and the AI-security portion of the blueprint tracks fast-moving services, so Microsoft may revise the outline at any time. Verify the current skills outline and weightings on Microsoft Learn before you sit the exam.
Trademark notice & independence. Certifym.net is operated by Certifym Exam Services, LLC and is not affiliated with, endorsed by, or sponsored by Microsoft Corporation. Microsoft®, Microsoft Certified®, Azure®, Microsoft Entra™, Microsoft Defender™, Microsoft Sentinel™, Microsoft Purview™, Microsoft 365®, Copilot™, and SC-500 are trademarks or registered trademarks of Microsoft Corporation in the United States and/or other countries. Use of these marks is solely to identify the certification for which these study materials are intended. The SC-500 exam objectives and skills outline are the property of Microsoft Corporation; candidates should review the official, current study guide directly on Microsoft Learn.
All course content, questions, answers, and explanations on Certifym are original content created for study purposes. They are not actual Microsoft training materials or examination questions and are not represented as such. Studying with these materials does not guarantee a passing result on any live certification exam. Exam requirements, format, domain weights, pricing, and renewal policies are set by Microsoft and may change; always verify current details on Microsoft Learn before scheduling your exam.