Skip to content

Commit ee017e3

Browse files
authored
Merge pull request #304478 from halkazwini/nw-nsgflowlogs
NSG flow logs retirement note
2 parents 125af39 + 5349f7c commit ee017e3

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

includes/network-watcher-nsg-flow-logs-retirement.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,8 +3,8 @@ author: halkazwini
33
ms.author: halkazwini
44
ms.service: azure-network-watcher
55
ms.topic: include
6-
ms.date: 09/26/2024
6+
ms.date: 09/20/2025
77
ms.custom: include file
88
---
99
> [!IMPORTANT]
10-
> On September 30, 2027, network security group (NSG) flow logs will be retired. As part of this retirement, you'll no longer be able to create new NSG flow logs starting June 30, 2025. We recommend [migrating](../articles/network-watcher/nsg-flow-logs-migrate.md) to [virtual network flow logs](../articles/network-watcher/vnet-flow-logs-overview.md), which overcome the limitations of NSG flow logs. After the retirement date, traffic analytics enabled with NSG flow logs will no longer be supported, and existing NSG flow logs resources in your subscriptions will be deleted. However, NSG flow logs records won't be deleted and will continue to follow their respective retention policies. For more information, see the [official announcement](https://azure.microsoft.com/updates/v2/Azure-NSG-flow-logs-Retirement).
10+
> Network security group (NSG) flow logs will be retired on September 30, 2027. After June 30, 2025, you'll no longer be able to create new NSG flow logs. We recommend [migrating](../articles/network-watcher/nsg-flow-logs-migrate.md) to [virtual network flow logs](../articles/network-watcher/vnet-flow-logs-overview.md), which address the limitations of NSG flow logs. After the retirement date, traffic analytics enabled for NSG flow logs will no longer be supported, and existing NSG flow log resources in your subscriptions will be deleted. However, existing NSG flow log records won't be deleted from Azure Storage and will continue to follow their configured retention policies. For more information, see the [official announcement](https://azure.microsoft.com/updates/v2/Azure-NSG-flow-logs-Retirement).

0 commit comments

Comments
 (0)