Hello @Jamie Fraser ,
The client being disconnected by Azure IoT Central approximately every 5 or 10 minutes and the presence of TLS Encrypted Alerts followed by FIN packets it suggests that the Shared Access Signature (SAS) token expiry time is the root cause.
Azure IoT Central uses SAS tokens for device authentication. These tokens include an expiry time (expressed as the number of seconds since the Unix epoch). If the SAS token has a short duration , Azure will gracefully disconnect the client once the token expires, even if the client is still actively sending telemetry.
Ensure that the SAS token generated on the client side has a longer expiry time . The maximum supported duration is 365 days, but you can safely start with at least a few hours (e.g., 3600–86400 seconds) for testing.
If you are not generating the SAS token yourself (e.g., the client is using a third-party stack), ask your client-side team or vendor to verify or extend the token duration.
Reference this MSDOC for more details :
- Azure IoT Hub Authentication using SAS
- Troubleshooting MQTT disconnects
- Create a rule and set up notifications in your Azure IoT Central application
Please don’t forget to click “Accept the answer” and “Yes” if the information helped you. This can be beneficial to other community members facing similar issues.
If you need further clarification, feel free to reply in the comments.