HTTP with Azure AD - some help please.

[Anonymous]

So I thought that this would be an easy way to call Microsoft Graph from Microsoft flow and it is however...

I can utilise https://graph.microsoft.com/v1.0/me
And it returns the expected result. However utilising https://graph.microsoft.com/v1.0/me/messages throws a 403 “error access denied”

I entered https://graph.microsoft.com for both the Base Resource URL and Azure AD Resource URI (application ID URI)

I have also tried https://graph.microsoft.com as the Base Resource URL and entered a URI for a registered app within Azure with the required permissions.

In both cases I get a result for /me but not for /me/messages

Can someone shed some light on this?

[v-xida-msft]

Hi @Anonymous,

Could you please share a screenshot of your flow's configuration?

The 403 error message told that you don't have enough permission to access the requested resource, please check if you have provided proper Bearer access_token as the authorization for your request.

Please check and see if the following article would help in your scenario:

https://powerusers.microsoft.com/t5/Microsoft-Flow-Community-Blog/Generate-an-Azure-OAuth2-0-Token-from-a-quot-service-quot-Flow/ba-p/61979

More details about 403 forbidden error, please check the following article:

https://developer.microsoft.com/en-us/graph/docs/concepts/errors

Best regards,

Kris

[Anonymous]

I have exactly the same issue (using Azure Logic App).

Has it been resolved yet?

Could you please share a screenshot of your flow's configuration?

I don't know how to attach a screenshot. My flow is reduced to the bare minimum.

Step1: Trigger- When a new mail arrives.  I logged in using my own credentials.

Step 2: Invoke an HTTP request (Preview). I again logged in using my credentials and connected with https://graph.microsoft.com/

The 403 error message told that you don't have enough permission to access the requested resource, please check if you have provided proper Bearer access_token as the authorization for your request.

The step does not have the possibilty to add a separate access_token.

The links you referred to unfortunately do not provide the solution.

[mr-dang]

Are you still having issues with this connector? I was able to set it up using this information:

Then going to https://aad.portal.azure.com, be sure to click "Grant Permissions" or get your IT person to do this if the permissions you selected are okay--only select the minimum needed for your task. That might be the issue with your current authentication right now.

[GabrielStJohn]

Hello, @Anonymous!

Have you had a chance to apply @mr-dang‘s recommendation to adapt your Flow? If yes, and you find that solution to be satisfactory, please go ahead and click “Accept as Solution” so that this thread will be marked for other users to easily identify!

Thank you for being an active member of the Flow Community!

-Gabriel

Microsoft Flow Community Manager

[Anonymous]

@mr-dang - can you update your solution with the current version of the Azure Active Directory admin center?  Looks like the world has changed a bit since your screenshot 🙂

[ChenYung]

Hello,
I am trying the Crisis Communication sample app. In Power Automate connection, I was unable to fix the connection. I tried login but nothing working. May I know what's wrong?

[VictorIvanidze]

The screenshot shows you cannot sign in. Did you try to use another account (another connection)?