Hello
Thanks for reaching out to Microsoft Q and A Forum.
We can try the following steps, but if the issue persists, I strongly recommend creating a support ticket to involve the backend engineering team for a resolution.
Remove Geo-DR Pairing
You can try breaking the pairing using:
az servicebus georecovery-alias break-pair --resource-group <resource_group> --namespace-name <namespace_name> --alias <alias>
This command unlinks the paired namespaces, which might help reset the provisioning state.
Force Delete Geo-DR Alias
If the alias deletion is blocked, try:
az servicebus georecovery-alias delete --resource-group <resource_group> --namespace-name <namespace_name> --alias <alias>
This forces the removal of the Geo-DR alias, which might resolve the stuck state.
Restart the Service Bus Namespace
While Azure Service Bus does not support a direct restart, you can update the namespace to trigger a re-evaluation:
az servicebus namespace update --name <namespace_name> --resource-group <resource_group> --tags "reset=true"
Adding a temporary tag forces Azure to refresh the namespace state.
Also request you to accept the answer if it was informative and helpful.
Thanks,
Pradeep