Skip to content

Commit a9c3489

Browse files
committed
move tip
1 parent e14231d commit a9c3489

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/firewall/firewall-preview.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -161,9 +161,6 @@ Policy analytics starts monitoring the flows in the DNAT, Network, and Applicati
161161
6. Go to the Firewall attached to the policy and enter the **Diagnostic settings** page. You'll see the **FirewallPolicySetting** added there as part of the policy analytics feature.
162162
7. Select **Edit Setting**, and ensure the **Resource specific** toggle is checked, and the highlighted tables are checked. In the previous example, all logs are written to the log analytics workspace.
163163

164-
> [!TIP]
165-
> Policy Analytics has a dependency on both Log Analytics and Azure Firewall resource specific logging. Verify the Firewall is configured appropriately or follow the previous instructions. Be aware that logs take 60 minutes to appear after enabling them for the first time. This is because logs are aggregated in the backend every hour. You can check logs are configured appropriately by running a log analytics query on the resource specific tables such as **AZFWNetworkRuleAggregation**, **AZFWApplicationRuleAggregation**, and **AZFWNatRuleAggregation**.
166-
167164
#### Firewall with Diagnostics settings already configured
168165

169166
1. Ensure that the Firewall attached to the policy is logging to **Resource Specific** tables, and that the following three tables are also selected:
@@ -179,6 +176,9 @@ Policy analytics starts monitoring the flows in the DNAT, Network, and Applicati
179176

180177
You can disregard this error message if the policy was successfully updated.
181178

179+
> [!TIP]
180+
> Policy Analytics has a dependency on both Log Analytics and Azure Firewall resource specific logging. Verify the Firewall is configured appropriately or follow the previous instructions. Be aware that logs take 60 minutes to appear after enabling them for the first time. This is because logs are aggregated in the backend every hour. You can check logs are configured appropriately by running a log analytics query on the resource specific tables such as **AZFWNetworkRuleAggregation**, **AZFWApplicationRuleAggregation**, and **AZFWNatRuleAggregation**.
181+
182182
## Next steps
183183

184184
To learn more about Azure Firewall, see [What is Azure Firewall?](overview.md).

0 commit comments

Comments
 (0)