Notification Hub Namespace disappeared after moving it between resource groups

Question

Notification Hub Namespace disappeared after moving it between resource groups

Garnet Crookes 0

We attempted to move a notification hub namespace from one resource group to another in our subscription using the move option in the azure portal. The move operation failed due to a 1 hour time out, and now the resource is not visible in the azure portal at all. If I look for it in the azure cli I can see the resource still exists and is listed in the resource group we tried to move it to. It is also continuing to work as notifications are getting sent out. Is there a way we can get the notificaiton hub namespace to show up in the portal again? Thanks in advance.

Praneeth Maddali 7,085 Reputation points Microsoft External Staff Moderator

2026-01-27T18:35:43.9066667+00:00

Hi @Garnet Crookes

Thank you for contacting us about the Notification Hub Namespace disappeared after moving it between resource groups issue. We have begun looking into it and will share our suggestions with you as soon as possible. If you have any additional details or concerns in the meantime, please let us know. We appreciate your patience while we work on this.
Praneeth Maddali 7,085 Reputation points Microsoft External Staff Moderator

2026-01-27T19:44:35.92+00:00
Hi @Garnet Crookes

Thanks for the details. Since your Notification Hub is still sending notifications, the backend resource is healthy and your registrations/PNS credentials are intact only the Azure Portal is not showing the namespace due to the failed move operation.

This can happen when the move partially completes: the resource is moved in ARM but the portal metadata does not refresh.

Here are the steps that typically restore visibility in the portal:

Force ARM to re-index the resource (most reliable fix):

az resource tag --tags forceRefresh=true --resource-group <target-RG> --name <namespaceName> --resource-type Microsoft.NotificationHubs/namespaces

This forces Azure to re-sync the resource and it usually becomes visible in the portal within a few minutes.

Re-register the Notification Hubs provider

Go to Subscription >Resource providers >Microsoft.NotificationHubs > Re-register

Check the provisioningState in Resource Explorer

https://resources.azure.com If the status shows "Moving" or "Failed", the resource exists but cannot be displayed in the UI.

4. Verify the namespace exists in ARM

az resource show --name <namespaceName> --resource-group <RG> --resource-type Microsoft.NotificationHubs/namespaces

Reference :

https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/move-resource-group-and-subscription?tabs=azure-cli

https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/move-support-resources#troubleshooting

Please try the re-index/tag update step first — this resolves most stuck portal visibility issues.

Kindly let us know if the above helps or you need further assistance on this issue.

Please "upvote" if the information helped you. This will help us and others in the community as well.
Garnet Crookes 0 Reputation points

2026-01-27T22:44:50.93+00:00

Hi,

I have tried to refresh the tags and it fails with the following error.

(ResourceNotFound) The Resource 'Microsoft.NotificationHubs/namespaces/<name>' under resource group '<rg>' was not found. For more details please go to https://aka.ms/ARMResourceNotFoundFix

I tried az resource show ... command which has the same error.

It looks like if I run az resource list --resource-type Microsoft.NotificationHubs/namespaces it only lists 2 resources which matches what I can see in the portal. But if I run az notification-hub namespace list then I get 4 different resources. The 2 that show up as part of the list. Then the one I want to refresh and one other one that we were playing around with and had the same thing happen.

I tried option 2 of re-registering the notification hubs which had no effect.

I also tried option 3, the specific namespace I want is not visible in the resource explorer. Only the same two which were listed as part of showing resource.

Maybe I am mistaking the azure cli for the notification-hub cli, because I don't actually have access to it through any of the az resource commands, just through az notification-hub commands. And I can't really do any updates from there.

Is there anything else I can do to get this to show up again if I am not able to update tags? Thanks.
Garnet Crookes 0 Reputation points

2026-02-10T22:18:23.6233333+00:00

@Praneeth Maddali This did not work and my namespace is still not visible is there anything else we can do to get this back?

Thanks!
Garnet
Shree Hima Bindu Maganti 6,880 Reputation points Microsoft External Staff Moderator

2026-02-19T05:07:59.0166667+00:00

Hi @Garnet Crookes
Apology for your inconveniences
This behavior indicates a control plane (ARM) metadata inconsistency caused by the failed move operation. The Notification Hub namespace is still sending notifications because the service plane (Notification Hubs resource provider) remains healthy, but the Azure Resource Manager (ARM) record was not successfully updated during the move. As a result, the namespace appears in az notification-hub namespace list (provider API) but does not appear in az resource list, Resource Explorer, or the Azure Portal (ARM control plane).

