vnet peering det disconnected when changing a backend pool in app gw

[neidiom]

I paired two vnets. One is where my Application Gateway is. Everytime I change something, like adding a new ip to the backend pool, the vnet peering breaks. Here is the error message.

* azurerm_virtual_network_peering.vnet_peer_2_ned_app_gw_vnet: 1 error(s) occurred:

* azurerm_virtual_network_peering.vnet_peer_2_xxx_app_gw_vnet: Error Creating/Updating Virtual Network Peering "peer_xxx_app_gw_vnet_to_xxx_xxx_vnet" (Network "xxxxs-vnet-12345" / Resource Group "xx-xx-west-test-xxxx-application-gateway-rg"): network.VirtualNetworkPeeringsClient#CreateOrUpdate: Failure sending request: StatusCode=400 -- Original Error: Code="RemotePeeringIsDisconnected" Message="Cannot create or update peering /subscriptions/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx/resourceGroups/xx-xx-west-test-xxxx-application-gateway-rg/providers/Microsoft.Network/virtualNetworks/xxxxs-vnet-12345/virtualNetworkPeerings/peer_xxx_app_gw_vnet_to_xxx_xxx_vnet because remote peering /subscriptions/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx/resourceGroups/xx-xx-netrg/providers/Microsoft.Network/virtualNetworks/xx-xx-vnet/virtualNetworkPeerings/peer_xxx_xxx_vnet_to_xxx_app_gw_vnet referencing parent virtual network /subscriptions/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx/resourceGroups/xx-xx-west-test-xxxx-application-gateway-rg/providers/Microsoft.Network/virtualNetworks/xxxxs-vnet-12345 is in Disconnected state. Update or re-create the remote peering to get it back to Initiated state. Peering gets Disconnected when remote vnet or remote peering is deleted and re-created." Details=[]

[ghost]

This issue has been automatically migrated to hashicorp/terraform-provider-azurerm#1274 because it looks like an issue with that provider. If you believe this is not an issue with the provider, please reply to hashicorp/terraform-provider-azurerm#1274.

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.