Update signalr-howto-scale-signalr.md

JialinXin · web-flow · commit a05d9d247de2 · 2026-02-11T12:30:48.000+08:00
minor update
diff --git a/articles/azure-signalr/signalr-howto-scale-signalr.md b/articles/azure-signalr/signalr-howto-scale-signalr.md
@@ -26,7 +26,7 @@ For information about the pricing and capacities of individual SignalR Service,
 > | -- | -- |
 > | Free ↔ Standard / Premium | Yes |
 > | Standard_S1 ↔ Premium_P1 | No |
-> | Premium_P1 ↔ Premium_P2 | Yes |
+> | Premium_P1 ↔ Premium_P2 | No |
 >
 > 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.
 

Original file line number	Diff line number	Diff line change
`@@ -26,7 +26,7 @@ For information about the pricing and capacities of individual SignalR Service,`
`26`	`26`	`> \| -- \| -- \|`
`27`	`27`	`> \| Free ↔ Standard / Premium \| Yes \|`
`28`	`28`	`> \| Standard_S1 ↔ Premium_P1 \| No \|`
`29`		`-> \| Premium_P1 ↔ Premium_P2 \| Yes \|`
	`29`	`+> \| Premium_P1 ↔ Premium_P2 \| No \|`
`30`	`30`	`>`
`31`	`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.`
`32`	`32`