In my previous blog, I guided you through how Power Automate and AI prompts can work together to automatically create ADO (Azure DevOps) work items. If you missed that go check it out: Azure DevOps Work items made easy with Copilot and Power Automate 

In this blog I will demo how you can create a new copilot and show you how you can create a new work item and get a work item with Copilot.

Create a new custom copilot

Go to https://copilotstudio.microsoft.com/

At the side pane click on ‘Create‘:

SpongYe_0-1719177069448.png

For demo purposes I click on ‘New Copilot’:

SpongYe_1-1719177165439.png

Skip to configure:

SpongYe_2-1719177230743.png

Fill in a Name ‘ADO Assistant’ and click ‘Create’:

SpongYe_5-1719178091669.png

In this blog I will explain the working bot with the Azure DevOps.

If you have any questions about Security and Authentication send me a message.

You are ready to configure the actions for the bot.

Configure actions

Click on Actions:

SpongYe_4-1719177682935.png

Click on ‘Add an action’:

SpongYe_6-1719178252005.png

Action: Azure DevOps – Create a work item

Search for Create a work item and select the action:

SpongYe_7-1719178388214.png

The correct connection and for authentication select User Authentication:

SpongYe_8-1719178524697.png

I left the Configure setting as default:

SpongYe_9-1719178571444.png

To configure the inputs I changed the Organisation and Project to Set as Value and let the others a user inputs.

SpongYe_10-1719178745736.png

Review and click Finish:

SpongYe_11-1719178776247.png

Now the action will be ready to use. 

For demo purposes I will not add this here but the same has to be done for the Action: Azure DevOps – Get work item details.

Publish and test your copilot!

Test your Copilot

SpongYe_0-1719179988029.gif

Conclusion

All Azure DevOps actions can accomplish this. However, the blog only demonstrated two functional actions. Feel free to comment and let me know how this can be useful for your next project!

Leave a Reply

Your email address will not be published. Required fields are marked *