DeborahDavidson-0683 avatar image
0 Votes"
DeborahDavidson-0683 asked ChristopherW-MSFT commented

are static domains, ports and TCP/IPv4 supported for a client/server app?

I have a client server app that needs a specific file folder structure, and a defined domain name/ IP address and port. It requires IP version 4. Is this possible to configure on Azure Cloud?

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

1 Answer

ChristopherW-MSFT avatar image
0 Votes"
ChristopherW-MSFT answered ChristopherW-MSFT commented

Hi @DeborahDavidson-0683 ,

These are all supported through Virtual Machines. If you're setting up the Server on a Windows or Linux Virtual Machine, you're free to set the folder structure however you need - If it's IIS then you'll bind the Private IP and Domain to that folder. Otherwise if the Server app is listening to a specific port without IIS binding, you'll just need to make sure Ports are open through the Network Security Group + OS Firewall.

We currently don't allow purchasing a specific IP Address, only regional ranges, but you can set the assignment to 'Static' when you create a Public IP to make sure it never changes. You can also create a Domain through 'App Service Domain', or any other Domain service and set the A Record as the IP, or Virtual Machine's DNS Name as a CNAME.

Here's our general guidelines on Azure Virtual Machines:

Azure App Services, which is a PaaS offering, can support most of these except for Port Mapping.

Let me know if there's specific architecture you need!

· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Thank you. Are you saying that the I can't set a static port in the configuration?
It doesn't matter what IP address and port are used as long as they can be set to static so they won't change once the software is configured and the server is started.

0 Votes 0 ·

Yeah that should be fine - It really depends on what the application is and if it requires specific IIS or other service setup. But if the server application doesn't need IIS binding, then it might just take it's own Port. You can check which port it's listening on with Command Prompt > Netstat, or use Windows Resource Monitor > Networking to find the app and listening port.

The Listening Port will be determined by the application itself, and as long as nothing else is trying to overtake that port, you should be fine and it wouldn't change. If it just needs HTTP/S 80 or 443 Ports, you can bind the web application to those normally, or change them to your requirements in Windows. You can also use a Load Balancer to re-route them by their Front-End to Back-End Ports if needed.

I'd say set it up in a small test environment to see if there any gaps in your setup, then move forward with re-configuring them if necessary.

0 Votes 0 ·