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

Secure Deployment needed, can't get past Policy for Private Endpoints #905

Open
willstMSFT opened this issue Nov 7, 2024 · 1 comment
Open
Assignees
Labels
question Further information is requested

Comments

@willstMSFT
Copy link

We have a State customer who has an Azure Policy that doesn't allow any public endpoints. While we requested the customer bypass the Policy to move forward, they were not willing to. Could you modify the template to make the deployment include the deployment of the Private Endpoints, versus having it be a two step process?

@bjakems bjakems self-assigned this Nov 8, 2024
@bjakems bjakems added the question Further information is requested label Nov 8, 2024
@bjakems
Copy link
Contributor

bjakems commented Nov 8, 2024

The latest version in main (1.2) deploys out private endpoints in step 1. In step 2, you must establish VPN connectivity since the resources are network restricted in order to deploy the code to the infrastructure. Which assets are you seeing that do not have private endpoints and are failing the Azure Policy? Please note, in the local.env you must set "export SECURE_MODE=true" in order for the deployment to leverage private endpoints.
Please review the documentation as there are other settings required here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants