Skip to content

Commit 60ea90e

Browse files
Merge pull request #278330 from vhorne/fw-basic-fresh
freshness review
2 parents 8465fae + 705d4c2 commit 60ea90e

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

articles/firewall/basic-features.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -5,13 +5,13 @@ services: firewall
55
author: vhorne
66
ms.service: firewall
77
ms.topic: conceptual
8-
ms.date: 03/15/2023
8+
ms.date: 06/14/2024
99
ms.author: victorh
1010
---
1111

1212
# Azure Firewall Basic features
1313

14-
[Azure Firewall](overview.md) Basic is a managed, cloud-based network security service that protects your Azure Virtual Network resources.
14+
[Azure Firewall Basic](overview.md#azure-firewall-basic) is a managed, cloud-based network security service that protects your Azure Virtual Network resources.
1515

1616
:::image type="content" source="media/overview/firewall-basic-diagram.png" alt-text="Diagram showing Firewall Basic.":::
1717

@@ -29,7 +29,7 @@ Azure Firewall Basic includes the following features:
2929
- Azure Monitor logging
3030
- Certifications
3131

32-
To compare Azure Firewall features for all Firewall SKUs, see [Choose the right Azure Firewall SKU to meet your needs](choose-firewall-sku.md).
32+
To compare Azure Firewall features for all Firewall versions, see [Choose the right Azure Firewall version to meet your needs](choose-firewall-sku.md).
3333

3434
## Built-in high availability
3535

@@ -45,7 +45,7 @@ Azure Firewall Availability Zones are available in regions that support Availabi
4545

4646
## Application FQDN filtering rules
4747

48-
You can limit outbound HTTP/S traffic or Azure SQL traffic to a specified list of fully qualified domain names (FQDN) including wild cards. This feature doesn't require TLS termination.
48+
You can limit outbound HTTP/S traffic or Azure SQL traffic to a specified list of fully qualified domain names (FQDN) including wild cards. This feature doesn't require Transport Layer Security (TLS) termination.
4949

5050
The following video shows how to create an application rule: <br><br>
5151

@@ -87,7 +87,7 @@ Inbound Internet network traffic to your firewall public IP address is translate
8787

8888
You can associate [multiple public IP addresses](deploy-multi-public-ip-powershell.md) with your firewall.
8989

90-
This enables the following scenarios:
90+
Multiple public IP addresses enable the following scenarios:
9191

9292
- DNAT - You can translate multiple standard port instances to your backend servers. For example, if you have two public IP addresses, you can translate TCP port 3389 (RDP) for both IP addresses.
9393
- SNAT - More ports are available for outbound SNAT connections, reducing the potential for SNAT port exhaustion. At this time, Azure Firewall randomly selects the source public IP address to use for a connection. If you have any downstream filtering on your network, you need to allow all public IP addresses associated with your firewall. Consider using a [public IP address prefix](../virtual-network/ip-services/public-ip-address-prefix.md) to simplify this configuration.

0 commit comments

Comments
 (0)