Added connection limits per SKU

Author: shpathak-msft

articles/redis/overview.md

@@ -118,7 +118,33 @@ The following table helps describe some of the features supported by tier:
 ### Other considerations when picking a tier
 
 - **Network performance**: If you have a workload that requires high throughput, network bandwidth might cause a bottleneck. You can increase bandwidth by moving up to a higher performance tier or by moving to a large instance size. Larger size instances have more bandwidth because of the underlying VM that hosts the cache. Higher bandwidth limits help you avoid network saturation that cause time-outs in your application. For more information on bandwidth performance, see [Performance testing](best-practices-performance.md)
-- **Maximum number of client connections**: Each SKU has a maximum number of client connections. This limit increases with higher performance tiers and larger instances sizes. For more information on the limit for each SKU, see [Azure Managed Redis Pricing](https://aka.ms/amrpricing).
+- **Maximum number of client connections**: Each SKU has a maximum number of client connections. This limit increases with higher performance tiers and larger instances sizes. The following table shows the maximum client connections allowed per Azure Managed Redis SKU
+
+
+[!INCLUDE [tier-preview](includes/tier-preview.md)]
+
+|  Size (GB)  |    Memory Optimized   |    Balanced   |   Compute Optimized  |  Flash Optimized (preview)|
+|:-----------:|:---------------------:|:-------------:|:--------------------:|:--------------------:|
+|    0.5      |       -               |    15000      |         -            |       -              |
+|     1       |       -               |    15000      |         -            |       -              |
+|     3       |       -               |    15000      |         30000        |       -              |
+|     6       |       -               |    15000      |         30000        |       -              |
+|     12      |   15000               |    30000      |         75000        |       -              |
+|     24      |   30000               |    75000      |         150000       |       -              |
+|     60      |   75000               |    150000     |         200000       |       -              |
+|     120     |   150000              |    200000     |         200000       |       -              |
+|     180 *   |   200000              |    200000     |         200000       |       -              |
+|     240 *   |   200000              |    200000     |         200000       |       75000          |
+|     360 *   |   200000              |    200000     |         200000       |       -              |
+|     480 *   |   200000              |    200000     |         200000       |       150000         |
+|     720 *   |   200000              |    200000     |         200000       |       200000         |
+|     960 *   |   200000              |    200000     |         -            |       200000         |
+|     1440 *  |   200000              |        -      |         -            |       200000         |
+|     1920 *  |   200000              |        -      |         -            |       200000         |
+|     4500 *  |       -               |        -      |         -            |       200000         |
+
+  \* These tiers are in Public Preview.
+
 - **High availability**: Azure Managed Redis provides multiple [high availability](high-availability.md) options. The SLA only covers connectivity to the cache endpoints. The SLA doesn't cover protection from data loss. For more information on the SLA, see the [SLA](https://azure.microsoft.com/support/legal/sla/cache/v1_0/). It's possible to disable high availability in an Azure Managed Redis instance. This lowers the price but results in data loss and downtime. We only recommend disabling high availability for dev/test scenarios.
 
 ### Other pricing considerations