Azure API Management
An Azure service that provides a hybrid, multi-cloud management platform for APIs.
2,187 questions
Does API Management Standard v2 Tier allow a Inbound Private IP to exist?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(176, 37%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJW%3C/text%3E%3C/svg%3E)
Jeff Wang
0
Reputation points
I am aware that by default API Management standard v2 tier does not have any Inbound or Outbound IP as it is running on a shared infrastructure. However, after placing it in a VNET and attempting to filter traffic using AKS's Ingress setting I noticed that I can limit APIM's traffic to AKS by filtering out its Subnet's address range.
This leads me to question if there are anyways I can forcefully apply an Inbound IP? I need to route traffic from Application Gateway to this APIM also and right now I have to use its domain but I need it to be an IP address. I had tried Private Endpoint but its not available for v2 tiers. Any suggestions are welcome, many thanks!
{count} votes
-
Jeff Wang 0 Reputation points
2024-07-11T09:33:05.4+00:00 I received this error when attempting to create the Private Endpoing: Call to Microsoft.ApiManagement/service failed. Error message: Setting up Private Endpoint Connection for API Management service /subscriptions/xxx/resourceGroups/xxx/providers/Microsoft.ApiManagement/service/xxx which is of StandardV2 is not supported. Please contact support to allowlist your subscription. (Code: NotSupported). Say if I contact support and allowlist my subscription, would this private endpoint work normally as an private endpoint on a premium tier API management? Thanks again
-
Aki Nishikawa 1,825 Reputation points Microsoft Employee2024-07-18T02:31:07.5933333+00:00 Hello @Jeff Wang ,
As you tried, APIM standard v2 does not support private endpoints as of now. In the current condition, how about configuring
ip-filterpolicy in global scope?- https://learn.microsoft.com/en-us/azure/api-management/ip-filter-policy
- https://learn.microsoft.com/en-us/azure/api-management/api-management-howto-policies#scopes
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(230.39999999999998, 93%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBG%3C/text%3E%3C/svg%3E)
Ben Gimblett 4,530 Reputation points Microsoft Employee2024-07-19T14:01:07.41+00:00 Doc link for the above limitation https://learn.microsoft.com/en-us/azure/api-management/v2-service-tiers-overview#limitations
Sign in to comment
Sign in to answer