Skip to content

Commit e7fd703

Browse files
authored
Revise scaling instructions and update date
Updated the date and added notes regarding scaling Azure Web PubSub Service.
1 parent 98c8673 commit e7fd703

1 file changed

Lines changed: 13 additions & 5 deletions

File tree

articles/azure-web-pubsub/howto-scale-manual-scale.md

Lines changed: 13 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Learn how to scale an Azure Web PubSub Service instance to add or r
44
author: biqian
55
ms.service: azure-web-pubsub
66
ms.topic: how-to
7-
ms.date: 12/19/2023
7+
ms.date: 02/10/2026
88
ms.author: biqian
99
ms.custom: devx-track-azurecli
1010
---
@@ -19,8 +19,16 @@ The scale settings take a few minutes to apply. In rare cases, it may take aroun
1919
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/).
2020

2121
> [!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.
2432
2533

2634
## Scale up on Azure portal
@@ -73,10 +81,10 @@ The new Premium_P2 SKU is designed to facilitate extensive scalability for high-
7381

7482
You can scale up the SKU to Premium_P2 using Azure portal or Azure CLI.
7583

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.
7785

7886
> [!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.
8088
8189
## Next steps
8290

0 commit comments

Comments
 (0)