Skip to content

Commit f830749

Browse files
authored
Merge pull request #46023 from nohaelanwer/patch-4
Update service-bus-create-namespace-portal.md
2 parents 935a7c3 + 58b0857 commit f830749

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

includes/service-bus-create-namespace-portal.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ To create a namespace:
2323
1. Enter a **name for the namespace**. The system immediately checks to see if the name is available. For a list of rules for naming namespaces, see [Create Namespace REST API](/rest/api/servicebus/create-namespace).
2424
2. Select the pricing tier (Basic, Standard, or Premium) for the namespace. If you want to use [topics and subscriptions](../articles/service-bus-messaging/service-bus-queues-topics-subscriptions.md#topics-and-subscriptions), choose either Standard or Premium. Topics/subscriptions are not supported in the Basic pricing tier.
2525
3. If you selected the **Premium** pricing tier, follow these steps:
26-
1. Specify the number of **messaging units**. The premium tier provides resource isolation at the CPU and memory level so that each workload runs in isolation. This resource container is called a messaging unit. A premium namespace has least one messaging unit. You can select 1, 2, or 4 messaging units for each Service Bus Premium namespace. For more information, see [Service Bus Premium Messaging](../articles/service-bus-messaging/service-bus-premium-messaging.md).
26+
1. Specify the number of **messaging units**. The premium tier provides resource isolation at the CPU and memory level so that each workload runs in isolation. This resource container is called a messaging unit. A premium namespace has at least one messaging unit. You can select 1, 2, or 4 messaging units for each Service Bus Premium namespace. For more information, see [Service Bus Premium Messaging](../articles/service-bus-messaging/service-bus-premium-messaging.md).
2727
2. Specify whether you want to make the namespace **zone redundant**. The zone redundancy provides enhanced availability by spreading replicas across availability zones within one region at no additional cost. For more information, see [Availability zones in Azure](../articles/availability-zones/az-overview.md).
2828
4. For **Subscription**, choose an Azure subscription in which to create the namespace.
2929
5. For **Resource group**, choose an existing resource group in which the namespace will live, or create a new one.

0 commit comments

Comments
 (0)