Skip to content

Commit 1779c55

Browse files
author
Jill Grant
authored
Merge pull request #277856 from AbdullahBell/firewall-diagram-lightbox-update
Firewall: Update: Add lightbox to all diagrams
2 parents 9d64e4e + 2479b74 commit 1779c55

12 files changed

+16
-16
lines changed

articles/firewall/deploy-ps-policy.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ For more information about Azure Bastion, see [What is Azure Bastion?](../bastio
3333
> [!IMPORTANT]
3434
> [!INCLUDE [Pricing](~/reusable-content/ce-skilling/azure/includes/bastion-pricing.md)]
3535
36-
![Tutorial network infrastructure](media/deploy-ps/tutorial-network.png)
36+
:::image type="content" source="media/deploy-ps/tutorial-network.png" alt-text="Diagram that shows a firewall network infrastructure." lightbox="media/deploy-ps/tutorial-network.png":::
3737

3838
In this article, you learn how to:
3939

articles/firewall/deploy-ps.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ For more information about Azure Bastion, see [What is Azure Bastion?](../bastio
3333
> [!IMPORTANT]
3434
> [!INCLUDE [Pricing](~/reusable-content/ce-skilling/azure/includes/bastion-pricing.md)]
3535
36-
![Tutorial network infrastructure](media/deploy-ps/tutorial-network.png)
36+
:::image type="content" source="media/deploy-ps/tutorial-network.png" alt-text="Diagram that shows a firewall network infrastructure." lightbox="media/deploy-ps/tutorial-network.png":::
3737

3838
In this article, you learn how to:
3939

articles/firewall/firewall-sftp.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ ms.custom: devx-track-azurepowershell
1414

1515
You can use Azure Firewall to access a storage account container via SFTP. Azure PowerShell is used to deploy a firewall in a virtual network and configured with DNAT rules to translate the SFTP traffic to the storage account container. The storage account container is configured with a private endpoint to allow access from the firewall. To connect to the container, you use the firewall public IP address and the storage account container name.
1616

17-
:::image type="content" source="media/firewall-sftp/accessing-storage-using-sftp.png" alt-text="Diagram showing SFTP to firewall to access a storage account container.":::
17+
:::image type="content" source="media/firewall-sftp/accessing-storage-using-sftp.png" alt-text="Diagram showing SFTP to firewall to access a storage account container." lightbox="media/firewall-sftp/accessing-storage-using-sftp.png":::
1818

1919
In this article, you:
2020

articles/firewall/premium-deploy.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ You'll use a template to deploy a test environment that has a central VNet (10.0
3131
3232
A single central VNet is used in this test environment for simplicity. For production purposes, a [hub and spoke topology](/azure/architecture/reference-architectures/hybrid-networking/hub-spoke) with peered VNets is more common.
3333

34-
:::image type="content" source="media/premium-deploy/premium-topology.png" alt-text="Central VNet topology":::
34+
:::image type="content" source="media/premium-deploy/premium-topology.png" alt-text="Diagram of Central VNet topology." lightbox="media/premium-deploy/premium-topology.png":::
3535

3636
The worker virtual machine is a client that sends HTTP/S requests through the firewall.
3737

@@ -139,8 +139,8 @@ Use the following steps to test TLS Inspection with URL filtering.
139139

140140
Some HTML pages may look incomplete because they refer to other URLs that are denied. To solve this issue, the following approach can be taken:
141141

142-
- If the HTML page contain links to other domains, you can add these domains to a new application rule with allow access to these FQDNs.
143-
- If the HTML page contain links to sub URLs then you can modify the rule and add an asterisk to the URL. For example: `targetURLs=www.nytimes.com/section/world*`
142+
- If the HTML page contains links to other domains, you can add these domains to a new application rule with allow access to these FQDNs.
143+
- If the HTML page contains links to sub URLs then you can modify the rule and add an asterisk to the URL. For example: `targetURLs=www.nytimes.com/section/world*`
144144

145145
Alternatively, you can add a new URL to the rule. For example:
146146

@@ -163,4 +163,4 @@ Let's create an application rule to allow access to sports web sites.
163163
## Next steps
164164

165165
- [Building a POC for TLS inspection in Azure Firewall](https://techcommunity.microsoft.com/t5/azure-network-security-blog/building-a-poc-for-tls-inspection-in-azure-firewall/ba-p/3676723)
166-
- [Azure Firewall Premium in the Azure portal](premium-portal.md)
166+
- [Azure Firewall Premium in the Azure portal](premium-portal.md)

articles/firewall/quick-create-multiple-ip-bicep.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ ms.date: 10/19/2023
1414

1515
In this quickstart, you use a Bicep file to deploy an Azure Firewall with multiple public IP addresses from a public IP address prefix. The deployed firewall has NAT rule collection rules that allow RDP connections to two Windows Server 2019 virtual machines.
1616

17-
:::image type="content" source="media/quick-create-multiple-ip-bicep/azure-firewall-multiple-ip.png" alt-text="Diagram showing the network configuration for this quickstart.":::
17+
:::image type="content" source="media/quick-create-multiple-ip-bicep/azure-firewall-multiple-ip.png" alt-text="Diagram showing the network configuration for this quickstart." lightbox="media/quick-create-multiple-ip-bicep/azure-firewall-multiple-ip.png":::
1818

1919

2020
[!INCLUDE [About Bicep](~/reusable-content/ce-skilling/azure/includes/resource-manager-quickstart-bicep-introduction.md)]

articles/firewall/quick-create-multiple-ip-template.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ ms.author: victorh
1414

1515
In this quickstart, you use an Azure Resource Manager template (ARM template) to deploy an Azure Firewall with multiple public IP addresses from a public IP address prefix. The deployed firewall has NAT rule collection rules that allow RDP connections to two Windows Server 2019 virtual machines.
1616

17-
:::image type="content" source="media/quick-create-multiple-ip-bicep/azure-firewall-multiple-ip.png" alt-text="Diagram showing the network configuration for this quickstart.":::
17+
:::image type="content" source="media/quick-create-multiple-ip-bicep/azure-firewall-multiple-ip.png" alt-text="Diagram showing the network configuration for this quickstart." lightbox="media/quick-create-multiple-ip-bicep/azure-firewall-multiple-ip.png":::
1818

1919
[!INCLUDE [About Azure Resource Manager](~/reusable-content/ce-skilling/azure/includes/resource-manager-quickstart-introduction.md)]
2020

articles/firewall/tutorial-firewall-deploy-portal-policy.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ For this tutorial, you create a simplified single VNet with two subnets for easy
2727
* **AzureFirewallSubnet** - the firewall is in this subnet.
2828
* **Workload-SN** - the workload server is in this subnet. This subnet's network traffic goes through the firewall.
2929

30-
![Tutorial network infrastructure](media/tutorial-firewall-deploy-portal/tutorial-network.png)
30+
:::image type="content" source="media/tutorial-firewall-deploy-portal/tutorial-network.png" alt-text="Diagram of Firewall network infrastructure." lightbox="media/tutorial-firewall-deploy-portal/tutorial-network.png":::
3131

3232
For production deployments, a [hub and spoke model](/azure/architecture/reference-architectures/hybrid-networking/hub-spoke) is recommended, where the firewall is in its own VNet. The workload servers are in peered VNets in the same region with one or more subnets.
3333

articles/firewall/tutorial-firewall-deploy-portal.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ For production deployments, a [hub and spoke model](/azure/architecture/referenc
2929
* **AzureFirewallSubnet** - the firewall is in this subnet.
3030
* **Workload-SN** - the workload server is in this subnet. This subnet's network traffic goes through the firewall.
3131

32-
![Network infrastructure](media/tutorial-firewall-deploy-portal/tutorial-network.png)
32+
:::image type="content" source="media/tutorial-firewall-deploy-portal/tutorial-network.png" alt-text="Diagram of Firewall network infrastructure." lightbox="media/tutorial-firewall-deploy-portal/tutorial-network.png":::
3333

3434
In this article, you learn how to:
3535

articles/firewall/tutorial-hybrid-portal-policy.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ For this tutorial, you create three virtual networks:
2222
- **VNet-Spoke** - the spoke virtual network represents the workload located on Azure.
2323
- **VNet-Onprem** - The on-premises virtual network represents an on-premises network. In an actual deployment, it can be connected by either a VPN or ExpressRoute connection. For simplicity, this tutorial uses a VPN gateway connection, and an Azure-located virtual network is used to represent an on-premises network.
2424

25-
![Firewall in a hybrid network](media/tutorial-hybrid-ps/hybrid-network-firewall.png)
25+
:::image type="content" source="media/tutorial-hybrid-ps/hybrid-network-firewall.png" alt-text="Diagram of Firewall in a hybrid network." lightbox="media/tutorial-hybrid-ps/hybrid-network-firewall.png":::
2626

2727
In this tutorial, you learn how to:
2828

@@ -241,7 +241,7 @@ In this step, you create the connection from the hub virtual network to the on-p
241241
1. Open the **FW-Hybrid-Test** resource group and select the **GW-hub** gateway.
242242
2. Select **Connections** in the left column.
243243
3. Select **Add**.
244-
4. The the connection name, type **Hub-to-Onprem**.
244+
4. For the connection name, type **Hub-to-Onprem**.
245245
5. Select **VNet-to-VNet** for **Connection type**.
246246
6. For the **Second virtual network gateway**, select **GW-Onprem**.
247247
7. For **Shared key (PSK)**, type **AzureA1b2C3**.

articles/firewall/tutorial-hybrid-portal.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ For this article, you create three virtual networks:
2222
- **VNet-Spoke**: The spoke virtual network represents the workload located on Azure.
2323
- **VNet-Onprem**: The on-premises virtual network represents an on-premises network. In an actual deployment, you can connect to it by using either a virtual private network (VPN) connection or an Azure ExpressRoute connection. For simplicity, this article uses a VPN gateway connection, and an Azure-located virtual network represents an on-premises network.
2424

25-
![Diagram that shows a firewall in a hybrid network.](media/tutorial-hybrid-ps/hybrid-network-firewall.png)
25+
:::image type="content" source="media/tutorial-hybrid-ps/hybrid-network-firewall.png" alt-text="Diagram that shows a firewall in a hybrid network." lightbox="media/tutorial-hybrid-ps/hybrid-network-firewall.png":::
2626

2727
If you want to use Azure PowerShell instead to complete the procedures in this article, see [Deploy and configure Azure Firewall in a hybrid network by using Azure PowerShell](tutorial-hybrid-ps.md).
2828

0 commit comments

Comments
 (0)