Hello @piyush shailly ,
I understand that you are trying to connect 2 different GCP VPC to one Azure VPN gateway and only one connection is getting active at one time.
You were using active-active enabled Route based VPNGW1 SKU Azure VPN gateway and were connecting the 2 different GCP VPCs to Azure using 2 different GCP gateways.
You were not using custom policies. You were using APIPA addresses for BGP. There were no address space overlaps between Azure Vnet and the 2 GCP VPC that you are trying to connect to but still one of your connections was active and another was down in GCP with its showing BGP: waiting for peers. On Azure side, it was showing Connected.
I advised you to refer the below doc which shows a similar setup but between Azure and AWS as it will help you in validating the configuration.
https://learn.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-howto-aws-bgp
Some other helpful references:
Following the below doc, you were able to resolve your issue:
https://learn.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-howto-aws-bgp
Kindly let us know if the above helps or you need further assistance on this issue.
Please "Accept the answer" if the information helped you. This will help us and others in the community as well.