Today we can send vRLI Alerts to vROps, we can generate emails on them, and there are out of the box Webhooks for Slack, Pager Duty, and vRO. What about Microsoft Teams? Well, we can create a custom Webhook for it, so what does that look like.
Let's first generate a TEAMs URL to which we will point our Webhook. Go to Teams, select your Team, then go to the three dots top right.
![](https://static.wixstatic.com/media/b4065e_a44c11386dd1473aa3f078a5c250d36a~mv2.png/v1/fill/w_958,h_1019,al_c,q_90,enc_auto/b4065e_a44c11386dd1473aa3f078a5c250d36a~mv2.png)
Select Connectors.
![](https://static.wixstatic.com/media/b4065e_f6efb444756a4a4d8c913cf5fe891123~mv2.png/v1/fill/w_802,h_913,al_c,q_90,enc_auto/b4065e_f6efb444756a4a4d8c913cf5fe891123~mv2.png)
Click Add and then Add which will add the Incoming Webhook to the Channel. We now need to configure it. Go back to the three dots top right and select Connectors.
![](https://static.wixstatic.com/media/b4065e_9530106fd8a74ba28f55c55ded09da70~mv2.png/v1/fill/w_813,h_878,al_c,q_90,enc_auto/b4065e_9530106fd8a74ba28f55c55ded09da70~mv2.png)
You'll notice it shows a Configure button now, select that.
![](https://static.wixstatic.com/media/b4065e_9a307861b78a4ee3a58329d88953ac0d~mv2.png/v1/fill/w_801,h_531,al_c,q_90,enc_auto/b4065e_9a307861b78a4ee3a58329d88953ac0d~mv2.png)
You'll give it a name, adjust the associated image if you want, then click Create. Once you click Create, a URL is generated for you.
![](https://static.wixstatic.com/media/b4065e_abc02019c71f4a7691743c75573fec32~mv2.png/v1/fill/w_810,h_800,al_c,q_90,enc_auto/b4065e_abc02019c71f4a7691743c75573fec32~mv2.png)
This is the URL to which you will send your vRLI Alerts. Click Done. Let's now configure the Alerts in vRLI to be sent to Teams. Log into vRLI, go to Alerts - Webhook and select NEW WEBHOOK.
![](https://static.wixstatic.com/media/b4065e_e57dc81610e4455ea1e390b80560f483~mv2.png/v1/fill/w_980,h_448,al_c,q_90,usm_0.66_1.00_0.01,enc_auto/b4065e_e57dc81610e4455ea1e390b80560f483~mv2.png)
From the Endpoint dropdown, you'll have four options.
![](https://static.wixstatic.com/media/b4065e_ea554b2f5dc14b7cbb4f9c9e2f8f39f4~mv2.png/v1/fill/w_874,h_471,al_c,q_90,enc_auto/b4065e_ea554b2f5dc14b7cbb4f9c9e2f8f39f4~mv2.png)
There are built-in Endpoints for Slack, Pager Duty, and vRO. There is a Custom option for others, like Microsoft Teams. Each Endpoint has its own Advanced Settings and Payload, the Custom Endpoint looks like this.
![](https://static.wixstatic.com/media/b4065e_99b35237ba1243e292b85f58aaaba5dd~mv2.png/v1/fill/w_851,h_831,al_c,q_90,enc_auto/b4065e_99b35237ba1243e292b85f58aaaba5dd~mv2.png)
The Webhook URL is the Teams URL we previously created. Content Type provides the payload format (JSON or XML). Action determines the method (POST or PUT). Authentication is optional and provided via the Authorization fields. You can add Custom Headers if you wish. The payload and its parameters are available at the bottom, this is how you format your message to Teams. Mine looks like this.
![](https://static.wixstatic.com/media/b4065e_403f6ee029654fe3b1eb33796b425d05~mv2.png/v1/fill/w_854,h_833,al_c,q_90,enc_auto/b4065e_403f6ee029654fe3b1eb33796b425d05~mv2.png)
Click TEST ALERT to test the Webhook.
![](https://static.wixstatic.com/media/b4065e_0e12f8d873324ffdb25b92efcf02b5d7~mv2.png/v1/fill/w_954,h_1014,al_c,q_90,enc_auto/b4065e_0e12f8d873324ffdb25b92efcf02b5d7~mv2.png)
As you can see, I've been testing, and my latest test is shown at the bottom. At this point, we can now use the Microsoft Teams Webhook in vRLI Alert definitions. I've created an Alert around the query "failed" using our new Webhook.
![](https://static.wixstatic.com/media/b4065e_eed6425470714e9ba48955aca8f187ab~mv2.png/v1/fill/w_980,h_578,al_c,q_90,usm_0.66_1.00_0.01,enc_auto/b4065e_eed6425470714e9ba48955aca8f187ab~mv2.png)
I've adjusted the Webhook payload to include a link to vRLI, it looks like this.
![](https://static.wixstatic.com/media/b4065e_969ef087e0544eeaacf77e7fc08b0ef6~mv2.png/v1/fill/w_854,h_833,al_c,q_90,enc_auto/b4065e_969ef087e0544eeaacf77e7fc08b0ef6~mv2.png)
We now wait for a "failed" log in vRLI, which we just got.
![](https://static.wixstatic.com/media/b4065e_425440f7e3474cbf9d51ca87dd96d133~mv2.png/v1/fill/w_980,h_587,al_c,q_90,usm_0.66_1.00_0.01,enc_auto/b4065e_425440f7e3474cbf9d51ca87dd96d133~mv2.png)
Which generated a Microsoft Teams message.
![](https://static.wixstatic.com/media/b4065e_ce791c974dae4a808662b15a8e884c79~mv2.png/v1/fill/w_952,h_1013,al_c,q_90,enc_auto/b4065e_ce791c974dae4a808662b15a8e884c79~mv2.png)
Clicking the link in the message takes the user back to the vRLI query. This is just one use case for vRLI Custom Webhooks, they can be used for other endpoints as well. VMware Staff Technical Account Manager Brian Wuchner published a nice video on this same topic, you can see it here. For more information on vRLI and vRLI Cloud, go here.
Comments