Views:

Please refer to this Microsoft document for the details on the new licensing and payment models for Teams APIs.

Due to this change, TMCAS will provide a new way to provision for Teams Chat with the customer’s own registered app.

The following table summarizes the licensing models defined by Microsoft and the supported Cloud App Security protection under each model.

ModelLicensing and Payment RequirementsSupported Cloud App Security Protection
Model A
  • An appropriate Microsoft 365 E5 license
  • Payment to Microsoft when the API usage exceeds the upper limit
  • Scan messages and files.
  • Block or pass messages and files upon detecting risks.
Model B
  • Payment to Microsoft for each API call
  • No license required
  • Scan messages and files.
  • Pass messages and files upon detecting risks.
     
    Blocking messages or files is not supported
     
Evaluation ModeNo license or payment required
  • Scan messages and files.
  • Block or pass messages and files upon detecting risks.
     
    As this mode provides limited API calls, TMCAS can scan and take action on only a limited number of messages and files.
     

Important

If you have already provisioned Teams Chat in the old way without creating your own app in TMCAS, it will only scan and take action on a limited number of messages or files once Microsoft’s new licensing models are enforced.

For the meantime, TMCAS protection for Microsoft Teams Chat is unaffected. However, we are not sure when Microsoft will start to take action on the API call throttling yet.

Trend Micro recommends that you update the provisioning to access the new licensing models to avoid any API call throttling and continue TMCAS protection. The new provisioning process is now available in TMCAS production console.

Follow the user guide to upgrade the provisioning for Team chat