0
votes

I am facing a very weird scenario as I did not realize it until now.

I am using power automate to create work items when an email is received in the inbox and save attachments in the SharePoint and update the links of these attachments in the existing work item. I created this workflow using my user and in the 'To' field of the email, also gave my email address for testing purposes. After various iterations, I was able to successfully build the sample flow.

Now, what I did not know is, this workflow can only work if I am providing my email address in the 'To' field as this workflow is owned by me. When I updated the workflow to provide a different email address and tested the flow, it failed and gave a timeout exception, It could not detect the trigger.

My problem is:

My real scenario is, we will be receiving email requests in the shared inbox and once we receive those emails, a corresponding work item should be created. In such a case, how can I use power-automate to create work items? Will I need to create this automated workflow on the shared inbox itself by obtaining the user credentials or there is any other alternate way to achieve it?

I saw there is a template available for creating work items with a shared inbox. Here is what it shows, when I try to use this flow.

Error

Thanks,

Bee

1
Hi benz, Not get your latest information, is the answer below helpful for you? Or if you have any concern, feel free to share it here - Vito Liu
Hey @Vito Liu-MSFT, I am still awaiting permissions of the shared inbox to be shared with me, so that I can test the flow. I will keep you posted about the outcome. - benz
Hi benz, If have any achievements, please feel free to let me know - Vito Liu
Hi benz, I just finished the test. I am registered as a user in the distribution list and create the flow via my account, it will create work item when the distribution list receives the email. In addition, I try to add another distribution list member as the owner of flow and update the flow connection. The flow still work. By the way, the work item creator seems still show the first user account. - Vito Liu
Hi benz,Glad to hear that your problem has been solved. You could accept it as an Answer, so it could help other community members who get the same issues and we could archive this thread, thanks. For the latest question, To or CC field contain To, if we configure the distribution list in the To filed, It will not work if someone send email and CC the distribution list. This is my test result, I recommend that you can raise it to the Power Automate Community, They will give you a detailed explanation. - Vito Liu

1 Answers

1
votes

When you use your account to issue any Outlook REST API request or when you use any Outlook functionality in Microsoft Flow, you may receive the error message: REST API is not yet supported for this mailbox To fix this issue, use one of the following options, as appropriate for your situation.

  1. Migrate your mailbox account
  2. Wait for your mailbox to update, or request a developer preview account
  3. Upgrade your Office 365 plan

Please refer this link for more details: "REST API is not yet supported for this mailbox" error for request to a mailbox

As a workaround

  1. Use your account create the flow-> open the flow and edit the tab owners, then add the shared inbox as owner

  2. Login Power Automate via the shared inbox-> click My flows and select Team flows->open the flow and edit it->click the button "..." and add new connection->enter the shared inbox email and password, then change the Original Mailbox Address to shared inbox.

  3. Then it will create work item In the Azure DevOps when the shared inbox receives an email

Update1

The distribution list has email address Steps: Expand the flow When a new email arrives and enter the distribution list email to the field To or CC, then it will create a work item when the distribution list receives an email.

when an email request with a particular subject

We can configure the field Subject Filter to do this.

enter image description here