Skip to content

Commit 5bd2714

Browse files
authored
Merge pull request #110014 from sethmanheim/pricing
Add pricing tier change note; review article
2 parents 0aba935 + 231f095 commit 5bd2714

File tree

1 file changed

+41
-28
lines changed

1 file changed

+41
-28
lines changed

articles/notification-hubs/change-pricing-tier.md

Lines changed: 41 additions & 28 deletions
Original file line numberDiff line numberDiff line change
@@ -10,74 +10,87 @@ ms.workload: mobile
1010
ms.tgt_pltfrm:
1111
ms.devlang:
1212
ms.topic: article
13-
ms.date: 01/28/2019
13+
ms.date: 04/02/2020
1414
ms.author: sethm
15-
ms.reviewer: jowargo
15+
ms.reviewer: thsomasu
1616
ms.lastreviewed: 01/28/2019
1717
---
1818

1919
# Change pricing tier of an Azure notification hubs namespace
20-
Notification Hubs is offered in three tiers: **free**, **basic**, and **standard**. This article shows you how to change the pricing tier for an Azure Notification Hubs namespace.
20+
21+
Notification Hubs is offered in three tiers: **free**, **basic**, and **standard**. This article shows you how to change the pricing tier for an Azure Notification Hubs namespace.
2122

2223
## Overview
23-
In Azure Notification Hubs, a **hub** is the smallest resource/entity. It generally maps to one application and can hold one certificate for each Platform Notification System we support for the app. The application can be a hybrid or a native and a cross-platform application.
2424

25-
A **namespace** is a collection of notification hubs. Each namespace usually consists of hubs that are related and used for a specific purpose. For example, you could have three different namespaces for development, test, and production purposes respectively.
25+
In Azure Notification Hubs, a hub is the smallest resource/entity. It generally maps to one application and can hold one certificate for each Platform Notification System (PNS) we support for the app. The application can be a hybrid, or a native and a cross-platform application.
26+
27+
A **namespace** is a collection of notification hubs. Each namespace usually consists of hubs that are related and used for a specific purpose. For example, you can have three different namespaces for development, test, and production purposes, respectively.
2628

27-
You can associate a pricing tier at the namespace level. Notification Hubs supports three tiers: **free**, **basic**, and **standard**. You can use the tier for a namespace that suits your requirements. The following sections show you how to change the pricing tier of a Notification Hubs namespace.
29+
You can associate a namespace with the **free**, **basic**, or **standard** pricing tiers. You can use the tier for a namespace that suits your requirements. The following sections show you how to change the pricing tier of a Notification Hubs namespace.
2830

29-
## Use Azure portal
30-
When using Azure portal, you can change the pricing tier for a namespace on the namespace page or a hub page. When you change it on a hub page, you actually change it at the namespace level. It changes the pricing tier for the namespace and all hubs in the namespace.
31+
## Use Azure portal
32+
33+
When using the Azure portal, you can change the pricing tier for a namespace on the namespace page, or on a hub page. When you change it on a hub page, you actually change it at the namespace level. It changes the pricing tier for the namespace and all hubs in the namespace.
3134

3235
### Change tier on the namespace page
33-
The following procedure gives you steps to change the pricing tier for a namespace on the namespace page. When you change the tier for a namespace, it applies to all hubs in the namespace.
36+
37+
The following procedure shows how to change the pricing tier for a namespace on the namespace page. When you change the tier for a namespace, it applies to all hubs in that namespace.
3438

