Closed RSBlek closed 1 year ago
Thank you for opening this issue, we will look into it.
@RSBlek Thanks for reaching out to us and reporting this issue. Could you please whitelist "52.138.230.0/23"
IP address range instead and check the behavior of this issue ?
Also for the respective ACR region you have chosen, Could you ensure that you have added the right IP Address as specified here ? Awaiting you reply.
Hello @navba-MSFT Thanks for the reply.
After adding 52.138.230.0/23 everything works fine. Is this the way to go?
I thought that the Checkbox "Allow trusted Microsoft services to access this container registry" would have the same result.
Hello @navba-MSFT, It seems your link for IP Address range for the ACR isn't working anymore and I fail to find the new one. Could you please help? Maybe that would be helpful to link it in the ACR documentation too, in the section about setting ACR Tasks. Best, Julien
Describe the bug
I can't run the "acr purge" command in a newly created Container Registry. The agent crashes with the error ...client with IP '52.138.231.5' is not allowed access....
I found "52.138.230.0/24" in the list of azure ip ranges. But i don't think that adding all possible ip ranges to the firewall is the correct solution.
The checkbox to allow trusted azure services is checked, but has no effect.
Related command
Errors
Issue script & Debug output
Will add when needed
Expected behavior
The acr purge command finishes without errors and without adding the explicit ip range because the checkbox to trust azure services is active.
Environment Summary
Additional context
No response