Deployment of a simple bicep takes too long

Question

Deployment of a simple bicep takes too long

Dronec 181

I have a bunch of biceps that deploy various parts of Azure infrastructure. All of them complete within reasonable timeframes except this guy. It runs forever, though, in fact, approves the private managed connection as supposed. Any thoughts?

param privateEndpointName string

resource privateEndpoint 'Microsoft.Sql/servers/privateEndpointConnections@2023-05-01-preview' = {
  name: privateEndpointName
  properties: {
    privateLinkServiceConnectionState: {
      status: 'Approved'
      description: 'Private endpoint for ADF'
    }
  }
}

Dronec 181 Reputation points

2024-02-08T05:06:59.3633333+00:00

ShaktiSingh, thanks for your reply. There are no other resource dependencies. I've even tried to run that bicep separately, when all other resources are created. The result is the same: it approves the connection that was previously in "Pending" state (it becomes "Approved") and keeps running forever. At the moment I do not have a support plan.
SSingh-MSFT 16,371 Reputation points Moderator

2024-02-09T04:00:50.11+00:00

Hi
Dronec,

The problem looks strange.

Could you send an email to "AzCommunity@Microsoft.com" with your Subscription ID and thread link to this post, and I will enable a one-time free support request for your subscription.

Please reference this forum thread in the subject:

ATTN: SHAKTI -Deployment of a simple bicep takes too long.

Regards, @ShaktiSingh-MSFT AzCommunity@microsoft.com
Dronec 181 Reputation points

2024-02-09T04:21:43.3466667+00:00

Shakti, Thank you for your assistance. I have already had a session with the first line of MS support this morning when we reproduced the issue. Please check the ticket TrackingID#2402090030000035 for futher details. Any updates are greatly appreciated.
SSingh-MSFT 16,371 Reputation points Moderator

2024-02-12T06:01:07.5233333+00:00

Hi
Dronec, Thanks for providing us the update here. I would recommend you to follow-up with the dedicated Engineer on support case assigned to you for solution. Thank you.
Dronec 181 Reputation points

2024-02-12T06:02:57.4166667+00:00

So far they're trying to find the reason not to do anything))
Jacob Bass 0 Reputation points

2025-06-03T21:33:34.9266667+00:00

Hi @Dronec !

Apologies for reviving this older thread, but was curious if you ever got any support from MSFT on your ticket as to why the deployment is taking so long? Running into the exact same issue as you except for SQL Managed Instance.

2 answers

Your answer

Dronec 181 Reputation points

2024-02-08T05:06:59.3633333+00:00

ShaktiSingh, thanks for your reply. There are no other resource dependencies. I've even tried to run that bicep separately, when all other resources are created. The result is the same: it approves the connection that was previously in "Pending" state (it becomes "Approved") and keeps running forever. At the moment I do not have a support plan.
SSingh-MSFT 16,371 Reputation points Moderator

2024-02-09T04:00:50.11+00:00

Hi
Dronec,

The problem looks strange.

Could you send an email to "AzCommunity@Microsoft.com" with your Subscription ID and thread link to this post, and I will enable a one-time free support request for your subscription.

Please reference this forum thread in the subject:

ATTN: SHAKTI -Deployment of a simple bicep takes too long.

Regards, @ShaktiSingh-MSFT AzCommunity@microsoft.com
Dronec 181 Reputation points

2024-02-09T04:21:43.3466667+00:00

Shakti, Thank you for your assistance. I have already had a session with the first line of MS support this morning when we reproduced the issue. Please check the ticket TrackingID#2402090030000035 for futher details. Any updates are greatly appreciated.
SSingh-MSFT 16,371 Reputation points Moderator

2024-02-12T06:01:07.5233333+00:00

Hi
Dronec, Thanks for providing us the update here. I would recommend you to follow-up with the dedicated Engineer on support case assigned to you for solution. Thank you.
Dronec 181 Reputation points

2024-02-12T06:02:57.4166667+00:00

So far they're trying to find the reason not to do anything))
Jacob Bass 0 Reputation points

2025-06-03T21:33:34.9266667+00:00

