AzPolicyAdvertizer

last sync: 2025-Oct-31 18:22:59 UTC

Azure Front Door profiles should use Premium tier that supports managed WAF rules and private link

Azure BuiltIn Policy definition

Source Azure Portal
Display name Azure Front Door profiles should use Premium tier that supports managed WAF rules and private link
Id dfc212af-17ea-423a-9dcb-91e2cb2caa6b
Version 1.0.0
Details on versioning
Versioning Versions supported for Versioning: 1
1.0.0
Built-in Versioning [Preview]
Category CDN
Microsoft Learn
Description Azure Front Door Premium supports Azure managed WAF rules and private link to supported Azure origins.
Cloud environments AzureCloud = true
AzureUSGovernment = unknown
AzureChinaCloud = unknown
Available in AzUSGov Unknown, no evidence if Policy definition is/not available in AzureUSGovernment
Mode Indexed
Type BuiltIn
Preview False
Deprecated False
Effect Default
Audit
Allowed
Audit, Deny, Disabled
RBAC role(s) none
Rule aliases IF (1)
Alias Namespace ResourceType Path PathIsDefault DefaultPath Modifiable
Microsoft.Cdn/Profiles/sku.name Microsoft.Cdn
Microsoft.Cdn		 profiles
profiles		 sku.name
properties.sku.name		 True
False
sku.name		 False
False
Rule resource types IF (1)
Compliance
The following 2 compliance controls are associated with this Policy definition 'Azure Front Door profiles should use Premium tier that supports managed WAF rules and private link' (dfc212af-17ea-423a-9dcb-91e2cb2caa6b)
Control Domain Control Name MetadataId Category Title Owner Requirements Description Info Policy#
Azure_Security_Benchmark_v3.0 NS-2 Azure_Security_Benchmark_v3.0_NS-2 Microsoft cloud security benchmark NS-2 Network Security NS-2 Secure cloud services with network controls Shared **Security Principle:** Secure cloud services by establishing a private access point for the resources. You should also disable or restrict access from public network when possible. **Azure Guidance:** Deploy private endpoints for all Azure resources that support the Private Link feature, to establish a private access point for the resources. You should also disable or restrict public network access to services where feasible. For certain services, you also have the option to deploy VNet integration for the service where you can restrict the VNET to establish a private access point for the service. **Implementation and additional context:** Understand Azure Private Link: https://docs.microsoft.com/azure/private-link/private-link-overview n/a link 126
U.07.1 - Isolated U.07.1 - Isolated 404 not found n/a n/a 60
Initiatives usage
Initiative DisplayName Initiative Id Initiative Category State Type polSet in AzUSGov
[Preview]: Microsoft cloud security benchmark v2 e3ec7e09-768c-4b64-882c-fcada3772047 Security Center Preview BuiltIn unknown
NL BIO Cloud Theme 6ce73208-883e-490f-a2ac-44aac3b3687f Regulatory Compliance GA BuiltIn unknown
NL BIO Cloud Theme V2 d8b2ffbe-c6a8-4622-965d-4ade11d1d2ee Regulatory Compliance GA BuiltIn unknown
History
Date/Time (UTC ymd) (i) Change type Change detail
2022-03-25 18:52:24 add dfc212af-17ea-423a-9dcb-91e2cb2caa6b
JSON compare n/a
JSON
api-version=2021-06-01
EPAC