Support for EnableFlowTraceLogging parameter on Azure Firewall

[jashwanth125]

Preconditions

• No need to upgrade Python SDK or the Python SDK is ready.

Related command

No response

Resource Provider

Microsoft.Network

Description of Feature or Work Requested

Resource Provider
Network (NRP)

Description of Feature or Work Requested
Need to add a new parameter named EnableFatFlowLogging to the base command of creating the Firewall.
az network firewall create -g MyResourceGroup -n MyFirewall --enable-flow-trace-logging true

Only parameter needed is:

enable-flow-trace-logging
Default value is false

No NRP/Swagger change needed
Additional context

Minimum API Version Required

N/A

Swagger PR link / SDK link

N/A

Request Example

No response

Target Date

N/A

PM Contact

Suren.Jamiyanaa@microsoft.com

Engineer Contact

jagangul@microsoft.com

Additional context

No response

[yonzhan]

Thank you for opening this issue, we will look into it.

[github-actions]

Here are some similar issues that might help you. Please check if they can solve your problem.

• Support for EnableFatFlowLogging parameter on Azure Firewall #23325
• Support for EnableUDPLogOptimization parameter on Azure Firewall #23758
• Support for AllowActiveFTP parameter on Azure Firewall #14369
• Support for DNS Proxy on Azure Firewall #13350

---

Possible solution (Extracted from existing issue, might be incorrect; please verify carefully)

Solution 1:

We'll develop it in this sprint.

Reference:

• Support for EnableFatFlowLogging parameter on Azure Firewall #23325 (comment)

Solution 2:

It will be sent to backend as an additional property (Network.AdditionalLogs.EnableFatFlowLogging) like it is done in the above PowerShell PR. Do we still need swagger change? e.g mapping from SDK to PS => {PSFirewallObj}.EnableFatFlowLogging = {SDKFirewallObj}.AdditionalProperties?.SingleOrDefault(kvp => kvp.Key.Equals("Network.AdditionalLogs.EnableFatFlowLogging", StringComparison.OrdinalIgnoreCase)).Value;

Reference:

• Support for EnableFatFlowLogging parameter on Azure Firewall #23325 (comment)

Powered by issue-sentinel