Timbo
My feedback
-
1,625 votes
Hi there – excited to say that this is now available in few regions (upgrade IP from Basic to Standard-no zone).
— Anavi N [MSFT]An error occurred while saving the comment An error occurred while saving the comment Timbo
commented
Is the limitation for none availability zone support temporary? This is surely the main reason for wanting to goto standard IP from Basic IP?
An error occurred while saving the comment Timbo
commented
is it planned for Q12020?
An error occurred while saving the comment Timbo
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
An error occurred while saving the comment Timbo
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?
Timbo
supported this idea
·
-
41 votes
We recently published guidance on using Azure Firewall to achieve this for ACI deployments in a Vnet. Would appreciate your feedback on this experience:
https://docs.microsoft.com/en-us/azure/container-instances/container-instances-egress-ip-address
Timbo
supported this idea
·
An error occurred while saving the comment Timbo
commented
any updates?
-
41 votes
Work is planned for this. In the meantime, we suggest using Azure Firewall as potential work around: https://docs.microsoft.com/en-us/azure/container-instances/container-instances-egress-ip-address
Timbo
supported this idea
·
-
225 votes
We’re looking at a few different ways to implement this and finalizing on a design (just correcting status)
An error occurred while saving the comment Timbo
commented
Is there any movement on this request? Would make this service considerably more attractive!
Timbo
supported this idea
·
-
10 votes
Upvotes: 15
Timbo
supported this idea
·
-
283 votes
An error occurred while saving the comment Timbo
commented
Last update on here was 15 months ago. Is this started? or still in the planned phase
Timbo
supported this idea
·
-
1,265 votes
URL rewrite for Application Gateway v2 is currently in public preview! With this, you can now rewrite URL path and query string parameters based on a condition. The condition will be on request or response parameters.
Also, you get the ability to choose the routing to a backend pool based on the original URL or the rewritten URL.
We’d love for you to try it out and let us know your valuable feedback. Learn more here – https://aka.ms/urlrewritepreview and https://aka.ms/urlrewriteconfiguration
Timbo
supported this idea
·
-
239 votes
This feature is planned in the upcoming months.
An error occurred while saving the comment Timbo
commented
Any update on when/if this is to be released?
-
1,094 votes
Wildcard host names in listeners for Application Gateway v2 is currently in public preview! You can configure host names with wildcard characters (* and ?) and up to 5 host names per listener with comma separated values.
We’d love for you to try it out and provide your valuable feedback. Learn more here – https://aka.ms/wildcardlistenerpreview
Timbo
supported this idea
·
An error occurred while saving the comment Timbo
commented
Any update on the status of this item?
I see this is now GA, but AV zone support isn't there (https://docs.microsoft.com/en-us/azure/virtual-network/virtual-network-public-ip-address-upgrade?tabs=option-upgrade-powershell%2Coption-migrate-powershell#limitations). Is this coming?