17 comments

Add a comment…

Sign in

prestine

Your email address

Check!

invalid email

(thinking…)

Reset

or sign in with

• 
• 

UserVoice password

Forgot password?

Create a password

Your name

I agree to the terms of service

You'll receive a confirmation email with a link to create a password (optional).

Signed in as (Sign out)

Close

Close

Post comment Submitting...

• Omri Gazitt commented  ·  October 31, 2011  ·  Flag as inappropriate  ·  Delete

  From a private communication... it now appears that as long as you don't delete a deployment, Azure will preserve VIP addresses (and considers any VIP address change to be a bug). Awaiting public confirmation :-)

• Omri Gazitt commented  ·  October 26, 2011  ·  Flag as inappropriate  ·  Delete

  +1 to this feature request.

  I have the exact scenario that Joe A described below... see the URL below for more details.

  http://social.msdn.microsoft.com/Forums/en-US/windowsazuredevelopment/thread/779d8ade-d212-4a3c-80cd-3c5748da1b72/

• Joe Albahari commented  ·  September 16, 2011  ·  Flag as inappropriate  ·  Delete

  I agree that elastic IPs are necessary to use http://domain.com as your primary URL instead of http://www.domain.com. This is because the former requires a cname on a second-level domain which conflicts with MX records

• Gregory Katz commented  ·  July 01, 2011  ·  Flag as inappropriate  ·  Delete

  I have a specific e-prescribe provider who uses IP based authentication and takes at least 2 weeks to change the setting.

• Stephen Goss commented  ·  March 29, 2011  ·  Flag as inappropriate  ·  Delete

  We go to third parties who impose IP based authentication. We need more stability in the IP address than the suggestion of not deleting the service. These IP authentications can take many weeks to set up with the larger corporates. The consequences of accidentally deleting the service and losing the IP are too serious.

• Lucian Daia commented  ·  February 06, 2011  ·  Flag as inappropriate  ·  Delete

  This feature is vital for us. We're trying to move a travel app into Windows Azure and we have lots of providers that authenticate based on IP. Reassigning a new IP to us could take a few days, during which we would basically have to rely on cached data (not an option for so long) or just take down the website. Elastic IPs would be a life-saver and would prevent us from going to Amazon.

• Brian commented  ·  January 05, 2011  ·  Flag as inappropriate  ·  Delete

  We depend on third party services that require that requests come from an IP address that they white list. It can take several days for the vendor to add new ip addresses to the white list.Thus, a change in our Azure IP address would bring down our service completely for up to several days. It's hard to imagine a serious commercial venture operating with that level of risk, particularly when key competitors (AWS) have had this feature for years.

• Jonas commented  ·  November 05, 2010  ·  Flag as inappropriate  ·  Delete

  No news at PDC 2010 for this? I would have expected at least an announcement for CY 2011. Nothing at all means I will have to recommend Amazon Web Services to our customers in certain scenarios.

• Chris Auld commented  ·  June 29, 2010  ·  Flag as inappropriate  ·  Delete

  Hi there. You have elastic IPs already unless you go and delete your deployment.
  The only time this is necessary (off the top of my head) is when you change the external end-points in the service definition. Everything else should be handled just fine with either an in-place upgrade or a VIP swap.

  To put it more simply. Once you create your deployment it will have a fixed IP that resolves to the load balancer for your service until that deployment is deleted.

  See my detailed answer in this thread
  http://social.msdn.microsoft.com/Forums/en-US/windowsazure/thread/fa00d06d-b631-46ce-af66-f463cf667282?prof=required

  To be honest I don`t think that the edge case of deleted services is sufficiently common to justify a bunch of effort on this feature

• Martin Wawrusch commented  ·  June 07, 2010  ·  Flag as inappropriate  ·  Delete

  This is a showstopper for us. We cannot migrate to Azure without the ability to resolve http://mydomain.com.

• filsinn commented  ·  April 16, 2010  ·  Flag as inappropriate  ·  Delete

  we consume in a webapp some services from another provider, who has ip-based authentication. this is a keyfeature of our webapp, unfortunatly we can not migrate to azure because of this.

• Rob Pinna commented  ·  March 13, 2010  ·  Flag as inappropriate  ·  Delete

  This issue is pushing us to choose Amazon even though we're an entirely Microsoft shop.

• Tim Hardy commented  ·  February 24, 2010  ·  Flag as inappropriate  ·  Delete

  I need elastic IPs in order to map a wildcard to my domain - *.mydomain.com. I need this for multi-tenant portal functionality where <tenantgeneratedcode>.mydomain.com must map to my app via DNS.

  I need this soon :)

• Andy Green commented  ·  January 22, 2010  ·  Flag as inappropriate  ·  Delete

  This one is a biggie for me as well; SEO issues are a big one with our site, so having some kind of plan for handling this is majorly important for some sites.

• mxrss commented  ·  December 17, 2009  ·  Flag as inappropriate  ·  Delete

  agreed you can always create DNS Aliases and be Fine.

• MakerOfThings77 commented  ·  December 07, 2009  ·  Flag as inappropriate  ·  Delete

  Depending on your needs, and who your DNS provider you may have issues, or SEO issues with that solution. See this link for more info:
  http://social.msdn.microsoft.com/Forums/en-US/windowsazure/thread/29d7ad54-f8c0-4ef1-a38c-3dfa975a6152

  Try using a SOAP webservice to update your IP address when your system boots up. Some examples here:

  http://social.msdn.microsoft.com/Forums/en-US/windowsazure/thread/c6ee0cf8-c5e0-46c6-a6d3-34a9b58dfb91

• Dennis commented  ·  November 25, 2009  ·  Flag as inappropriate  ·  Delete

  Have you seen this? http://blog.smarx.com/posts/custom-domain-names-in-windows-azure I've set up my azure apps that way and it works great.