Skip to content

Commit 7ea22c8

Browse files
committed
Putting under restrictions section
1 parent cfaee83 commit 7ea22c8

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/iot-edge/iot-edge-limits-and-restrictions.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -53,10 +53,6 @@ IoT Hub has the following restrictions for IoT Edge automatic deployments:
5353
* 100 deployments (including layered deployments per paid SKU hub)
5454
* 10 deployments per free SKU hub
5555

56-
### NTLM Authentication
57-
58-
IoT Edge does not currently support network proxies that use NTLM authentication. Users may consider bypassing the proxy by adding the required endpoints to the firewall allow-list.
59-
6056
## Restrictions
6157

6258
### Certificates
@@ -109,6 +105,10 @@ Changes made in `config.toml` to `edgeAgent` environment variables like the `hos
109105

110106
When using Node.js to send device to cloud messages with the AMQP protocol to an IoT Edge runtime, messages stop sending after 2047 messages. No error is thrown and the messages eventually start sending again, then cycle repeats. If the client connects directly to Azure IoT Hub, there's no issue with sending messages. This issue has been fixed in IoT Edge 1.2 and later.
111107

108+
### NTLM Authentication
109+
110+
IoT Edge does not currently support network proxies that use NTLM authentication. Users may consider bypassing the proxy by adding the required endpoints to the firewall allow-list.
111+
112112
:::moniker-end
113113
<!-- end 1.1 -->
114114

0 commit comments

Comments
 (0)