Open mb236 opened 2 years ago
Hey @mb236 , can you share more details about your use case? Currently 25 IP ranges are limit and this is the first ask we've had to increase it.
Hi @miwebst, yeah for sure. I want to ensure that the traffic to my Azure Static Web App is only allowed from the servers from a third-party service that I am using. For that use case, the service provides an API to gather the list of possible CIDR ranges. And this API happens to return more than 25 possible CIDR ranges. Therefore I ran into the issue mentioned above during the deployment of my Static Web App.
Just out of curiosity, is the limit implemented on the Azure Static App service as well or only in the StaticSites client that is used within the Azure DevOps task?
@miwebst Our organization would also greatly appreciate the capability to add more than 25 IP address ranges. Our static app is used worldwide, and it's been a nightmare trying to keep the application private while also staying under the limit.
Hello! My organisation too would apreciate a limit higher than 25!
Hello!
My organization also need option to add more than 25 IP address ranges
@miwebst I'd be very grateful if you or someone else at Microsoft could share a short update on this. Are there any plans to change the limit? Unfortunately I also couldn't find anything on this in the documentation. I think it would be great to add that to the 'restrictions' section of the documentation.
As mentioned several times above the currenlty limits is a major challenge for the use of Static Web Apps in large networks.
After contacting Microsoft Support they opened https://github.com/MicrosoftDocs/azure-docs/pull/111934 to include this restriction in the 'networking' section of the docs.
Hey folks, how many IP ranges would be suitable for your use case? How are you using the SWA in such a way that you require more than 25 IP ranges?
In my case, 30. Simply the number of WAF servers (in my case) spread across the world.
Honestly the more the merrier. We're looking at using more than 100 IP ranges.
Ok thanks @wklepacki and @AdrianDsg
Hello! My organization too would appreciate a limit higher than 25!
Hi @thomasgauvin, Are there any news on this? I'd be very grateful if you share a short update on this.
We now also run into this issue. Very strange, it's an arbitrary limit that should not exist. We need around 40.
Adding my vote here. We use IP ranges to restrict access to certain internal tools, and we have many IP blocks (one per geographical location). So the more the better. 25 is too few.
Hi @thomasgauvin, Several months have passed since your last message. Has there been any new developments within Microsoft regarding this topic?
Chiming in to support the raising of the cap. My use case has ~150 IPs it needs to support - same as others, I'm restricting access to be only from within internal networks that are in many locations.
I stumbled upon the following error during a deployment to an Azure Static Web App with the AzureStaticWebApp@0 Task in Azure DevOps:
Encountered an issue while validating allowedIpRanges: Number of CIDR ranges cannot exceed 25
As the error indicates I would like to add more than 25 entries to the allowedIpRanges part of the staticwebapp.config.json file. What I would like to know if this is a limitation of the Azure DevOps Task or a limitation by Static Web Apps in general and if there is a way for me to add more than 25 allowed IP ranges.
Thanks in advance!