> ## Documentation Index
> Fetch the complete documentation index at: https://help.nops.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Move Non-Production Service Bus Namespaces from Premium to Standard

> Move non-production Service Bus namespaces from Premium to the much cheaper Standard tier.

A Service Bus Premium namespace is billed for dedicated messaging units every hour. Standard is a shared tier with a small base charge plus a charge per million operations above an included amount. nOps finds non-production Premium namespaces and estimates the saving from moving them to Standard.

| | |
| - | - |
| **Cloud** | Microsoft Azure |
| **Category** | Integration |
| **Service** | Azure Service Bus |
| **Action** | Modify |
| **Effort** | Medium |
| **Restart needed** | Yes |
| **Can be rolled back** | Yes |
| **Analysis window** | Last 7 days |
| **Source** | nOps |

## Why it matters

Development and test namespaces are often created on Premium to match production, which costs far more than they need.

## How nOps finds it

nOps reads the last 14 days of Service Bus billing. A namespace is flagged when its Premium messaging units were billed on at least 7 of those days and recently, its name or resource group contains a non-production word (such as dev, test, qa, staging or uat, and not prod), and it does not use geo-replication. The saving is the 7-day Premium cost, scaled to a month, minus what Standard's base charge would cost for the same days, using the regional list price. It assumes your traffic stays within the operations included in Standard's base charge. Services mostly paid with credits and savings under \$5 a month are left out.

## Before you start

Confirm the namespace uses no Premium-only features and that its traffic fits Standard.

## How to implement

1. Check the namespace does not use Premium-only features: private endpoints or VNet integration, messages over 256 KB, geo-disaster recovery or JMS 2.0.
2. Create a Standard namespace (portal: **Service Bus → Create**, or `az servicebus namespace create --sku Standard ...`).
3. Recreate the queues, topics, subscriptions and access policies, ideally from your Terraform, Bicep or ARM templates.
4. Point clients at the new namespace, let the old one drain, then delete it.

## Risks and considerations

* Premium cannot be downgraded in place, so this is a migration to a new namespace with a new connection string.
* Standard shares capacity with other tenants, so latency and throughput are less predictable.
* Premium does not bill operations, so nOps cannot see your volume. Above the included operations, Standard charges per million, which lowers the saving.
* To roll back, point clients back to the Premium namespace before you delete it.

## FAQs

> [accordion] How does nOps decide a namespace is non-production?
>
> From words in its name and resource group, such as dev, test, qa, staging or uat. A namespace whose own name contains prod is treated as production.

## Related

* [Use the Developer Tier for Non-Production API Management](https://help.nops.io/inform/supported-recommendations/use-the-developer-tier-for-non-production-api-management)
* [Lower Over-Provisioned Event Hubs Throughput Units](https://help.nops.io/inform/supported-recommendations/lower-over-provisioned-event-hubs-throughput-units)
* [Supported recommendations](https://help.nops.io/inform/supported-recommendations.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.