I can't bump my Notification Hub Pricing tier

The error you are encountering when trying to update the pricing tier of your Notification Hub namespace from Free to Basic is likely due to a conflict with the existing authorization rules. This can happen if there are existing settings or configurations that prevent the update from being applied.

To resolve this issue, you can try the following steps:

1. Check Authorization Rules: Ensure that there are no conflicting authorization rules that might be preventing the update. You can list the current authorization rules using the Azure CLI command:

      az notification-hub namespace authorization-rule list --resource-group rg-keyboardy --namespace-name nhns-keyboardy
   

2. Modify or Remove Conflicting Rules: If you find any conflicting authorization rules, consider modifying or removing them before attempting to change the pricing tier again.
3. Retry the Update: After addressing any conflicts, retry the command to update the pricing tier:

      az notification-hub namespace update --sku Basic --resource-group rg-keyboardy -n "nhns-keyboardy"
   

4. Use Azure Portal: If the CLI continues to give you issues, try using the Azure portal to change the pricing tier, ensuring that all settings are correctly configured.

If the problem persists after these steps, it may be necessary to contact Azure support for further assistance.

Hi @Abd Alrifai

Thank you for posting your question on the Microsoft Q&A forum.

As You are attempting to upgrade your Notification Hub namespace from the Free tier to the Basic tier using both the Azure portal and the Azure CLI, and the operation fails with the error “Unable to update namespace authorization rules due to conflict. Code: 80.”

Based on similar community discussions and Azure documentation, this error usually occurs because the namespace contains authorization rules that do not match the format expected when moving to the Basic tier. In simple terms, during a tier change Azure needs to update the internal access policies of the namespace, but if there are extra or modified Shared Access Policies, Azure cannot update them, which results in the conflict.

Suggested steps that typically resolve this issue:

• Review and remove any custom Shared Access Policies on the Notification Hub namespace.
  • Only below default policies should be present.
    • DefaultListenSharedAccessSignature
    • DefaultFullSharedAccessSignature
• If custom policies exist, delete them using the Portal or CLI.
• Once the policies are cleaned up, try upgrading the SKU again.
• If the issue continues, you may re-register the Notification Hubs resource provider:

For reference, please review the official documentation for Notification Hubs security:

Please feel free to reply back if you need any further clarification or if the issue continues after trying the above steps.