Forum Discussion
App Service with another port e.g 4443
Hello everyone,
I am migrating from my VM server to Azure. When the website is running with my VM server, it is host in port 4443 but when I host the website under Azure app service, there is no option to use that port. My company does not want end users to change the url to access the website so I must find the option to use the port 4443 under Azure app service or make the redirect from port 4443 to 443.
Anyone please help me with this.
Thank you very much in advance.
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.
- hspinto
Microsoft
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.
Thank you very much for this but it seems that I need 2 different domains for Application Gateway and App Service. Is it correct? And can i use the same domain for both Application Gateway and App Service?
Thanks.
- hspinto
Hello, KenNguyen11031987!
Your users will come to your app through Application Gateway (AppGw). Therefore, you will need to associate a custom domain only to AppGw. This will in turn forward requests to your Web App through its default *.azurewebsites.net domain. You don't need to associate your domain also to the Web App (though possible to do), as it is never exposed directly to the end user - it exchanges traffic only with AppGw.
