Skip to content

Commit 333e698

Browse files
authored
Merge pull request #1 from sffamily/patch-1
Update signalr-howto-scale-signalr.md
2 parents f27e339 + 641ac5a commit 333e698

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

articles/azure-signalr/signalr-howto-scale-signalr.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
---
22
title: Scale an instance of Azure SignalR Service
3-
description: Learn how to scale an Azure SignalR Service instance to add capacity.
3+
description: Learn how to scale an Azure SignalR Service instance to add or reduce capacity, through Azure Portal or Azure CLI.
44
author: sffamily
55
ms.service: signalr
66
ms.topic: conceptual
7-
ms.date: 03/27/2019
7+
ms.date: 11/21/2019
88
ms.author: zhshang
99
---
1010
# How to scale an Azure SignalR Service instance?
@@ -15,20 +15,20 @@ This article shows you how to scale your instance of Azure SignalR Service. Ther
1515

1616
The scale settings take a few minutes to apply. They don't require you to change your code or redeploy your server application.
1717

18-
For information about the pricing and capacities of individual SignalR Service, see [Azure SignalR Service Pricing Details](https://azure.microsoft.com/en-us/pricing/details/signalr-service/).
18+
For information about the pricing and capacities of individual SignalR Service, see [Azure SignalR Service Pricing Details](https://azure.microsoft.com/pricing/details/signalr-service/).
1919

2020
> [!NOTE]
21-
> If change SignalR Service from the **Free** tier to **Standard** or vice versa, the public service IP will change and it usually takes 3-60 minutes to propagate the change to DNS servers across the entire internet.
21+
> Changing SignalR Service from **Free** tier to **Standard** tier or vice versa, the public service IP will be changed and it usually takes 3-60 minutes to propagate the change to DNS servers across the entire internet.
2222
> Your service might be unreachable before DNS gets updated. Generally it’s not recommended to change your pricing tier too often.
2323
2424

2525
## Scale on Azure Portal
2626

27-
1. In your browser, open the [Azure portal][portal].
27+
1. In your browser, open the [Azure portal](https://portal.azure.com).
2828

2929
2. In your SignalR Service page, from the left menu, select **Scale**.
3030

31-
3. Choose your Pricing tier, and then click **Select**. Select Unit count for **Standard** Tier.
31+
3. Choose your pricing tier, and then click **Select**. You need to set the unit count for **Standard** Tier.
3232

3333
![Scale on Portal](./media/signalr-howto-scale/signalr_howto_scale.png)
3434

@@ -74,7 +74,7 @@ Make a note of the actual name generated for the new resource group. You will us
7474

7575
## Compare pricing tiers
7676

77-
For detailed information, such as messages and connections for each pricing tier, see [SignalR Service Pricing Details](https://azure.microsoft.com/en-us/pricing/details/signalr-service/).
77+
For detailed information, such as included messages and connections for each pricing tier, see [SignalR Service Pricing Details](https://azure.microsoft.com/pricing/details/signalr-service/).
7878

7979
For a table of service limits, quotas, and constraints in each tier, see [SignalR Service limits](../azure-subscription-service-limits.md#azure-signalr-service-limits).
8080

0 commit comments

Comments
 (0)