Bicep : Private Endpoint already exists - Cognitive Search

az feedback auto-generates most of the information requested below, as of CLI version 2.0.62

Related command

az deployment group create --template-file main.bicep --resource-group %rg%

Describe the bug on running the bicep template the 2nd/3rd/4th etc time an error that the private endpoint already exists . it runs successfully the first time

Call to Microsoft.Search/searchServices failed. Error message: PrivateEndpointConnectionProxy myPrivateEndpoint.b2686eab-ca66-415d-8354-89a557719bfe already exists on search service sqlserverk7n35dszoxenq

To Reproduce main.bicep

Expected behavior ability to run the bicep definition multiple times without error/ trying to create another private endpoint

Environment summary

azure-cli                         2.38.0

core                              2.38.0
telemetry                          1.0.6

Dependencies:
msal                            1.18.0b1
azure-mgmt-resource             21.1.0b1

Python location 'C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\python.exe'
Extensions directory 'C:\Users\domalley\.azure\cliextensions'

Python (Windows) 3.10.5 (tags/v3.10.5:f377153, Jun  6 2022, 15:58:59) [MSC v.1929 32 bit (Intel)]

Additional context the same configuration works for sql server main.bicep based on the arm template supplied here: https://docs.microsoft.com/en-us/azure/private-link/create-private-endpoint-bicep?tabs=CLI

[tim-telen]

Same issue here.

[alex-frankel]

This is an idempotency issue with the resource provider. @yonzhan – what is the right way to involve the Networking Resource Provider to look into this?