Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hiding App Service behind a VNet #263

Closed
mikhailshilkov opened this issue May 28, 2019 · 2 comments · Fixed by pulumi/examples#909
Closed

Hiding App Service behind a VNet #263

mikhailshilkov opened this issue May 28, 2019 · 2 comments · Fixed by pulumi/examples#909
Assignees
Labels
area/providers kind/enhancement Improvements or new features
Milestone

Comments

@mikhailshilkov
Copy link
Member

mikhailshilkov commented May 28, 2019

One problem with Azure App Service has always been the fact that it's open to the internet. This is changing: Azure has a preview feature to Integrate your app with an Azure Virtual Network in combination with Access Restrictions and Service Endpoints.

This post summarizes how to use this integration to isolate backend API from public access.

The feature is in preview, and the tooling is somewhat half-baked so far. There is a How do we integrate the new vnet integration with ARM templates? issue for ARM templates docs, but the feature seems to work.

Terraform still lags behind: App Service VNET integration not working, Problem with IP Restriction rules in azurerm_app_service resource. Therefore, Pulumi support is lacking too.

I'm creating this issue to track progress, as the case seems to be important for enterprisy Azure users.

@NoNameProvided
Copy link

Hi @viveklak!

I see this landed in the next-gen version, this means this wont be backported to the current Azure provider?

@viveklak
Copy link
Contributor

Hi @viveklak!

I see this landed in the next-gen version, this means this wont be backported to the current Azure provider?

I believe complete support for this in the azure provider is currently still blocked behind hashicorp/terraform-provider-azurerm#2488. However, it is entirely possible for you to mix providers and use the nextgen provider to achieve this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/providers kind/enhancement Improvements or new features
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants