Forum Discussion
App Service with another port e.g 4443
KenNguyen11031987, you cannot use ports other than 80 or 443 to get Internet inbound traffic with App Services. See details here. However, you can put an Application Gateway in front of the App Service and use whatever port you want (up to 65199) in the Application Gateway listener, which will then forward traffic to the App Service. With Application Gateway, you can also benefit from SSL termination, Web Application Firewall, URL-based routing and much more.
Can anybody show in detail how such an application gateway should be set up?
I had this working with Application Gateway V1
However migrating/creating an Application Gateway V2 fails for me.
My initial attempts failed on some obscure certificate issue.
When setting up with rounting/rules/settings without https I get the error below
The client with object id '661935d5-bf36-43bb-8614-eb0dc2558119' does not have authorization
to perform action 'Microsoft.Network/virtualNetworks/subnets/join/action'
over scope '/subscriptions/70dce68d-6522-4cd4-997e-a39b617f4c68/resourceGroups/SecLicenseServer/providers/Microsoft.Network/virtualNetworks/SecLicenseServerVNET2/subnets/default'
or the scope is invalid.
For details on the required permissions, please visit 'https://aka.ms/appgwroles'.
If access was recently granted, please refresh your credentials. Click here for details
Note: I created a new AppGW V2 with a new public IP without deleting my V1 GW