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
Configure virtual networks to enforce workspace, storage account and retention interval for Flow logs and Traffic Analytics: Needs to assess Microsoft.Network/networkWatchers/flowLogs/provisioningState
#1402
Open
jcetina opened this issue
Nov 22, 2024
· 1 comment
Details of the scenario you tried and the problem that is occurring
Flow logs can fail to provision correctly sometimes (we don't know why - they just do). When provisioning state fails, it is reflected in the JSON representation of the flowLog resource in properties.provisioningState. If this field does not equal Succeeded, then the resource is not correctly provisioned.
Verbose logs showing the problem
This is the only indication of error we get in Activity Logs.
Details of the scenario you tried and the problem that is occurring
Flow logs can fail to provision correctly sometimes (we don't know why - they just do). When provisioning state fails, it is reflected in the JSON representation of the flowLog resource in
properties.provisioningState
. If this field does not equalSucceeded
, then the resource is not correctly provisioned.Verbose logs showing the problem
This is the only indication of error we get in Activity Logs.
Suggested solution to the issue
Include the following check in the existinceCondition within the
allOf
block:If policy is Guest Configuration - details about target node
The text was updated successfully, but these errors were encountered: