You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-web-pubsub/howto-scale-manual-scale.md
+13-5Lines changed: 13 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: Learn how to scale an Azure Web PubSub Service instance to add or r
4
4
author: biqian
5
5
ms.service: azure-web-pubsub
6
6
ms.topic: how-to
7
-
ms.date: 12/19/2023
7
+
ms.date: 02/10/2026
8
8
ms.author: biqian
9
9
ms.custom: devx-track-azurecli
10
10
---
@@ -19,8 +19,16 @@ The scale settings take a few minutes to apply. In rare cases, it may take aroun
19
19
For information about the pricing and capacities of individual Web PubSub Service, see [Azure Web PubSub Service Pricing Details](https://azure.microsoft.com/pricing/details/web-pubsub/).
20
20
21
21
> [!NOTE]
22
-
> Changing Web PubSub Service from **Free** tier to **Standard** or **Premium** tier or vice versa, the public service IP will be changed and it usually takes 30-60 minutes to propagate the change to DNS servers across the entire internet. Changing tiers between **Standard** and **Premium** will not change the public IP.
23
-
> Your service might be unreachable before DNS gets updated. Generally it’s not recommended to change your pricing tier too often.
22
+
> Scaling Azure SignalR Service between different pricing tiers may result in service downtime.
23
+
> The downtime behavior varies by tier combination and is summarized in the table.
24
+
>
25
+
> | Scale Scenario | Downtime Expected |
26
+
> |--|--|
27
+
> | Free ↔ Standard / Premium | Yes |
28
+
> | Standard_S1 ↔ Premium_P1 | No |
29
+
> | Premium_P1 ↔ Premium_P2 | No |
30
+
>
31
+
> For scale scenarios where downtime is expected, the downtime occurs because the **public service IP address changes** during the scaling operation. This IP change typically takes **30–60 minutes** to propagate across DNS servers globally, during which the service may be temporarily unreachable. Generally it’s not recommended to change your pricing tier too often.
24
32
25
33
26
34
## Scale up on Azure portal
@@ -73,10 +81,10 @@ The new Premium_P2 SKU is designed to facilitate extensive scalability for high-
73
81
74
82
You can scale up the SKU to Premium_P2 using Azure portal or Azure CLI.
75
83
76
-
The Premium_P2 tier uses a different architecture internally to manage a large amount of underlying resources. Thus, it's expected that scaling operations of this tier might take longer compared to those in smaller SKUs.
84
+
The Premium_P2 tier uses a different architecture internally to manage a large amount of underlying resources. Thus, it's expected that scaling operations of this tier might take longer compared to those tiers in smaller SKUs.
77
85
78
86
> [!NOTE]
79
-
> Be aware that there is a default quota limit capping the number of Web PubSub units at **150** per subscription per region. This is a soft limit and can be increased upon request. To do so, simply submit a support ticket to request an adjustment to this quota.
87
+
> There is a default quota limit capping the number of Web PubSub units at **150** per subscription per region. This is a soft limit and can be increased upon request. To do so, simply submit a support ticket to request an adjustment to this quota.
0 commit comments