-
For outbound traffics from VMs associated with NAT Gateway, NSG Flow logs won't show the correct destination public IP in the logs. While this is due to the internal design of NAT Gateway and it's the…
-
As stated under limitations in the documentation, all node pools have to reside within the samee subnet.
The ask is to support assignment of a unique subnet per node pool in a cluster, but all shar…
-
### Terraform (and AzureRM Provider) Version
hashicorp/azurerm v2.73.0
terraform v0.14.9
### Affected Resource(s)
azurerm_network_watcher_flow_log
### Terraform Configuration Files
```
reso…
-
Hello, This is **breaking our terraform automation to enable the NSG flow logs**. I was going through this https://github.com/hashicorp/terraform-provider-azurerm/blob/485955c183064df242be931543c2039e…
-
### Terraform Version
Terraform v0.14.8
+ provider registry.terraform.io/taliesins/hyperv v1.0.1
### Affected Resource(s)
No resources are being created, terraform is failing on Apply
### Deb…
-
As we are preparing to open up features to community contributions, we found that some features need to install after other features. This issue proposes to add support for soft-dependencies to arrive…
-
This doc contains old information around not being able to automate NSG Flow logs via ARM
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub is…
-
In the scenario where I define a network watcher as per below
```hcl
network_watchers = {
nwaue = {
name = "aue"
resource_group_key = "network"
region = "…
-
Upon troubleshooting, it has been discovered that the Logstash code on the Azure document has an error. There appears to be a " }} " as opposed to " ]} " at the end of the " operationName " and " Vers…
-
This log doesn't appear to be available any more:
NetworkSecurityGroupFlowEvent
I assume that flow logs have to use Network Watcher and can't be directly enabled through diagnostic settings. Pleas…