Please checkout Part I if you landed directly on this page.
This post is a continuation how to Forms and Power Automate can be used to create an approval workflow to automatically provision a Team. We will see the user’s experience here.
When user submits the Microsoft Form, the approver gets an email.
![](https://acloudguy.com/wp-content/uploads/2022/04/image-84-1024x754.png)
In my scenario, I’m using a service account called ‘Teams admin’ and I can see the email as below,
![](https://acloudguy.com/wp-content/uploads/2022/04/image-69.png)
In the Outlook.office.com, the approver can directly click on ‘Approve’ or ‘Reject’ and also add comments if they wish to.
![](https://acloudguy.com/wp-content/uploads/2022/04/image-79.png)
Once approved, the rest of the flow runs and at the end the user gets an email confirming the Team creation.
![](https://acloudguy.com/wp-content/uploads/2022/04/image-80.png)
User can also launch Teams and check that he is part of the new Team that was created.
![](https://acloudguy.com/wp-content/uploads/2022/04/image-81-1024x476.png)
![](https://acloudguy.com/wp-content/uploads/2022/04/image-85-1024x476.png)
As you can see the ‘Teams admin’ service account is also a owner in the Team it created. This might become an issue during compliance audits and this can be fixed by adding a step in Power Automate with a HTTP request.
The HTTP request option is a premium feature and hence no screenshot here.
DELETE https://graph.microsoft.com/v1.0/groups/{id}/owners/{id}/$ref
This is a short post as most of the inner workings of this process was covered in the earlier one.
Thank you for stopping by. ✌