> The only option there would be to create a new, public-facing server, set it up with a domain name and SSL certificate, expose it to the world, and then give

> The only option there would be to create a new, public-facing server, set it up with a domain name and SSL certificate, expose it to the world, and then give it access to those services - which defeats the point of having those services internal and secure if we just create a non-internal system and give it access to them. That's not the only solution -- you could also develop a bot that will do those specific things. In the days of yore I know of at least three companies that were using IRC bots to similar effect long before webhooks ever existed. Because of that prior experience, this is how I currently manage a similar set of problems, albeit not on Teams in my current role.