When a resource move operation times out, ARM metadata may fail to commit even if the backend provider completes the operation. In this state, tag updates, az resource show, or re-registering the provider will not restore visibility because the ARM record is missing.
https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/move-support-resources#troubleshooting
https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/overview
https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/move-resource-group-and-subscription?tabs=azure-cli
Let me know if you have any further assistances needed.
Garnet Crookes 0 Reputation points

2026-03-10T17:42:10.15+00:00

Hi @Shree Hima Bindu Maganti

Thank you for the explaination of what is happening. How do we add back the missing ARM record for the failed move so that we can see the resource in the control plane again?

Thanks,
Garnet
Shree Hima Bindu Maganti 6,880 Reputation points Microsoft External Staff Moderator

2026-03-14T17:23:47.5833333+00:00

Hi @Garnet Crookes
Thanks for your question. Unfortunately, if the Notification Hubs namespace is no longer visible through Azure Resource Manager (for example, it does not appear in az resource commands or in Resource Explorer and returns ResourceNotFound), there is no supported way for customers to manually add back or recreate the missing ARM record. Since the namespace is still visible via az notification-hub commands and continues to send notifications, it means the service backend is healthy but the ARM control-plane registration became inconsistent during the failed move operation. Until the ARM record is restored, management operations on that namespace will remain unavailable, so please avoid deleting or recreating related resources.
Let me know if you have any further assistances needed.
Garnet Crookes 0 Reputation points

2026-03-18T19:07:59.4466667+00:00

Hi @Shree Hima Bindu Maganti

Is there some process that will go through and restore the ARM record eventually? That seems unlikely since this has been gone for months. What steps do I need to take to get microsoft to restore it for me? Is this just a support level issue? If we upgrade to standard support can we get in contact with someone that can restore it for us? Please advise on any steps we can take to get this restored.

Thanks,

Garnet

1 answer

Your answer

Praneeth Maddali 7,085 Reputation points Microsoft External Staff Moderator

2026-01-27T18:35:43.9066667+00:00

Hi @Garnet Crookes

Thank you for contacting us about the Notification Hub Namespace disappeared after moving it between resource groups issue. We have begun looking into it and will share our suggestions with you as soon as possible. If you have any additional details or concerns in the meantime, please let us know. We appreciate your patience while we work on this.
Praneeth Maddali 7,085 Reputation points Microsoft External Staff Moderator

2026-01-27T19:44:35.92+00:00

Hi @Garnet Crookes

Thanks for the details. Since your Notification Hub is still sending notifications, the backend resource is healthy and your registrations/PNS credentials are intact only the Azure Portal is not showing the namespace due to the failed move operation.

This can happen when the move partially completes: the resource is moved in ARM but the portal metadata does not refresh.

Here are the steps that typically restore visibility in the portal:

Force ARM to re-index the resource (most reliable fix):

az resource tag --tags forceRefresh=true --resource-group <target-RG> --name <namespaceName> --resource-type Microsoft.NotificationHubs/namespaces

This forces Azure to re-sync the resource and it usually becomes visible in the portal within a few minutes.

Re-register the Notification Hubs provider

Go to Subscription >Resource providers >Microsoft.NotificationHubs > Re-register

Check the provisioningState in Resource Explorer

https://resources.azure.com If the status shows "Moving" or "Failed", the resource exists but cannot be displayed in the UI.

4. Verify the namespace exists in ARM

az resource show --name <namespaceName> --resource-group <RG> --resource-type Microsoft.NotificationHubs/namespaces

Reference :

https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/move-resource-group-and-subscription?tabs=azure-cli

https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/move-support-resources#troubleshooting

Please try the re-index/tag update step first — this resolves most stuck portal visibility issues.

Kindly let us know if the above helps or you need further assistance on this issue.

Please "upvote" if the information helped you. This will help us and others in the community as well.
Garnet Crookes 0 Reputation points

2026-01-27T22:44:50.93+00:00

Hi,

I have tried to refresh the tags and it fails with the following error.

(ResourceNotFound) The Resource 'Microsoft.NotificationHubs/namespaces/<name>' under resource group '<rg>' was not found. For more details please go to https://aka.ms/ARMResourceNotFoundFix

I tried az resource show ... command which has the same error.

It looks like if I run az resource list --resource-type Microsoft.NotificationHubs/namespaces it only lists 2 resources which matches what I can see in the portal. But if I run az notification-hub namespace list then I get 4 different resources. The 2 that show up as part of the list. Then the one I want to refresh and one other one that we were playing around with and had the same thing happen.