3539
1. Sign in to the [Azure portal](https://portal.azure.com).
36-
2. Select **All services** on the left menu.
37-
3. Select **Notification Hub Namespaces** in the **Internet of Things** section. If you select star (`*`) next to the text, it gets added to the left navigation bar under **FAVORITES**. It helps you with accessing the namespaces page faster the next time onwards. After you add it to the FAVORITES, select **Notification Hub Namespaces**.
40+
2. Select **All services** on the left menu.
41+
3. Select **Notification Hub Namespaces** in the **Internet of Things** section. If you select the asterisk (`*`) next to the text, it gets added to the left navigation bar under **FAVORITES**. It helps you access the namespaces page faster going forward. After you add it to FAVORITES, select **Notification Hub Namespaces**.
3842

3943
![All services -> Notification Hub Namespaces](./media/change-pricing-tier/all-services-nhub.png)
40-
1. On the **Notification Hub Namespaces** page, select the namespace for which you want to change the pricing tier.
41-
2. On the **Notification Hub Namespace** page for your namespace, you can see the current pricing tier for the namespace in the **Essentials** section. In the following image, you can see that the pricing tier of the namespace is **Free**.
44+
45+
4. On the **Notification Hub Namespaces** page, select the namespace for which you want to change the pricing tier.
46+
5. On the **Notification Hub Namespace** page for your namespace, you can see the current pricing tier for the namespace in the **Essentials** section. In the following image, you can see that the pricing tier of the namespace is **Free**.
4247

4348
![Current pricing tier on the namespace page](./media/change-pricing-tier/pricing-tier-before.png)
44-
1. On the **Notification Hub Namespace** page for your namespace, select **Pricing Tier** under **Manage** section.
49+
50+
6. On the **Notification Hub Namespace** page for your namespace, select **Pricing Tier** under **Manage** section.
4551

4652
![Select pricing tier on the namespace page](./media/change-pricing-tier/namespace-select-pricing-menu.png)
47-
6. Change your pricing tier, and click the **Select** button.
48-
7. You see the status of the tier change action in the **alerts**.
49-
8. Switch to the **Overview** page. Confirm that the new tier is shown for the **Pricing Tier** field in the **Essentials** section.
50-
1. This step is optional. Select any hub in the namespace. Confirm that you see the same pricing tier in the **Essentials** section. You should see the same pricing tier for all the hubs in the namespace.
53+
54+
7. Change the pricing tier, and then click the **Select** button.
55+
8. You can see the status of the tier change action in the **alerts**.
56+
9. Switch to the **Overview** page. Confirm that the new tier is shown for the **Pricing Tier** field in the **Essentials** section.
57+
10. This step is optional. Select any hub in the namespace. Confirm that you see the same pricing tier in the **Essentials** section. You should see the same pricing tier for all hubs in the namespace.
5158

5259
### Change tier on the hub page
53-
The following procedure gives you steps to change the pricing tier for a namespace on the hub page. Even though you do these steps starting from the hub page, you actually change the pricing tier for the namespace and all hubs in the namespace.
60+
61+
The following procedure shows how to change the pricing tier for a namespace on the hub page. Even though you do these steps starting from the hub page, you actually change the pricing tier for the namespace and all hubs in the namespace.
5462

5563
1. Sign in to the [Azure portal](https://portal.azure.com).
5664
2. Select **All services** on the left menu.
57-
3. Select **Notification Hubs** in the **Internet of Things** section.
58-
4. Select your notification **hub**.
59-
5. Select **Pricing Tier** on the left menu.
60-
6. Change the pricing tier, and click the **Select** button. This action changes the pricing tier setting for the namespace that contains the hub. So, you see the new pricing tier on the namespace page and all hub pages.
65+
3. Select **Notification Hubs** in the **Internet of Things** section.
66+
4. Select your notification **hub**.
67+
5. Select **Pricing Tier** on the left menu.
68+
6. Change the pricing tier, and click the **Select** button. This action changes the pricing tier setting for the namespace that contains the hub. So, you see the new pricing tier on the namespace page and all hub pages.
69+
70+
> [!NOTE]
71+
> All pricing tier changes are effective immediately.
6172
6273
## Use REST API
63-
You can use the following Resource Provider REST APIs to get the current pricing tier and update it.
74+
75+
You can use the following Resource Provider REST APIs to get the current pricing tier and update it.
6476

6577
### Get current pricing tier for a namespace
66-
To get the **current namespace tier**, send a GET command as shown in the following example:
78+
79+
To get the current namespace tier, send a GET command, as shown in the following example:
6780

6881
```REST
6982
GET: https://management.core.windows.net/{subscription ID}/services/ServiceBus/Namespaces/{namespace name}/notificationhubplan
7083
```
7184

7285
### Update pricing tier for a namespace
73-
To **update the namespace tier**, send a PUT command as shown in the following example:
86+
87+
To update the namespace tier, send a PUT command, as shown in the following example:
7488

7589
```REST
7690
PUT: https://management.core.windows.net/{subscription ID}/services/ServiceBus/Namespaces/{namespace name}/notificationhubplan
7791
Body: <NotificationHubPlan xmlns:i="https://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/netservices/2010/10/servicebus/connect"><SKU>Standard</SKU></NotificationHubPlan>
7892
```
7993

80-
81-
8294
## Next steps
95+
8396
For more information about these tiers and pricing, see [Notification Hubs pricing](https://azure.microsoft.com/pricing/details/notification-hubs/).

0 commit comments

Comments
 (0)