Exchange is deprecating Basic Authentication later this year. Will the Email actions be updated to accommodate?

[drake]

Exchange is deprecating Basic Authentication later this year.  The Email actions like Power Automate Desktop, like Retrieve email message and Process email messages, utilize Basic Authentication but I was wondering if the "Exchange" email actions in Power Automate Desktop will still work?

I just need to know the path forward in Power Automate Desktop, for working with IMAP.  Thanks!

[josephb61]

Hi @John_Mavridis

We use the PAD Exchange Connection Actions for the Email Receive, Process, Send Exchange Email actions in all our PAD Flows. 

Please advise if there will be a PAD Release, Before October 1 -  For updating the Exchange Connection Action to support Modern Authentication ?

[Anonymous]

Do we have a solution for this yet?

[jadenkim]

we already got an issue from customer. 

do you have any work around to retrieve email???

[VJR]

@CoralFarmer, @kenseongtan 

request your inputs please, or if you can get an answer from the product team.

[josephb61]

jadenkim,

1.  The MS Exchange Team issued a link that any customer that needs an Extension of Basic Auth, until December 31, can obtain the extension for Basic Auth in the theor Office 365 Tenant.

The Office 365 Global Administrator for your office 365 email account tenant can execute the procedure in the below link to to extend - Basic Auth for Exchange EWS, until Dec. 31, 2002.  It should take effect within an hour of executing the procedure.

... This will get your pad flow working for the short term

2. As microsoft support for PAD has indicated that they will not be supporting the pad exchange actions for modern auth, you can use this tim to re-code all your email PAD flows to use the PAD Outlook Desktop Client Actions (Launch Outlook, receive, send), Of course you will have to ensure you have Outlook installed on your PAD connected machines.  Outlook desktop client 2016 and later will automatically work with Modern Authentication when it is later turned back on for your client.

[josephb61]

Jadenkim,

• Using the below Article Link, from the MS Exchange Team, follow the Procedure Steps we have listed below, to Re-enable Basic Auth, until December 31
  
  
• Steps:
• 1)  Click the Button within the article link which is towards the bottom of the article.  ( This should automatically route you into your Office 365 Admin Center in the Help Support section, if not follow the instructions in the article to position yourself to the appropriate section of the help support area).

2)  Click "Run Diagnostics" and wait for the Progress indicator to Stop and for Field to appear Titled:  "Protocol".

3)  In the Protocol Field, From Drop Down Arrow Select:  Exchange Web Services (EWS)  

4)  Check the Box:  " I acknowledge ...... ".

5)  Click:  Update - Button.

6)  Repeat  - Steps 2 to 5, above, but this time, in the Protocol Field, From Drop Down Arrow Select:  IMAP   ......... If you use, IMAP

7)  If no error message is received, then the Enabling of Basic Auth has succeeded.

https://techcommunity.microsoft.com/t5/exchange-team-blog/basic-authnentication-deprecation-in-exchange-online-september/ba-p/3609437

[josephb61]

Jadenkim,

• Then re-code your pad desktop flows to use the PAD outlook desktop actions, by December 31.

[jadenkim]

thanks for detail reply.

i've done re-enable basic auth according to the guide from message center. 

it's a temporary solution by end of this year.

then how could i re-code pad for retreiving email without imap action?

one thing i can use is outlook client. 

why pad didnt provide actions for exchange online. when will these action be updated....

[josephb61]

From Jadenkim,

"why pad didnt provide actions for exchange online."

.... I would like an answer on this too.

From jadenkim,

"when will these action be updated"

• .... MS support for pad told uz in the 1st half of 2023, after December 31, permament disable of basic auth. They said we need to recode pad desktop flows by Dec 31.

.

[JamesP_MSFT]

Hello all, 

From Jadenkim,

"why pad didnt provide actions for exchange online."

.... I would like an answer on this too.

Power platform provides cloud connectors for Exchange Online automation.

From jadenkim,

"when will these action be updated"

.... MS support for pad told uz in the 1st half of 2023, after December 31, permament disable of basic auth. They said we need to recode pad desktop flows by Dec 31.

Exchange Server and Exchange Online are two separate products. 
Exchange Team is updating Exchange Online to not utilize Basic Auth anymore. 
As explicitly stated in the Designer's tooltips as well as the official documentation, Exchange group of actions is aimed for Exchange Server automation. 
On top of that, Exchange Online was never listed as an option to the "Connect to Exchange" action. 

https://learn.microsoft.com/power-automate/desktop-flows/actions-reference/exchange

The correct approach is to utilize cloud flows, using the appropriate Office 365 connectors for Exchange Online automation. 

Regarding the next steps, Cloud Connectors have already been introduced in PAD (started with SharePoint - currently in preview). We will be introducing more connectors in the future (Office 365 included). 

[josephb61]

JamesP_MSFT,

"The correct approach is to utilize cloud flows, using the appropriate Office 365 connectors for Exchange Online automation. "

• James,
• Do you have an example of passing email body text received in cloud flows to pass into pad desktop flow ?
• Also, for PAD desktop flow that needs to Send email when specific logic is executed in desktop flow, how to trigger cloud flow from desktop PAD to send email for the PAD desktop flow ?

[JamesP_MSFT]

Orchestration takes place through cloud flows. You can use a cloud flow to execute a desktop flow, not the other way around. You can though pass data from one flow to the other (either cloud or desktop). 
Create a desktop flow and setup its input parameters to receive data from other flows. 
So in Exchange's case, utilize the cloud connector in a cloud flow, execute a desktop flow using the desktop flow connector and pass the requisite data from the previous step as data to the desktop flow. 

You can pass data from the desktop flow to a cloud flow by configuring the desktop flow to generate output data. 
Desktop flow will generate the data once its execution is concluded successfully. You can then utilize the data from the caller cloud flow. 

For input/output parameters in desktop flows please see the lessons here: Define input and output parameters in Power Automate - Training | Microsoft Learn

 

[AscendDev]

In regards to this, you can trigger a cloud flow via a desktop flow, not directly, but via an API call

We, like most people have this same issue and we have resolved by using an API connector in PAD to trigger a cloud flow passing the information to the Cloud using parameters in the API call and then using the standard Cloud Outlook connector to send the email.  Its not elegant, but it works

Note, if sending an attachment, you will have to pass the content of the file in the API call

Hope this helped someone