Load Balancer and Public IP SKU.
There must be an option of Upgrading Public IP SKU from Basic to Standard without losing Static PIP as it is a creating a big road block when we do any planning like moving existing PIP behind any NVA Standard Load balancer.
If any existing Production Server are already running on Basic PIP then it is very tough to make any decisions to upgrade SKU or move it behind any Standard ELB.
Need suggestion here how and till what time we can overcome here.
Rohit Kumar
shared this idea
Thank you for the feedback. We are working on prereqs to make this possible. Not in scope for CY2019.
— Christian
30 comments
-
Jari Turkia
commented
What!
You cannot change public IP address SKU!!!?At the time I created those addresses, no SKU choice was available and now you cannot change it? Is this for real or are these guys just joking?
-
Vipin Yadav
commented
Really surprised by MS's approach on this issue. Its stand still since more than an year and there r so many clients like us who are impacted by this.
-
Anonymous
commented
See that its in the backlog (although the status hasn't changed to planned in the last year). Would be good for a Rough ETA, this restriction has a significant impact to our business and infrastructure planning
-
Richard
commented
Is there a solutions to this problem yet?
We have come across the same issue. Is there anyway I can keep my IP -
Simon
commented
allow us to change the sku without losing the IP !
as usual, always disapointed with Microsoft -
Elan Shudnow commented
Would be a great feature as I know a lot of people who get bit by this problem. Definitely needs to be an option to upgrade from basic to standard SKU.
-
Daniel Smith
commented
Hello.> So today this bit us across 8 regions and more than 20 LB's since we are using a GLOBAL Peer.
this is really poor implementation MSFT - please provide a solution, as this now means about 3 weeks repeated work for our staff..
-
Uncharted
commented
no.....
we designed our entire production (public ip and LB) with basic SKU, and just realized the basic SKU doesnt have SLA and we cannot simply move from basic to standard.
We have shared our IP to all our clients...
when is this going to be released?
-
Cristiano
commented
We have the same problem, We want to upgrade our services, and we need to reuse same IP, upgrading load balancer. I cannot believe this feature being so complex to realize!
-
Anonymous
commented
We have multiple ipaddresses whitelisted with other businesses API's. We really want top upgrade our infrastructure to use standard loadbalancer's availability zones and V2 Application Gateways. But this limitation blocks us as there is a significant monitary and engineering costs which will impact if we cannot reutilise/upgrade our existing ipaddresses.
Is there any movement on the status of this issue?
-
Blake
commented
We setup aks and now realized that we can't do much with the networking at all, we need a way to convert basic to standard without having to rebuild the entire thing.
-
Lalitha Nochili
commented
This restriction is not documented in the Azure DOCs. AZ CLI for public-IP command with "Update" action does show --SKU as valid parameter. The HELP for public-ip can be updated accordingly
-
Richard Jones
commented
This is really needed, its a basic function to be able to keep a RIPE address when moving from Basic to Std.
Any news on a resolution? -
Arlindo
commented
I have the same problem, I can't lose my basic pre-configured IP and must use load Balancing
-
Dennis George
commented
This is a basic functionality that is expected from an enterprise cloud solution.
-
[Deleted User]
commented
yes please, we also need it.
-
Anonymous
commented
yes please - we need this
-
Grafana
commented
Any improvment on this topic ?
-
Nir Shamir
commented
This feature really needs to be supplied.
I have a customer that wants to upgrade from a old Cluster version of a Firewall to a new Cluster version of the same vendor. on the Old Cluster he has a public IP which is being used for ~70 VPN Site-to-Site and other things.The Old cluster uses BASIC Public IP and the new Cluster uses STANDARD. we can't move that IP ADDRESS to the new Cluster because of this problem.
Now we need to do a very complicated work of replacing that PUBLIC IP in all the other sites and vendors which will take time and cost money.
-
dmarlow
commented
This just bit me. I migrated a Public IP from classic to ARM and couldn't use it in the LB.. now we're stuck. Please fix this!