If you are attempting to integrate Teams into the Cireson Portal but are finding that the Sign-In button in Teams is unresponsive, you may need to configure additional settings related to URL header translations .
Validation
To confirm that this issue is what you are facing, head on over to MS Teams and hover over the Please Sign In button in the bot itself.
As seen in the screenshot, the sign in link is pointing to a .local site. This is not going to be able to be reached by MS Teams, so we will need to make some adjustments.
Note: The instructions shown here apply to the Azure App Proxy method of making your Portal URL publicly available. If you are using a different method, some of the same principals apply, but the method will differ.
Azure App Proxy
If you are making the Cireson Portal publicly accessible via Azure App Proxy, go to your Enterprise Application and open the settings for the Cireson Portal Application
Go to Manage -> Application Proxy tab
Ensure the "Translate URLs in Headers" option is set to "No"
Note: If you are using an alternate redirect method for your public-facing URL, ensure that headers are not being translated between the public and private addresses
Confirmation
Send another message to the bot to generate a new sign in button. Hover over the new Sign-In button once this is configured.
If the URL is a valid, external facing URL, you should be able to proceed with signing in.
If you are still having issues, please contact the Cireson Support Team @ https://www.cireson.com/contact