Azure Database for PostgreSQL flexible server Is not getting Started

Question

Azure Database for PostgreSQL flexible server Is not getting Started

Talior, Anil 0

Azure Database for PostgreSQL flexible server Is not getting Started. and server is currently in starting state.

And getting below waring massage in portal:

"The server is currently in 'starting' state. Please wait for the operation to complete. You can refresh to check status. Reach out to Microsoft support if the operation is taking too long."

Please help me to resolving the above issue.

Thanks

Anil

Ganesh Chelluri 190 Reputation points Microsoft External Staff Moderator

2026-08-03T15:46:22.2733333+00:00
Hi @Talior, Anil ,

If the Azure Database for PostgreSQL Flexible Server has remained in the "Starting" state for an extended period and does not transition to "Ready", this is typically not something that can be resolved from the portal alone.

Could you please share the information in private message:

Subscription ID

Server name

Azure region

Approximate time when the start operation was initiated

Also, please check the Activity Log for any failed operations related to the server.

If the server continues to remain stuck in the Starting state, a support ticket may be required for further investigation.

Thanks.
Ganesh Chelluri 190 Reputation points Microsoft External Staff Moderator

2026-08-04T10:16:31.6733333+00:00

Hi @Talior, Anil

We haven’t received a response. Please let us know if you need any additional information or assistance from my side.
Dhir, Nitin-XT 0 Reputation points

2026-08-04T11:22:32.4633333+00:00

hi @Ganesh Chelluri
Approximate time when the start operation was initiated - initiated on 31 July but got stuck in updating state

Comment: Activity log have Get PostgreSQL server List job running continously and no option to cancel it. We need this server into Ready state for processing.
Ganesh Chelluri 190 Reputation points Microsoft External Staff Moderator

2026-08-04T16:55:00.54+00:00
Hi @Dhir, Nitin-XT ,

Thanks for the update. A couple of points to help move this forward.

On the Activity Log entry

"Get PostgreSQL server List" is a read operation the portal fires every time the blade is opened or refreshed. It isn't a running job, there's nothing to cancel, and it won't be what's holding the server.

Finding the actual start operation

Open Activity Log on the server.

Set the timespan to custom and select 31 July.

Look for a Write entry such as Start PostgreSQL server or Update PostgreSQL server.

Open it and note the status and the Correlation ID from the JSON tab.

Getting the server back to Ready

While the server is in Starting/Updating, Restart and Stop aren't available, so this is actioned from the backend. Raise a support request from the portal:

Help + support > Create support request > Technical > Azure Database for PostgreSQL flexible server

Include in the request:

Subscription ID

Server name

Azure region

Correlation ID and UTC timestamp of the 31 July start operation

That gives the engineer everything needed to pick it up straight away.
Ganesh Chelluri 190 Reputation points Microsoft External Staff Moderator

2026-08-06T02:43:56.7433333+00:00

Hi @Talior, Anil ,

Just checking in to see if the information provided earlier was helpful. Please let us know if you need any additional details or assistance, and we’ll gladly continue supporting you.

Your answer

Ganesh Chelluri 190 Reputation points Microsoft External Staff Moderator

2026-08-03T15:46:22.2733333+00:00

Hi @Talior, Anil ,

If the Azure Database for PostgreSQL Flexible Server has remained in the "Starting" state for an extended period and does not transition to "Ready", this is typically not something that can be resolved from the portal alone.

Could you please share the information in private message:

Subscription ID

Server name

Azure region

Approximate time when the start operation was initiated

Also, please check the Activity Log for any failed operations related to the server.

If the server continues to remain stuck in the Starting state, a support ticket may be required for further investigation.

Thanks.
Ganesh Chelluri 190 Reputation points Microsoft External Staff Moderator

2026-08-04T10:16:31.6733333+00:00

Hi @Talior, Anil

We haven’t received a response. Please let us know if you need any additional information or assistance from my side.
Dhir, Nitin-XT 0 Reputation points

2026-08-04T11:22:32.4633333+00:00

hi @Ganesh Chelluri
Approximate time when the start operation was initiated - initiated on 31 July but got stuck in updating state

Comment: Activity log have Get PostgreSQL server List job running continously and no option to cancel it. We need this server into Ready state for processing.
Ganesh Chelluri 190 Reputation points Microsoft External Staff Moderator

2026-08-04T16:55:00.54+00:00

Hi @Dhir, Nitin-XT ,

Thanks for the update. A couple of points to help move this forward.

On the Activity Log entry

"Get PostgreSQL server List" is a read operation the portal fires every time the blade is opened or refreshed. It isn't a running job, there's nothing to cancel, and it won't be what's holding the server.

Finding the actual start operation

Open Activity Log on the server.

Set the timespan to custom and select 31 July.

Look for a Write entry such as Start PostgreSQL server or Update PostgreSQL server.

Open it and note the status and the Correlation ID from the JSON tab.

Getting the server back to Ready

While the server is in Starting/Updating, Restart and Stop aren't available, so this is actioned from the backend. Raise a support request from the portal:

Help + support > Create support request > Technical > Azure Database for PostgreSQL flexible server

Include in the request:

Subscription ID

Server name

Azure region

Correlation ID and UTC timestamp of the 31 July start operation

That gives the engineer everything needed to pick it up straight away.
Ganesh Chelluri 190 Reputation points Microsoft External Staff Moderator

2026-08-06T02:43:56.7433333+00:00

Hi @Talior, Anil ,

Just checking in to see if the information provided earlier was helpful. Please let us know if you need any additional details or assistance, and we’ll gladly continue supporting you.