Secure application platform services
Defender for Containers, AKS, Container Registry, Container Instances and Container Apps, Functions, Logic Apps, App Service, Web Application Firewall, and API Management back-end protection.
- 24 min
- 9 concepts
- Try it yourself
- 4-question check
Learn
Application platforms share the same security themes: identity for authentication, private networking, no secrets in config, patched images, and runtime threat detection.
- 1
Detect misconfigurations and runtime risks in container workloads by using Defender for Containers
Defender for Containers provides vulnerability assessment of images in registries and running containers (powered by Defender Vulnerability Management), Kubernetes posture recommendations (via Azure Policy for Kubernetes), and runtime threat detection via the Defender sensor, for AKS, EKS, GKE and Arc-enabled Kubernetes.
Remember: Image scanning + posture + runtime detection.
- 2
Implement and configure security controls for Azure Kubernetes Service (AKS)
Use Microsoft Entra integration with Kubernetes RBAC (disable local accounts), a private cluster or authorised IP ranges for the API server, network policies (Azure, Cilium or Calico), Workload Identity for pods, Azure Policy for Kubernetes (pod security), node image auto-upgrade and Key Vault Secrets Store CSI driver.
Remember: Disable local accounts; use Entra with Kubernetes RBAC.
- 3
Implement and configure security controls for Azure Container Registry
Disable the admin user, use Entra identities with AcrPull/AcrPush (or repository-scoped permissions), disable public access with private endpoints (Premium), enable content trust or signing (Notation), quarantine, and Defender for Containers scanning. Use customer-managed keys if required.
Remember: Admin user off; pull with managed identity.
- 4
Implement and configure security controls for Azure Container Instances and Azure Container Apps
ACI: deploy into a VNet, use managed identities, keep secrets in secure environment variables or Key Vault. Container Apps: put the environment in your VNet with internal-only ingress, use built-in authentication (Easy Auth), managed identity, Key Vault secret references, IP restrictions and mTLS between apps.
Remember: Internal ingress keeps Container Apps off the internet.
- 5
Implement and configure security controls for Azure Functions, including authentication and network access
Use App Service Authentication (Entra ID) rather than function keys alone for user-facing APIs, managed identity for outbound calls, Key Vault references for settings, private endpoints for inbound, VNet integration for outbound, HTTPS only and minimum TLS 1.2. Secure the storage account the function app uses.
Remember: Function keys aren't user authentication.
- 6
Implement and configure security controls for Azure Logic Apps
Restrict trigger access with IP ranges or OAuth with Entra ID (authorisation policies), use secure inputs/outputs to hide sensitive data in run history, use managed identity for connectors, and for Standard logic apps use private endpoints and VNet integration.
Remember: Secure inputs/outputs hide secrets in run history.
- 7
Implement and configure security controls for Azure App Service
Turn on HTTPS Only, minimum TLS 1.2+, disable FTP/basic auth publishing, use Easy Auth with Entra ID, managed identity and Key Vault references, access restrictions or private endpoints, and Defender for App Service. Keep the runtime up to date.
Remember: Disable basic auth publishing credentials.
- 8
Implement and configure Azure Web Application Firewall
WAF on Application Gateway or Front Door uses the Default Rule Set (OWASP-based) plus bot protection, custom rules (geo-filtering, rate limiting) and exclusions for false positives. Start in Detection mode, tune, then switch to Prevention. Send logs to Log Analytics.
Remember: Detection first, then Prevention.
- 9
Implement security policies for back-end API protection by using API Management
APIM policies: validate-jwt / validate-azure-ad-token for OAuth, rate-limit-by-key and quota, ip-filter, request validation (content, parameters), and authentication-managed-identity to the back end. Put APIM in a VNet (internal mode) with Application Gateway WAF in front for internet exposure.
Remember: Validate tokens at the gateway, not just the back end.
A secured web API path
- Front Door + WAFGlobal entry, OWASP rules, bot protection.
- API ManagementToken validation, rate limits, managed identity to back end.
- App Service / Container AppsPrivate endpoint or internal ingress only.
- DataKey Vault, SQL, Storage via managed identity and private endpoints.
Try it
Which control fits?
This interactive part needs JavaScript.
In the portal
- Defender for ContainersAzure portal: Microsoft Defender for Cloud > Environment settings > your subscription > Defender plans > Containers
- WAF policiesAzure portal: Web Application Firewall policies (WAF) > Create
- App Service authenticationAzure portal: App Services > your app > Settings > Authentication
Key terms
Click a card to see the definition.
Check your understanding
4 questions. Score 80% or more and these skills are marked as confident in your SC-500 study plan.
Which WAF mode should you start in?
Tune false positives before blocking.
How should AKS pods access Key Vault?
Entra federated identity for pods.
What should be disabled on Azure Container Registry?
It's a shared credential.
Which APIM policy throttles a client by key?
Rate limiting per caller.
Sources
- Microsoft Learn: Overview of Defender for Containers
- Microsoft Learn: AKS security best practices
- Microsoft Learn: Azure Container Registry security
- Microsoft Learn: Securing Azure Functions
- Microsoft Learn: Azure Web Application Firewall
- Microsoft Learn: API Management policies reference
Facts in this lesson are from Microsoft Learn. This site isn't affiliated with Microsoft.