How to Configure UltraDNS Push Notifications for Microsoft Teams

Hello everyone,

I'm excited to share a new way to stay updated on DNS changes directly within your Microsoft Teams channels using Workflows! By leveraging UltraDNS's push notification functionality and AWS Lambda, you can receive notifications whenever changes and events occur, ensuring you never miss critical updates. Check out the GitHub link below:

https://github.com/vercara/udns_ptt

Setting Up Your Integration

First, you’ll want to set up the webhook in Microsoft Teams. Head to your channel, click on the "..." to access more options, and select "Workflows." Here, you can create a new workflow using the template "Post to a channel when a webhook request is received." This workflow will generate a unique URL that your AWS Lambda function will use to send notifications to your channel.

Next, create a new Lambda function in AWS, selecting Python 3.x as the runtime. Enable the function URL, but instead of using AWS-specific authentication, you will restrict access to specific IP addresses. These are the IP addresses of our push notification servers, which you can find listed in the UltraDNS user interface. This ensures that only requests from these IPs can invoke your Lambda function. Upload your function code packaged in a .zip file and set the environment variables.

Now, let's link everything back to UltraDNS. In your UltraDNS account settings under "Notification Settings," add a new notification endpoint using the Lambda function URL you set up. Here you can also choose which DNS change events should trigger notifications, customizing the alerts to meet your needs.

If Things Don't Go as Planned

If you run into issues, make sure the webhook and Lambda URLs are correctly configured. If you're using IP whitelisting, double-check those settings. And don't forget, AWS CloudWatch is your friend for diagnosing any problems with the Lambda function.

Looking Ahead

Should you encounter any issues, first ensure the webhook and Lambda URLs are correctly configured. Also, confirm the IP whitelisting settings are accurate. For further diagnostics, AWS CloudWatch logs can be a useful resource to help identify and resolve any problems with the Lambda function.

We Want to Hear From You!

How has your setup gone? Share your experiences and any improvements you've made. Your insights help us all learn and grow. And if you've developed any tweaks or additional features, consider sharing them on our GitHub or right here in the comments.