Tim B

My feedback

  1. 51 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    8 comments  ·  Virtual Machines  ·  Flag idea as inappropriate…  ·  Admin →
    Tim B supported this idea  · 
    Tim B commented  · 

    I was trying to migrate a system to Azure VMs while we refactor to make necessary changes to run stateless and its a real hard sell to tell my customers they need to quadruple their infrastructure cost because they cant have multiple web applications with web services on a single VM because they cant have more than a single public IP address.

    Because of this I have customers forced to go to AWS and others.

    This is a common setup and while SNI is great for modern browsers its not supported by the vast majority of the people who consume older WCF services so its hard for me to advise people to move to Azure where they lose basic functionality that is everywhere else.

    Until this is resolved I have no choice but to develop for AWS and advise my customers as such for any existing applications not ready for PaaS.

  2. 616 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    23 comments  ·  Cloud Services (Web and Worker Role)  ·  Flag idea as inappropriate…  ·  Admin →

    SSL only requires multiple IPs when the client is on Windows XP, using an older version of Internet Explorer. Most modern browsers support SNI (Server Name Indication) and thus don’t require multiple IPs.

    Support for multiple IPs is under review in the team.

    Tim B supported this idea  · 
    Tim B commented  · 

    I find the answer from Corey Sanders to be inadequate. I am trying to migrate a system to azure and because there is no well documented way to have more than a single IP SSL working with a VM my customers are going with another provider, probably AWS.

    Its a very common setup to have a web server VM with multiple public IP's for SSL purposes because not everything is consumed via a browser and therfore can be fixed with SNI such as the case with my client and their WCF consumers.

    While SNI is great, by ignoring the needs of your potential customers for basic functionality available in other providers and bare metal your only keeping people off your platform.

Feedback and Knowledge Base