This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](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(121.6, 74%, 21%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ENB%3C/text%3E%3C/svg%3E)
Currently, the APIM V2 SKUs only support vnet injection for private outbound traffic.
Later this year, these SKUs are also supposed to support private endpoint for private inbound traffic.
My question is, when both features will be available, will we be able to use them at the same time on the same APIM instance to be able to have all traffic flow through private networks instead of needing a Premium APIM V1 for this?
![](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(0, 59%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJM%3C/text%3E%3C/svg%3E)
@NGANDU-BISEBA Gabriel Thanks for reaching out. V2 SKU's will not support VNET injection, but it will support inbound private link by end of year no exact ETA available.
Hello @JananiRamesh-MSFT ,
Sorry for the confusion. I meant VNET integration and not vnet injection.
My question is if VNET integration and private endpoints will be able to be enabled at the same time unlike App Services where apps must have one or the other.
Hello @JananiRamesh-MSFT ,
Sorry for the confusion, I meant VNET integration instead of injection.
My question is if, unlike App service apps where it is one or the other for a specific app, we will be able to enable both private links and VNET integration at the same time on the same API management instance
@NGANDU-BISEBA Gabriel Apologies for the delay, let me discuss internally on this and will get back to you.
![](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)
Hi- thanks for the question
The most current info available is here this goes with the networking concepts doc here
We are currently waiting on the details for the planned Premium V2 tier
So today, the only APIM versions which support private inbound and outbound together are Premium (and Developer) in the classic tiers.
Hello,
Thank you for the answer.
So if I understand correctly, in the future, if the V2 SKUs support both private inbound and outbound, it will only be through the Premium V2 SKU?