Bicep Template failing on privateEndpointConnections

Mahesh chandak 0

Hi,

We are getting the below error while deploying privateEndpointConnections for service bus.

ERROR: {"status":"Failed","error":{"code":"DeploymentFailed","target":"/subscriptions/e03a9d4e-499f-4fd2-8fd1-4d13d0756fc2/resourceGroups/rg-dev-uks-integrations-common/providers/Microsoft.Resources/deployments/azuredeploy","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-deployment-operations for usage details.","details":[{"code":"PrivateEndpointConnectionInvalidStateChange","message":"A state change from Approved to Approved is not valid"}]}}

Here is the snip of the bicep template. Also just to let you know the private endpoint connection already exists. But we expect the bicep template to not fail and just update the existing resource.

Bicep snip

var servicebusprivateendpoint='/subscriptions/xxx/resourceGroups/rg-${environment}-xxxx/providers/Microsoft.Network/privateEndpoints/xxx'


resource privateEndpointConnections_102e8d0a_a3b0_4307_849d_39d2ac85be19 'Microsoft.ServiceBus/namespaces/privateEndpointConnections@2022-10-01-preview' = {
  parent: servicebus_namespace_resource
  name: '102e8d0a-a3b0-4307-849d-39d2ac85be19'
  location: resource_location
  properties: {
    provisioningState: 'Succeeded'
   privateEndpoint: {
      id: servicebusprivateendpoint
    }
    privateLinkServiceConnectionState: {
      status: 'Approved'
      description: 'Auto-Approved'
    }
  }
}

Stanislav Zhelyazkov 21,336 Reputation points MVP

2024-03-08T08:09:23.7033333+00:00

Hi this is most likely bug with the API. I would suggest logging official support case or log the issue on GitHub.

Please "Accept the answer" if the information helped you. This will help us and others in the community as well.
MuthuKumaranMurugaachari-MSFT 22,146 Reputation points

2024-03-11T20:50:02.8966667+00:00

Mahesh chandak Thanks for posting your question in Microsoft Q&A. Quickly reviewed connection 102e8d0a-a3b0-4307-849d-39d2ac85be19 in the backend logs and found that it was already approved.

From the exception above and backend logs, the connection was already approved and changing status from approved to approved is not valid and hence you got the error. If this template doesn't require any change in status, try including actionsRequired : None in PrivateLinkServiceConnectionState and validate again. Check out https://learn.microsoft.com/en-us/rest/api/virtualnetwork/private-endpoints/create-or-update?view=rest-virtualnetwork-2023-09-01&tabs=HTTP for samples.

I hope this helps. If you have any questions or still face issues, let me know.
MuthuKumaranMurugaachari-MSFT 22,146 Reputation points

2024-03-13T13:32:57.1666667+00:00

Mahesh chandak Just a follow up to see if you have any questions on the info shared below. Feel free to reach out for any questions.

Mahesh Chandak 0

Still no luck on this. I am still getting the same error.here is the snip of bicep

resource namespaces_sb_dev_uks_integrations_name_102e8d0a_a3b0_4307_849d_39d2ac85be19 'Microsoft.ServiceBus/namespaces/privateEndpointConnections@2022-10-01-preview' = {
  parent: servicebus_namespace_resource
  name: '102e8d0a-a3b0-4307-849d-39d2ac85be19'
  location: resource_location
  properties: {
    provisioningState: 'Succeeded'
    privateEndpoint: {
      
    }
    privateLinkServiceConnectionState: {
      actionRequired: 'None'
      status: 'Approved'
      description: 'Auto-Approved'
    }
  }
}

MuthuKumaranMurugaachari-MSFT 22,146 Reputation points

2024-03-13T16:39:27.2433333+00:00

Sorry about that. I am looking into it and get back to you.
Mahesh Chandak 0 Reputation points

2024-03-19T15:56:33.1766667+00:00

any update on this?