Description

The Microsoft Teams integration with the Webhooks connector and Export API requires a self-signed certificate. This certificate must be uploaded to both Azure and the Globanet Portal. Additionally, it needs to be installed on the hosting machine where Merge1 is running. However, the certificate has an expiration date, and if it is not updated, the connector will be unable to retrieve data.

To prevent this issue, there are two possible scenarios.

The first scenario involves creating a new subscription in the Globanet Portal and a new Azure application, as outlined in the Merge1 User Guide. This should be done before the current certificate expires. Failing to do so would result in a period of time where the old subscription has expired and the new one has not been created, making it impossible to retrieve data due to the limitations of Webhooks and subscriptions.

The second option is to only replace the certificate on the Azure side. The certificates used for Azure and the Globanet Portal can be the same or different from each other. Therefore, when it's time to change the certificate, only the one for Azure should be updated, while leaving the Globanet Portal's certificate unchanged.

It's important not to delete the old certificate from the machine. If the old certificate is deleted, it will be impossible to use the Globanet subscription to capture data.

To replace the certificate on Azure's side, please follow the steps below.

1. Create a new self-signed certificate.
2. Export it from the MMC (Microsoft Management Console) in .CER Base 64 format.
3. Upload it to Azure.
4.  This step is variable, and you can choose the option that suits the company more.

• The first option will be using the Local Machine function. Here, into Merge1 UI type the certificate’s thumbprint, and make sure that the certificate is installed into the Merge1 hosting machine.
• 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.