If you want to make the MetaSwitch Commportal web interface available inside of Teams - in the branded Teams Application you build - this is possible with a few key steps.
Configure, Build and Deploy the Teams App
The details about building the Teams App can be found here. As seen in the image below, the CommPortal URL should be entered into the Website URL entry in the App Management page. It can also be included on the App Templates page if it will be applied to multiple Enterprises).
The CommPortal interface will be displayed in an iFrame inside the Teams App. This requires that certain settings be set up as documented by Microsoft. Our platform arranges to deploy the app so that it conforms to these requirements. There are certain settings that also must be changed by a Metaswitch administrator on the CommPortal app configuration to allow the web page to render properly.
Specifically, as documented, the Content-Security-Policy header must include teams.microsoft.com *.teams.microsoft.com *.skype.com so that our server is allowed to access the pages. In practice, this header might include additional values and might appear in the HTTP response like
Content-Security-Policy: frame-ancestors 'self' teams.microsoft.com *.teams.microsoft.com *.skype.com;
Please contact your Metaswitch support organization if these settings are difficult to locate.
Configure any Access Control Lists to allow access from Teams.
If you have Access Control or firewall restrictions, contact us to determine the correct IP address(es) to allow.
When correctly configured, the CommPortal login page should appear in the End User Portal tab in the Teams App.
You may only need to sign into the portal once if you check the Remember Me box on the login page.
