From 860584b16e47c8187ad814340e5be16a010cd39d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Dawid=20Stefa=C5=84ski?=
 <141818369+stefanskid@users.noreply.github.com>
Date: Mon, 16 Dec 2024 14:38:06 +0100
Subject: [PATCH] Update README.md

---
 examples/common_cloudngfw/README.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/examples/common_cloudngfw/README.md b/examples/common_cloudngfw/README.md
index 8c9edb5..2b6f440 100644
--- a/examples/common_cloudngfw/README.md
+++ b/examples/common_cloudngfw/README.md
@@ -26,6 +26,8 @@ This design uses a Transit VNet. Application functions and resources are deploye
 a hub-and-spoke topology. The hub of the topology, or transit VNet, is the central point of connectivity for all inbound,
 outbound, east-west, and enterprise traffic. You integrate CNGFW with the transit VNet. Please see the [CNGFW design guide](https://www.paloaltonetworks.com/apps/pan/public/downloadResource?pagePath=/content/pan/en_US/resources/guides/securing-apps-with-cloud-ngfw-for-azure-design-guide).
 
+![Azure NGFW hub README diagrams - cngfw_vnet (1)](https://github.com/user-attachments/assets/6e82efa3-b1a9-4570-87d7-42076117d6b8)
+
 This reference architecture consists of:
 
 - a VNET containing: