Skip to content

Commit 2eadd67

Browse files
committed
update the title metadata
1 parent fd7842a commit 2eadd67

File tree

2 files changed

+4
-4
lines changed

2 files changed

+4
-4
lines changed

articles/network-watcher/quickstart-configure-network-security-group-flow-logs-from-arm-template.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
---
2-
title: 'Quickstart: Configure network security group flow logs by using an Azure Resource Manager template (ARM template)'
2+
title: 'Quickstart: Configure Network Watcher network security group flow logs by using an Azure Resource Manager template (ARM template)'
33
description: Learn how to enable network security group (NSG) flow logs programmatically by using an Azure Resource Manager template (ARM template) and Azure PowerShell.
44
services: network-watcher
55
author: damendo
66
ms.author: damendo
7-
ms.date: 08/26/2022
7+
ms.date: 09/01/2022
88
ms.topic: quickstart
99
ms.service: network-watcher
1010
ms.custom: devx-track-azurepowershell, subject-armqs, mode-arm

articles/network-watcher/quickstart-configure-network-security-group-flow-logs-from-bicep.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: 'Quickstart: Configure network security group flow logs by using a Bicep file'
2+
title: 'Quickstart: Configure Network Watcher network security group flow logs by using a Bicep file'
33
description: Learn how to enable network security group (NSG) flow logs programmatically by using Bicep and Azure PowerShell.
44
services: network-watcher
55
author: damendo
@@ -39,7 +39,7 @@ The highlighted code in the preceding sample shows an NSG flow resource definiti
3939

4040
## Deploy the Bicep file
4141

42-
This tutorial assumes that you have an network security group that you can enable flow logging on.
42+
This tutorial assumes that you have a network security group that you can enable flow logging on.
4343

4444
1. Save the Bicep file as **main.bicep** to your local computer.
4545
1. Deploy the Bicep file using either Azure CLI or Azure PowerShell.

0 commit comments

Comments
 (0)