Azure-docs: New-vnet-integration - GA Date

[Syamala2604]

Hi, I see the goal is to have the feature GA by mid-year of 2019. (This is a goal not a commitment.) 3 months ago. Just wanted to check if there is any change in the commitment.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: a7a98803-1438-b1b5-f543-7dd88bc4294e
• Version Independent ID: 37ff1d0f-ed8e-5e4d-1f4c-1b9f6cffb938
• Content: Integrate app with Azure Virtual Network - Azure App Service
• Content Source: articles/app-service/web-sites-integrate-with-vnet.md
• Service: app-service
• GitHub Login: @ccompy
• Microsoft Alias: ccompy

[SnehaAgrawal-MSFT]

@Syamala2604 Thanks for the question! We are investigating and will update you shortly.

[SnehaAgrawal-MSFT]

@Syamala2604 Thanks again for the question! I have assigned the issue to the content author to get you update on this.

[gcakiroglu]

Hi, any updates on the estimated GA date for this capability?

[shaunakv1]

Same here, any updates on the GA date yet?

[GrzegorzOpara]

Hi, this is something we are really waiting for. It would be really helpful to have some estimates about the GA delivery date, since it's a blocker for a few our projects.

[jcbrooks92]

Please see this comment above:

This feature is in preview but, it is supported for Windows app production workloads with the following limitations:

[salviri]

Same here, we are very looking forward to this feature as well.

[arkiaconsulting]

@jcbrooks92 Any source that could prove this info ?

[jcbrooks92]

@arkiaconsulting

Based on this statement here "it is supported for Windows app production workloads"

This feature is in preview but, it is supported for Windows app production workloads with the following limitations:

You can only reach addresses that are in the RFC 1918 range. Those are addresses in the 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16 address blocks.
You cannot reach resources across global peering connections
You cannot set routes on the traffic coming from your app into your VNet
The feature is only available from newer App Service scale units that support PremiumV2 App Service plans.
The integration subnet can only be used by only one App Service plan
The feature cannot be used by Isolated plan apps that are in an App Service Environment
The feature requires an unused subnet that is a /27 with 32 addresses or larger in your Resource Manager VNet
The app and the VNet must be in the same region
You cannot delete a VNet with an integrated app. You must remove the integration first
You can have only one regional VNet Integration per App Service plan. Multiple apps in the same App Service plan can use the same VNet.

[SnehaAgrawal-MSFT]

@Syamala2604 We will close this out but if you feel you need more information please just let us know.

[rdewet]

When will it be supported for Linux workloads?