Content Manager MS Teams Integration

Yes, deploy the new Teams manifest using the latest setup script: https://raw.githubusercontent.com/content-manager-sdk/Community/master/docs/files/24.1/az_install.ps1

Perform the below steps to ensure that Content Manager Teams integration is added to Teams Shared Channel:

1. Sign in to Microsoft Entra ID using a Global administrator or Security administrator account.

2. Select External Identities, and then select Cross-tenant access settings (preview).

3. On the Default settings tab, under Inbound access settings, select Edit inbound defaults.

4. Select the B2B direct connect tab.

5. On the Users and groups tab, under Access status, choose Allow access.

6. On the External applications tab, under Access status, choose Allow access.

7. Select Save.

8. Select the Trust settings tab.

9. Choose if you want to trust multi-factor authentication, compliant devices, or Microsoft Entra hybrid joined devices from other organizations.

10. Select Save and close the Default settings blade.

This is an expected behavior.

Keeping the option enabled helps the user to modify and check in the document to Content Manager without any delay even automatic capturing is configured in Server side filling for the channel.

Yes, it is possible to run two MS Teams apps pointing to different dataset.

However, make sure:

  1. That each of these datasets has its own ServiceAPI instance. You can run multiple ServiceAPI instances from one ServiceAPI installation which would reduce the overhead.

    For more details, see Accessing multiple datasets section in Content Manager MS Teams Integration help.

  2. Choose one ServiceAPI to be your primary instance, this is the one that the Teams integration manifest points to.

    For detailed, see Manifest section in CMxx.x_MSTeams_Integration.pdf document.

To resolve this issue, make sure that authentication for service API is enabled as anonymous in IIS.

To enable anonymous authentication, perform the following steps:

  1. Open IIS manager.
  2. Navigate to Default Web Site > CMServiceAPI. CMServiceAPI home is displayed.
  3. Double-click Authentication available user IIS.
  4. Click Anonymous Authentication and select Enable from the Action panel or right-click and select Enable.

The following log text in the EmailLink logs:

Invoked API requires Protected API access in application-only context when not using Resource Specific Consent.

If you come across the above log message in the EmailLink logs, make sure that your request to access the protected MS Teams API is granted. Otherwise, it is recommended to get in touch with the MS Teams support.