Implement using Private endpoint about ipam HOT 4 OPEN

I have deployed everything using Terraform with private endpoints and vnet integration, no public access allowed.
Not sure if it's of any interest since not everyone uses Terraform.

Let me know and i could perhaps share my terraform module in some way.

from ipam.

Hi @maayanlux, thank you for reaching out on this topic!

The high-level process to make this solution private is as follows:

1. Deploy the solution with the provided deploy.ps1 script.
2. Create Private Endpoints for all of the Azure resources (App Services, CosmosDB, KeyVault)
3. Enable Virtual Network Integration for the App Service

The process of creating the Private Endpoints should also create the required Private DNS Zones, or you can choose to link those Private Endpoints to your existing/centralized Private DNS Zone you may already have within your environment.

I'm guessing the reason that you're seeing the error message above is likely DNS related as the App Service will need to be able to resolve the Private for CosmosDB.

That is the very high level process, and I am indeed working on some more thorough documentation on this process which I'll post soon. In the meantime, if you'd like some additional assistance please feel free to ping me on Team at [email protected], or even drop me an email. We can schedule some time to take a look at your environment together if that would be helpful. Let me know, thanks!

from ipam.

@egnirra , I would like to approach for the same requirement. Could you please assist me to implement and please provide a strategy to achieve it . Please let me know if we can connect over email?

from ipam.

I have deployed everything using Terraform with private endpoints and vnet integration, no public access allowed. Not sure if it's of any interest since not everyone uses Terraform.

Let me know and i could perhaps share my terraform module in some way.

Could you share your terraform

from ipam.