I have a problem connecting my Azure AppService to a new subnet created. My AppService is upgraded to PremiumV2 plan. When trying to setup subnet via VNet Integration I can see the VNet as well as newly created Subnet in selection drop down, but getting an error
The request timed out. Diagnostic information: timestamp 'xxxxx', subscription id '', tracking id 'xxxxx', request correlation id 'xxxxx'.
If I change my AppService plan to another PremiumV2 everything works fine (newly created subnet has no other applications using it). Maybe someone has any ideas what could be wrong since I looked at limitations defined by Microsoft and there should be no problem with those.