Automating the toil - Part 5

Today's automation: Collect Microsoft Form submissions, and put them into a specific Azure DevOps work queue

Why?

Being an operational team, we have a lot of daily contact with other teams needing support. This was done by a shared mailbox, but this has problems with:

• Tracking progress
• Tracking time spent
• Keeping comms in one place to allow for easy handover
• Archiving old/completed work

So, I automated the process. Of course. ;)

This means that any incoming work is visible to the team as soon as it arrives. It also lets the submitter know we've got it - and gives them a link to it if they need to add further detail, like attachments or screenshots.

How?

• This flow watches for submissions from a specific Microsoft Form. Note that this assumes you've setup the form already.
• It retrieves the details (i.e. the actual form field data filled in).
• It then makes an ADO ticket out of them - with a specific parent Epic, and custom tags set to clarify what kind of work this is. Note that this is important for identifying and running ADO queries on this kind of incoming work.
• Then it posts a message to the submitter, saying we've received it, providing a link to it on our board, and stating our SLA.
• Simultaneously it posts a message in our shared group chat telling us that this new request has been submitted into the queue.