Hi @Dronec !

Apologies for reviving this older thread, but was curious if you ever got any support from MSFT on your ticket as to why the deployment is taking so long? Running into the exact same issue as you except for SQL Managed Instance.

Answer 1

Deepanshu katara 16,790 MVP Moderator

Hi , Welcome to Microsoft Q&A I think Issue lies with in API , please use API 2022-05-01-preview and below code once and check

resource symbolicname 'Microsoft.Sql/servers/privateEndpointConnections@2022-05-01-preview' = {
  name: 'string'
  parent: resourceSymbolicName
  properties: {
    privateEndpoint: {
      id: 'string'
    }
    privateLinkServiceConnectionState: {
      description: 'string'
      status: 'string'
    }
  }
}

Please accept answer if it helps , Thanks!

Dronec 181 Reputation points

2024-02-08T04:23:29.8033333+00:00

Hi Deepanshu, Unfortunately, that didn't help.
Deepanshu katara 16,790 Reputation points MVP Moderator

2024-02-08T04:39:40.35+00:00

Ok let me reproduce this once and check, will update you in a while
Dronec 181 Reputation points

2024-02-08T04:44:59.49+00:00
Deepanshu,

Thank you so much. Basically, our current workflow is the following:

Create ADF

Create SQL server

Create managed endpoint in ADF pointing to SQL server

Approve endpoint on SQL side

Any advices are appreciated.
Dronec 181 Reputation points

2024-02-08T07:31:32.48+00:00
Interesting development: as I mentioned before, the bicep approves the private connection, but does not finishes. If I cancel it and re-run, it finishes with the following error:

"code": "DeploymentFailed", "details": [ { "code": "PrivateEndpointConnectionStatusNotPending", "message": "Private Endpoint Connection Status is not Pending" } ],

Which sort of goes against the supposedly idempotent nature of Bicep/ARM deployment which states that I should be able to deploy the same script over and over again.
Dronec 181 Reputation points

2024-02-09T10:26:25.8666667+00:00

Noticed that the same bug is opened here: https://github.com/Azure/bicep-types-az/issues/2032
Dronec 181 Reputation points

2024-04-23T12:01:04.1633333+00:00

Update from Microsoft regarding this issue:

Incident Title: Issue with Azure SQL Server Private Connection

Incident Summary:

The incident started on Feb 9, 2024. It affected the SQL server [iverxue-logisql] and disrupted its normal operation. This incident did not allow resources to be deployed due to a continuous "Ready" status response which caused ARM deployment jobs to go past their allowed timeout period.

Analysis and Mitigation:

Investigations show that a provisioningState value of "Ready" was continuously returned which is seen as a non-terminal state and resulted in the ARM deployment jobs running over the allowed timeout period. These jobs were expecting a terminal state of "Succeeded" for successful resource provision. The issue was fixed via a reconfiguration of the SQL server and private endpoint connections.

Next Steps:

To avoid repeats of this issue in the future, steps have been put in place to ensure operations run smoothly and that the "Ready" status does not cause the ARM deployment jobs to overrun their timeout period. We have created a repair item to fix this issue. We assure you that we are doing our best to provide the highest quality service and will address this incident accordingly. We are sorry for this disruption, and we appreciate your understanding.
SSingh-MSFT 16,371 Reputation points Moderator

2024-04-24T03:52:39.0466667+00:00

Hi Dronec,

Thank you so much for your effort to share the solution here with the community.

Have a great day!
Dronec 181 Reputation points

2024-05-16T05:23:22.9066667+00:00

New update from Microsoft:

Answer 2

Hi
Dronec,

Welcome to Microsoft Q&A forum.

As I understand, your private endpoint for ADF bicep is taking long for completion. With the information provided, it could be due to resource dependencies i.e if private endpoint connection relies on other resources being deployed first, ensure that those resources are successfully provisioned before attempting to deploy the private endpoint connection.

For deeper understanding and investigation into your set up we recommend you to file support case and if you don't have a support plan, do let us know here so that we can check on other options to unblock you. Thanks

Share via

Deployment of a simple bicep takes too long

2 answers

Your answer