SAP Builders Discussions
Join the discussion -- ask questions and discuss how you and fellow SAP Builders are using SAP Build, SAP Build Apps, SAP Build Process Automation, and SAP Build Work Zone.
cancel
Showing results for 
Search instead for 
Did you mean: 

RPA SMTP Mail Destination Configuration with OAuth2Password for Microsoft 365?

stefanusz
Explorer
561

UPDATE : 23 May 2024 - In case anyone is reading / searching for the same thing, I've got a confirmation from ticket that this is a known bug and being worked on. 

 

Hi everyone, 

Have anyone succesfully manage to configure SMTP mail server with OAuth2Password base on the information below? This is for microsoft 365 account. 

https://help.sap.com/docs/build-process-automation/sap-build-process-automation/configuring-smtp-mai...

I've registered the app within Entra ID and give the correct permission (base on my current assumptiong). Testing the scope, client id and secret via postman seems to be okay (it returns the token). 

f6018d83-c97e-4094-a661-076b8956ba62.png

However testing within BPA lobby is showing authentication issue. I'm trying to figure out if there is a missing configuration or is there something wrong within the test mail function? 

#sbpa #irpa #bpa #automation

2 REPLIES 2

Manas_Vincit
Active Participant
0 Kudos
323

I have similar issue with setup . Are you able to figure it out correct setup in Entra ID ? I have also one issue while switching to Basic authentication to Oauth2password Destination does not appear in Mail server(Backend Configuration) in Lobby area. Have you faced such issue?

0 Kudos
284

Hi Manas, 

At the moment it has not been fully resolve for my side. 

I'm still in a conversation with SAP support regarding this and last advice was needing to enable SMTP AUTH, however due to it being a legacy way to connect, I'm having some challenges to enable that due to company policy that I'm working at. 

You can use / build notification within the automation itself and that's working as expected on my end. The one within an automation uses the more up to date authentication call via the agent. 

If you go with oauth2password, it might not appear due to how you grant the API permission within Azure, it needed to be Application instead of Delegation type and the Azure admin need to grant that (if that is not the case for your end at the moment).