Skip to content

Commit 4dce127

Browse files
committed
edit
1 parent 1096847 commit 4dce127

File tree

1 file changed

+7
-8
lines changed

1 file changed

+7
-8
lines changed

articles/dns/dns-security-policy.md

Lines changed: 7 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -17,29 +17,28 @@ This article provides an overview of DNS security policy. Also see the following
1717

1818
> [!NOTE]
1919
> DNS security policy is currently in PREVIEW.<br>
20-
> See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
20+
> See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.<br>
21+
> Some [Requirements and restrictions](#requirements-and-restrictions) apply to DNS security policy during preview.
2122
2223
## What DNS security policy?
2324

24-
DNS security policy offers the ability to filter and log DNS queries at the virtual network (VNet) level. With DNS security policy you can:
25+
DNS security policy offers the ability to filter and log DNS queries at the virtual network (VNet) level. Policy applies to both public and private DNS traffic within a VNet. DNS logs can be sent to a storage account, log analytics workspace, or event hubs. You can choose to allow, alert, or block DNS queries.
26+
27+
With DNS security policy you can:
2528
- Create rules to protect against DNS-based attacks by blocking name resolution of known or malicious domains.
2629
- Save and view detailed DNS logs to gain inside into your DNS traffic.
2730

28-
DNS security policy applies to both public and private DNS traffic within a VNet.
29-
30-
DNS logs can be sent to a storage account, log analytics workspace, or event hubs. You can choose to allow, alert, or block DNS queries.
31-
3231
A DNS security policy has the following associated elements and properties:
3332
- **[Location](#location)**: The Azure region where the security policy is created and deployed.
3433
- **[DNS traffic rules](#dns-traffic-rules)**: Rules that allow, block, or alert based on priority and domain lists.
3534
- **[Virtual network links](#virtual-network-links)**: A link that associates the security policy to a VNet.
3635
- **[DNS domain lists](#dns-domain-lists)**: Location-based lists of DNS domains.
3736

38-
DNS Security Policy can be configured using Azure PowerShell or the Azure portal.
37+
DNS security policy can be configured using Azure PowerShell or the Azure portal.
3938

4039
## Location
4140

42-
A security policy can only apply to VNets in the same region. You can create any number of security policies in the same region. In the following example, two policies are created in each of two different regions (East US and Central US).
41+
A security policy can only apply to VNets in the same region. You can create up to 10 security policies per region during preview. In the following example, two policies are created in each of two different regions (East US and Central US).
4342

4443
![Screenshot of the list of DNS security policies.](./media/dns-security-policy/policy-list.png)
4544

0 commit comments

Comments
 (0)