MS Teams via Export API: replacing the SSL certificate.
book
Article ID: 100058812
calendar_today
Updated On:
Description
Description
The Microsoft Teams integration with the Webhooks connector and Export API requires a self-signed certificate. This certificate must be uploaded to Azure. The certificate has an expiration date, and if it is not updated, the connector will be unable to retrieve data, but the connector saves his history point and the data is stored on the Microsoft side, thus, as soon as the certificate will be replaced, the connector will continue capturing the data starting from the last successful run. To change the certificate please follow the below steps.
- Create a new self-signed certificate.
- Export it from the MMC (Microsoft Management Console) in .CER Base 64 format.
- Upload it into Azure (The steps on how to upload it are described in the User Guide)
- This step is variable, and you can choose the option that suits the company more.
In Merge1 there are two ways to upload the certificate
- The first option will be using Local Machine. Here, into Merge1 UI type the certificate’s thumbprint, and make sure that the certificate is installed into the Merge1 hosting machine (the machine where Merge1 is installed)
- The second is upload to certificate into the Merge1 in PFX format. In this scenario, there is no need to have a certificate installed in the Merge1 hosting machine, but to upload it into Merge1 UI it is necessary to have a self-signed certificate in PFX format with its private key.
Issue/Introduction
MS Teams via Export API: replacing the SSL certificate.
Was this article helpful?
thumb_up
Yes
thumb_down
No