Not able to tick the checkbox "Enable traffic analytics" in the Flow log settings page

@Oruganti, Sudhamayi ,

Welcome to the Microsoft Q&A Platform. Thank you for reaching out & I hope you are doing well.

• It is possible that you are lacking the necessary permission to do so
  • To check, navigate to the NetworkWatcher_<YOURREGION> under Network Watcher and go to IAM
  • Under "Check Access", select "View my access" and share your role
• Are you using a Preview Portal?
  • If so, try using normal portal : https://portal.azure.com/?preview=no
  • If not, try using preview portal : https://portal.azure.com/?preview=yes#home
• You can also try using Azure Powershell :
  • This will get the Flow Log and while we Set, will not enable Traffic Analytics
  • See : Change a flow log

# Place the network security group properties into a variable.
$nsg = Get-AzNetworkSecurityGroup -Name 'myNSG' -ResourceGroupName 'myResourceGroup'

# Place the storage account properties into a variable.
$sa = Get-AzStorageAccount -Name 'myStorageAccount' -ResourceGroupName 'myResourceGroup'

# Update the NSG flow log.
Set-AzNetworkWatcherFlowLog -Name 'myFlowLog' -Location 'eastus' -TargetResourceId $nsg.Id -StorageId $sa.Id -Enabled $true -FormatVersion 2

Cheers,

Kapil

hi Kapil, Thanks for the response.

It's not access issue as I have sufficient privileges to do the update. Perhaps the powershell works but I see javascript error on the page when I click on the checkbox. It needs fixing.

@Oruganti, Sudhamayi ,

Thanks for the info.

However, I was not able to replicate this issue.

• From which region are you accessing the Azure Portal?
• Is it possible for you to try and repo this from a different region
  • You can try to do the same from a VM which is in a different region
• Do you have a different user testing this and able to repo?
• Is this issue happening with only a particular flow log (NSG) ?
• Or all the flow logs?

Cheers,

Kapil

hi Kapil,

I'm accessing the portal from India. Same problem exists with user accessing from a different region also.

The issue is not specific to one NSG/flow log but interestingly we noticed that it is happening only in one tenant.