I tried option 2 of re-registering the notification hubs which had no effect.

I also tried option 3, the specific namespace I want is not visible in the resource explorer. Only the same two which were listed as part of showing resource.

Maybe I am mistaking the azure cli for the notification-hub cli, because I don't actually have access to it through any of the az resource commands, just through az notification-hub commands. And I can't really do any updates from there.

Is there anything else I can do to get this to show up again if I am not able to update tags? Thanks.
Garnet Crookes 0 Reputation points

2026-02-10T22:18:23.6233333+00:00

@Praneeth Maddali This did not work and my namespace is still not visible is there anything else we can do to get this back?

Thanks!
Garnet
Shree Hima Bindu Maganti 6,880 Reputation points Microsoft External Staff Moderator

2026-02-19T05:07:59.0166667+00:00

Hi @Garnet Crookes
Apology for your inconveniences
This behavior indicates a control plane (ARM) metadata inconsistency caused by the failed move operation. The Notification Hub namespace is still sending notifications because the service plane (Notification Hubs resource provider) remains healthy, but the Azure Resource Manager (ARM) record was not successfully updated during the move. As a result, the namespace appears in az notification-hub namespace list (provider API) but does not appear in az resource list, Resource Explorer, or the Azure Portal (ARM control plane).

When a resource move operation times out, ARM metadata may fail to commit even if the backend provider completes the operation. In this state, tag updates, az resource show, or re-registering the provider will not restore visibility because the ARM record is missing.
https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/move-support-resources#troubleshooting
https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/overview
https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/move-resource-group-and-subscription?tabs=azure-cli
Let me know if you have any further assistances needed.
Garnet Crookes 0 Reputation points

2026-03-10T17:42:10.15+00:00

Hi @Shree Hima Bindu Maganti

Thank you for the explaination of what is happening. How do we add back the missing ARM record for the failed move so that we can see the resource in the control plane again?

Thanks,
Garnet
Shree Hima Bindu Maganti 6,880 Reputation points Microsoft External Staff Moderator

2026-03-14T17:23:47.5833333+00:00

Hi @Garnet Crookes
Thanks for your question. Unfortunately, if the Notification Hubs namespace is no longer visible through Azure Resource Manager (for example, it does not appear in az resource commands or in Resource Explorer and returns ResourceNotFound), there is no supported way for customers to manually add back or recreate the missing ARM record. Since the namespace is still visible via az notification-hub commands and continues to send notifications, it means the service backend is healthy but the ARM control-plane registration became inconsistent during the failed move operation. Until the ARM record is restored, management operations on that namespace will remain unavailable, so please avoid deleting or recreating related resources.
Let me know if you have any further assistances needed.
Garnet Crookes 0 Reputation points

2026-03-18T19:07:59.4466667+00:00

Hi @Shree Hima Bindu Maganti

Is there some process that will go through and restore the ARM record eventually? That seems unlikely since this has been gone for months. What steps do I need to take to get microsoft to restore it for me? Is this just a support level issue? If we upgrade to standard support can we get in contact with someone that can restore it for us? Please advise on any steps we can take to get this restored.

Thanks,

Garnet

Answer 1

If the notification hub namespace is not visible in the Azure portal after a failed move operation but is still accessible via the Azure CLI and continues to function, it may be a temporary issue with the Azure portal's display. Here are a few steps you can take to troubleshoot and potentially resolve the issue:

Refresh the Azure Portal: Sometimes, the portal may not reflect the latest state of resources. Try refreshing the portal or logging out and back in.
Check Resource Group and Subscription: Ensure that you are viewing the correct resource group and subscription in the Azure portal where the namespace is supposed to be located.
Use Azure CLI for Verification: Since you can see the resource in the Azure CLI, you can verify its properties and ensure it is correctly configured. You can use commands like az notification-hub namespace show to get details about the namespace.
Contact Azure Support: If the namespace still does not appear in the portal after refreshing and verifying, it may be necessary to contact Azure support for assistance. They can investigate the issue further and help restore visibility in the portal.
Wait for Propagation: Occasionally, changes in Azure can take some time to propagate fully across the platform. If the move operation was recent, it might resolve itself after some time.

These steps should help you address the visibility issue of the notification hub namespace in the Azure portal.

Share via

Notification Hub Namespace disappeared after moving it between resource groups

1 answer

Your answer