Skip to content

Commit d5184ad

Browse files
authored
Update Max Web Socket Connections
Source code shows we allow a maximum of 100. Correcting docs to reflect that.
1 parent 89c8484 commit d5184ad

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

includes/api-management-service-limits.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ ms.custom: Include file
3636
| Maximum number of [schemas](../articles/api-management/validation-policies.md#schemas-for-content-validation)<sup>10</sup> | 100 |
3737
| Maximum size of request or response body in [validate-content policy](../articles/api-management/validation-policies.md#validate-content)<sup>10</sup> | 100 KB |
3838
| Maximum number of self-hosted gateways<sup>11</sup> | 25 |
39-
| Maximum number of active WebSocket connections per unit | 200 |
39+
| Maximum number of active WebSocket connections per unit | 100 |
4040
| Maximum number of tags supported by an API Management resource|15|
4141

4242
<sup>1</sup> Scaling limits depend on the pricing tier. For details on the pricing tiers and their scaling limits, see [API Management pricing](https://azure.microsoft.com/pricing/details/api-management/).<br/>

0 commit comments

Comments
 (0)