Issue with Microsoft 365 – Outlook VBO

[Anonymous]

Hi,

we are facing an issue with HTTP request by Send Mail with Microsoft 365 – Outlook.

Authenticate works fine because we a Auth Token (AccessToken) back when we use our TenantID, ClientID and Client Secret.

But when we go futher the process we get a error in Utility - HTTP when we do the HTTP request.
The error is:

{"error":{"code":"InvalidAuthenticationToken","message":"Access token is empty.","innerError":{"date":"2022-11-17T13:26:30","request-id":"507dcf7a-db97-4f38-9f10-df1bf5a4952a","client-request-id":"507dcf7a-db97-4f38-9f10-df1bf5a4952a"}}}

Could anyone please help me on this and let me know what caused this error?

Thanks in advance...

Regards,

Patrick

[ewilson]

@Patrick Meijer,

You're using an older version of the Utility - HTTP VBO that doesn't support adding a bearer token to the Authentication header. Download the latest release of the VBO from the following link:

​https://digitalexchange.blueprism.com/dx/entry/3439/solution/utility---http

Cheers,
Eric

[Anonymous]

@ewilson Thanks for your help.

I have imported the latest release of Utility - HTTP VBO and now sending an email works.

Only this works when I run the process from studio and does not work when I run the process from the control room. Then I see the following messages in the process log:

Stage Name: Get Auth Token - Client Secret
Result: ERROR: Internal : Could not run the object because one of the code stages has a compile error, use Check for Errors for a list of problems

Stage Name: Microsoft 365 - Outlook::Authenticate
Result: ERROR: Internal : Could not run the object because one of the code stages has a compile error, use Check for Errors for a list of problems

Do you have any idea what could be causing this?

[ewilson]

@Patrick Meijer,

When you try to run your process from Control Room are you running it on a different Runtime Resource than your local dev machine? If so, I’d say you’re missing the MSAL DLL that’s required by the underlying MSAL.NET VBO.

Cheers,
Eric​

[Anonymous]

@Eric Wilson ,Thanks again.

When I run the process from Control Room I'm running it on a different Runtime Resource than my local dev machine.
I forgot to place the MSAL DLL on the Runtime Resource.
Now it works both ways.

[AmasaNareshKumarReddy]

Hi @ewilson 

I am also facing similar issue but slightly different. 

Microsoft 365 – Outlook.

Authenticate works fine because we a Auth Token (AccessToken) ,TenantID, ClientID  but  when tried to read list of folder , send a mail , i am getting below error. definitely i am using updated version of HTTP VBO.  and from IT team , he showed me some power shell script and ran it in his machine and with this info he was able to fetch the folder info.   please help me on this.Status Code: 403 Result: {"error":{"code":"ErrorAccessDenied","message":"Access is denied. Check credentials and try again."}}

Thanks,

Naresh.

[stepher]

Naresh,

I believe your issue is related to the Azure-side setup (he said like he had a clue what that means).  In our rollout of the Outlook365 VBO, I had the exact same issue.  Going back through my email, there is a section of the documentation I highlighted for our Azure team, related to Delegated Permissions and Allow Public Flows (it was section 15/figure 12 from the version that I was using).

The Allow Public Flows was a point of contention.  In the end, what I sort of remember happening was that they created a separate security group for the two email addresses that we were concerned about, and then worked with the Application Permissions.  It worked, but it had some odd downstream effects.  Primarily that I can no longer access these accounts as a delegate.  This probably means that there are other issues as well, but the less I know the better off I am.

Good luck,

Red

[AmasaNareshKumarReddy]

Hi @stepher 

Thanks for your insights.  this issue was exactly resolved after these set of permissions was enabled by Microsoft Azure team.

Regards,

Naresh.

[AmasaNareshKumarReddy]

I have gone through these references and shared with Azure teams , later they enabled the permissions.

https://stackoverflow.com/questions/75650693/microsoft-graph-apis-access-is-denied-check-credentials-and-try-again

https://learn.microsoft.com/en-us/graph/api/mailfolder-list-messages?view=graph-rest-1.0&tabs=http#permissions

Thanks

Naresh.