You're not alone — I had the exact same reaction when I reviewed the permissions.
Reading all groups, teams, channels, and members across the tenant seems way beyond what's necessary for a Teams integration focused on ticket updates or agent communication.
In a larger company, it's a real issue too — security policies often won't allow granting that level of access, especially when it's tenant-wide and not limited to a specific scope.
It definitely raises data privacy, compliance, and security concerns that need a very solid justification.
I'm also hoping Freshworks can clarify why these permissions are needed, or if there's any plan to offer a version with more limited permissions.
It would make a big difference in getting approvals to actually use the bot.
Would love to hear if anyone from Freshworks can weigh in here.
We were looking to turn this functionality on, however these permissions seem too broad. It would be nice if they would allow us to select what we could allow and have more control instead of “Read User Full Profile”.