cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Ad0m
New Member

Flow condition not picking up the 'TO' email address based on a Shared Mailbox Alias

Hello. 

 

Will try to keep this simple. 

-------------------

Trying to achieve: 
-------------------

A single Shared Mailbox - has multiple aliases i.e. 

 

A  automated system sends a report to an e-mail address for each client's respective e-mail addresses  (i.e. the Aliases) 

e.g. :
SYSTEM SEND MAIL to CLIENT1@DOMAIN.COM -> Flow picks up Alias and Drops attachments into CLIENT1 SharePoint Document Library

SYSTEM SEND MAIL to CLIENT2@DOMAIN.COM -> Flow picks up Alias and Drops attachments into CLIENT2 SharePoint Document Library

------------------------------
Problem
------------------------------

I add the condition to say,  IF CLEINT1 alias, send attachment to SharePoint DOC Library CLIENT1  (and the same for CLIENT2) 

 

But the Flow fails and says the condition is FALSE.   

My thinking is that the condition disregards the alias and just sees the primary email address for the Shared Mailbox i.e. it only sees clientreports@domain.com and therefore the condition fails.  

To prove this I used the "initialize variable"  for the Dynamic content TO address and ran a test, the TO address shows the primary email and not the alias that I originally sent the email to. 

------------

Question 
------------
I guess the question is: Is there anyway to create an expression that ensures it reads the ALIAS email address and not the primary shared mailbox email address?  

 

I've posted some screenshots with my findings - and can get it to work if I don't use a shared mailbox with aliases.
i.e. If I use my own email address with an alias works - but not on a with a Shared Mailbox. 

Thanks to any one reviewing this!
--------------------------------------------------------------
Note: In this image, the initialize variable I used only so I could see what TO address was being picked up:

FlowAliasAddress.png

 

Result from Test: 
FlowAliasAddress2.png

3 REPLIES 3
v-litu-msft
Community Support
Community Support

Hi @Ad0m,

 

You could have a try to set the To field in the trigger to alias1@domain.com, if any match, the trigger will run.

If it could work, you could create two separate Flows for two alias.

https://docs.microsoft.com/en-us/connectors/office365/#when-a-new-email-arrives-in-a-shared-mailbox-...
Annotation 2020-07-01 144245.jpg

 

Best Regards,
Community Support Team _ Lin Tu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Hey @v-litu-msft 

 

Thanks for coming back. 


I have tried this - I have created 2 flows and made them real simple 

  • When a new email arrives in a shared mailbox --> create file in SharePoint Site/Library

on both flows I add the different alias's in to the TO box (like in your print screen) - Then, when I send an e-mail to either of those aliases, I get the attachment saved to both SharePoint locations. 

 

Hence why I put the "initialize variable" to capture if the TO field was in fact being picked up - but it seems as though, no matter what I put in the TO field, the result is the same, it only picks up the Shared Mailbox primary email address and not the alias I asked it to.  

(if that makes any sense at all 🤔

Many thanks 

Adam

AndrewDeitering
New Member

@Ad0m, did you ever figure this out?  I'm running into essentially the same issue and I'm not having much luck finding any other info on it.

Helpful resources

Announcements
MPA_User Group Leader_768x460.jpg

Manage your user group events

Check out the News & Announcements to learn more.

Community Connections 768x460.jpg

Community & How To Videos

Check out the new Power Platform Community Connections gallery!

Welcome Super Users.jpg

Super User Season 2

Congratulations, the new Super User Season 2 for 2021 has started!

Carousel 2021 Release Wave 2 Plan 768x460.jpg

2021 Release Wave 2 Plan

Power Platform release plan for the 2021 release wave 2 describes all new features releasing from October 2021 through March 2022.

Top Solution Authors
Users online (1,209)