You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/network-watcher/network-watcher-nsg-flow-logging-azure-resource-manager.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -107,11 +107,11 @@ Below are two examples of complete templates to set up NSG Flow Logs.
107
107
```
108
108
109
109
> [!NOTE]
110
-
> * The name of resource has the format "Parent Resource_Child resource". Here, the parent resource is the regional Network Watcher instance (Format: NetworkWatcher_RegionName. Example: NetworkWatcher_centraluseuap)
110
+
> * The name of the resource has the format "Parent Resource_Child resource". Here, the parent resource is the regional Network Watcher instance (Format: NetworkWatcher_RegionName. Example: NetworkWatcher_centraluseuap)
111
111
> * targetResourceId is the resource ID of the target NSG
112
112
> * storageId is the resource ID of the destination storage account
113
113
114
-
**Example 2**: The following templates enabling NSG Flow Logs (version 2) with a retention for 5 days. Enabling Traffic Analytics with a processing interval of 10 minutes.
114
+
**Example 2**: The following templates enable NSG Flow Logs (version 2) with retention for 5 days. Enabling Traffic Analytics with a processing interval of 10 minutes.
Network Security Group flow logs are a feature of Network Watcher that allows you to view information about ingress and egress IP traffic through a Network Security Group. These flow logs are written in JSON format and show outbound and inbound flows on a per rule basis, the NIC the flow applies to, 5-tuple information about the flow (Source/Destination IP, Source/Destination Port, Protocol), and if the traffic was allowed or denied.
23
23
24
-
The detailed specification of all NSG flow log commands for various versions of AzPowerShell can be found [here](/powershell/module/az.network/#network-watcher)
24
+
The detailed specification of all NSG flow logs commands for various versions of AzPowerShell can be found [here](/powershell/module/az.network/#network-watcher)
25
25
26
26
> [!NOTE]
27
27
> - The commands [Get-AzNetworkWatcherFlowLogStatus](/powershell/module/az.network/get-aznetworkwatcherflowlogstatus) and [Set-AzNetworkWatcherConfigFlowLog](/powershell/module/az.network/set-aznetworkwatcherconfigflowlog) used in this doc, requires an additional "reader" permission in the resource group of the network watcher. Also, these commands are old and may soon be deprecated.
Copy file name to clipboardExpand all lines: articles/network-watcher/nsg-flow-logs-policy-portal.md
+14-11Lines changed: 14 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,17 +19,20 @@ ms.author: damendo
19
19
# QuickStart: Deploy and manage NSG Flow Logs using Azure Policy
20
20
21
21
## Overview
22
-
Azure Policy helps to enforce organizational standards and to assess compliance at-scale. Common use cases for Azure Policy include implementing governance for resource consistency, regulatory compliance, security, cost, and management. In this article, we will use two built-in policies available for NSG Flow Logs to manage your flow logs setup. The first policy flags any NSGs without flow logs enabled. The second policy automatically deploys Flow logs for NSGs without Flow logs enabled.
22
+
23
+
Azure Policy helps to enforce organizational standards and to assess compliance at scale. Common use cases for Azure Policy include implementing governance for resource consistency, regulatory compliance, security, cost, and management. In this article, we will use two built-in policies available for NSG Flow Logs to manage your flow logs setup. The first policy flags any NSGs without flow logs enabled. The second policy automatically deploys Flow logs for NSGs without Flow logs enabled.
23
24
24
25
If you are creating an Azure Policy definition for the first time, you can read through:
@@ -95,7 +98,7 @@ If you want to see the full definition of the policy, you can visit the [Definit
95
98
96
99
1. Fill in your policy details
97
100
98
-
- Scope: A subscription is the common choice, you can also choose a management group or resource group as relevant to you.
101
+
- Scope: A subscription is a common choice, you can also choose a management group or resource group as relevant to you.
99
102
- Policy Definition: Should be chosen as shown in the "Locate the policies" section.
100
103
- AssignmentName: Choose a descriptive name
101
104
@@ -104,17 +107,17 @@ If you want to see the full definition of the policy, you can visit the [Definit
104
107
The Network Watcher service is a regional service. These parameters allow the policy action of deploying flow logs to be executed.
105
108
- NSG Region: Azure regions at which the policy is targeted
106
109
- Storage ID: Full resource ID of the storage account. Note: This storage account should be in the same region as the NSG.
107
-
- Network Watchers RG: Name of the resource group containing your Network Watcher resource. If you have not renamed it, you can enter 'NetworkWatcherRG' which is the default.
110
+
- Network Watchers RG: Name of the resource group containing your Network Watcher resource. If you have not renamed it, you can enter `NetworkWatcherRG` which is the default.
108
111
- Network Watcher name: Name of the regional network watcher service. Format: NetworkWatcher_RegionName. Example: NetworkWatcher_centralus. See the full list.
0 commit comments