A short post about a new use case. I was asked to implement my ProPlus channel update script in a PROD environment. I was provided with an Azure Automation account. Looking at it, I saw that it did not have a Run As account. The customer did not want to allow an Azure Automation Run As account, as it per default gets Contributor role to the entire subscription. It can be scoped down with RBAC, but a decision was made to try to avoid it altogether. Fair enough, I had to take another look at my script.

I have shared some scripts in my earlier posts. However, as I run the scripts in Azure Automation, I made some adjustments in the versions I use in my setup.

UPDATED: June 2021: Microsoft changed channel names and URLs causing the script to fail. Updates have been implemented to ensure the functionality works with the changes by Microsoft. Please use the latest version in GitHub.

This is part IV of the series Teams message cards.

This is part III of the series Teams message cards.

Microsoft Teams has become an important part of the everyday worklife. It is a great collaboration tool for companies, providing files, chat and telephony. To extend even further, it provides a lot of possibilities for integration with other services. Incoming webhooks is a way to integrate with other services, for example to present information.