Azure Resource Provider Registration Failing with InternalServerError — Subscription Registration Issue

Hi @RedwanHossain-0639 ,

ISSUE
Hi The customer is unable to register the Microsoft.DBforPostgreSQL resource provider for their Azure subscription.

The registration has been attempted through multiple supported management paths:

• Azure Portal
• Azure CLI using az provider register --namespace Microsoft.DBforPostgreSQL
• Direct ARM requests

According to the customer, each attempt returns InternalServerError, and the registration remains unsuccessful.

The customer has also confirmed that:

• The Azure subscription is enabled.
• Their account has the Owner role at the subscription level.
• Multiple registration attempts have already been performed.
• The issue is preventing them from proceeding with the required Azure Database for PostgreSQL configuration.

Technical Analysis

Resource provider registration is performed at the Azure subscription level. Before using a resource provider, the Azure subscription needs to be registered for that provider.

Microsoft documentation confirms that Azure CLI can be used to check the registration status of resource providers and manually register a provider.

In this case, the registration operation has already been attempted through the Azure Portal, Azure CLI, and direct ARM requests, with the customer reporting InternalServerError across each method.

Since the failure is occurring across multiple management interfaces, obtaining the current registration status and detailed diagnostics from a controlled registration attempt is recommended before proceeding further.

At this stage, there is insufficient evidence to confirm the root cause. We should not conclude that the failure is caused by Azure Resource Manager, the PostgreSQL resource provider, customer permissions, subscription configuration, or another Azure component without supporting telemetry.

RCA Status: Under Investigation

Mitigation / Next Steps

1. Verify the current provider registration state

Check the registration status of Microsoft.DBforPostgreSQL for the affected subscription and determine whether it currently reports Registered, Registering, or NotRegistered.

1. Perform one controlled registration attempt

Run the resource provider registration again through Azure CLI and capture the complete diagnostic information from that attempt.

1. Collect diagnostic evidence

Capture the following from the failed registration attempt:

• Affected Subscription ID
• Resource provider namespace: Microsoft.DBforPostgreSQL
• Exact failure timestamp and timezone
• Complete error message/response
• HTTP status/error code
• Correlation ID / Request ID, if returned
• Current provider registration state
• Screenshot of the failure from the Azure Portal, if available
• Avoid unnecessary repeated registration attempts

Since the same operation has already failed through multiple methods, focus on obtaining complete diagnostic information from a controlled attempt rather than repeatedly issuing the registration operation.

1. Escalate for backend investigation if InternalServerError persists

If Microsoft.DBforPostgreSQL continues to return InternalServerError, provide the collected subscription and correlation details for further engineering investigation of the unsuccessful resource-provider registration operation.

1. Validate after remediation

Once the registration operation succeeds, verify that Microsoft.DBforPostgreSQL shows the expected registration state before proceeding with the Azure Database for PostgreSQL Flexible Server operation.

RCA Position

RCA remains under investigation.

The confirmed issue is that registration of Microsoft.DBforPostgreSQL is failing with InternalServerError across the customer's attempted Portal, Azure CLI, and ARM methods.

The available evidence does not establish why the registration operation is failing. Backend diagnostic information associated with the failed request should be reviewed before confirming the root cause.