The main differences between Zabbix 5.0 and 7.0 for Telegram integration are:
Zabbix 5.0
- Requires a custom script to enable HTTP proxy support for Telegram notifications[3]
- The `HTTPProxy` parameter needs to be added manually to the `media_telegram.xml` or `media_telegram.yaml` file[3]
- The script must include logic to check for the `HTTPProxy` parameter and configure the HTTP request accordingly using the `CurlHttpRequest` method[3]
Zabbix 7.0
- Telegram integration with HTTP proxy support is included out-of-the-box, no custom script required[1][2]
- Supported features include personal and group notifications, with Markdown, HTML, and MarkdownV2 parsing modes[2]
- Limitations include no graph sending (waiting for ZBXNEXT-5611 feature) and no emoji support[2]
So in summary, while Zabbix 5.0 required additional manual configuration and scripting to enable HTTP proxy support for Telegram, Zabbix 7.0 includes this functionality natively. However, some limitations around graph sending and emoji support still exist in the latest version.
Citations:[1] https://www.zabbix.com/rn/rn7.0.0
[2] https://www.zabbix.com/integrations/telegram
[3] https://gist.github.com/CHERTS/04a0905d53c136ee8d5a81c4af93bc9d
[4] https://www.zabbix.com/rn/rn7.0.0alpha5
[5] https://github.com/CHERTS/zabbix_telegram_webhook/blob/master/HOW-TO-USE-HTTPPROXY.md
[6] https://sbcode.net/zabbix/media-types-telegram-webhook/
[7] https://www.zabbix.com/documentation/current/en/manual/introduction/whatsnew700
[8] https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/telegram/media_telegram.yaml?at=release%2F6.4