(reposted here from the Get help forum as suggested by Scott Shearer)
There has been a (hopefully) unintended breaking change with the email input field for triggers.
I have a SharePoint (selected file) trigger for a flow that asks for email addresses as input. Up until this week, users where able to input any valid email addresses, including external ones:
Now the field only accepts actual directory users.
This is a breaking change for my process. How is that possible that only internal user's email addresses can be "valid" email addresses in a business process input? Thanks!
I also have this issue and do not want to change every single flow process that takes an email address as input and make it a text field. I will submit a ticket with Microsoft. This is a critical break for us too! It starts off our new hire onboarding process!
I'm not sure how anyone else is getting on with their support tickets but raising mine has proved a waste of time. I was told by the MS support person that sending e-mails to external addresses with any of the manual triggers isn't supported. At first they tried to say it's never been supported but then I showed them some previous runs from a few weeks ago although this didn't seem to convince them fully.
I'm at a bit of a loss now as to what to do. The only alternative seems to be changing the email input to normal text but I can see that causing issues with no input validation etc.
Hi @gjayne84 ,
I think responses largely depend on the person you get at Microsoft. The following is the response I got from the Microsoft Rep that picked up my ticket:
Thank you for reaching out to Microsoft Power Automate support. This is Alex and I will be the Support Professional who will be working with you in this case 2112200010002495.
I am sorry to hear that you are experiencing some difficulties with Power Automate.
Thank you for reporting this as well as providing me the link to the article referencing what you and other users are experiencing.
I would like to let you know that we are currently trying to fix this as soon as possible. This issue has been already identified and we have it marked at the highest priority. I apologize for any inconvenience this is causing. At this time, I do not have an ETA on when it will be fixed but if you want I can notify you once the issue is mitigated.
If you have any further questions, please let me know and I will be more than happy to help!
I look forward to your reply.
@KathyBl wow that is a different response to the one I got but one that is definitely more positive. At least they've acknowledged the issue and hopefully if it's a priority it will get fixed as soon as possible. I'm glad you posted this as I wasn't looking forward to changing all the flows we have that make use of this functionality 😊
Hi, my ticket is also taking KathyBI's turn. It is acknowledged as a bug, they are working on it and they will keep me posted as to when a fix will be pushed. Thanks!
Microsoft response this morning:
From: Alex Bedigian Perez <email@example.com>
Sent: Tuesday, January 4, 2022 9:00 AM
To: ROI IT Support <ITSupport@roihs.com>
Cc: firstname.lastname@example.org; email@example.com
Subject: RE: Prior to this week I was able to enter a no... - TrackingID#2112200010002495
Happy new year!
I wanted to notify you that we’ve finally received an ETA on the work item.
The current ETA is scheduled for January 24th.
PowerApps & Power Automate Support Engineer – Americas Region
Working Hours: 7 AM to 4 PM EST | Mon – Fri
Support Manager: Soledad Gil (firstname.lastname@example.org
The first Microsoft-sponsored Power Platform Conference is coming in September. 100+ speakers, 150+ sessions, and what's new and next for Power Platform.
Learn to digitize and optimize business processes and connect all your applications to share data in real time.
Are you new to designing flows? What is your biggest struggle with Power Automate Designer? Help us make it more user friendly!