Access the Graph /me/chats endpoint from a flow

(0) Share

Report

Posted on by BenAffleck

Hi,

is it possible to access the Graph /me beta endpoint with delegated permission from within a flow?

I'm particularly interested in the /chats endpoint which none of the standard and premium connectors implements https://graph.microsoft.com/beta/me/chats

Is writing my own connector the only option to achieve this?

Categories:

Using connectors

I have the same question (0)

All responses (6)

Answers (1)

Rohit Sharma354 Microsoft Employee on at

Like (1)

Report
Copy link

Link copied!

Hello,

Yes, based on my research, it looks like custom connector is the available option at this point.

Was this reply helpful? Yes No
VictorIvanidze 13,079 on at

Like (0)

Report
Copy link

Link copied!

Just use the premium connector "HTTP with Azure AD".

Was this reply helpful? Yes No
BenAffleck 25 on at

Like (0)

Report
Copy link

Link copied!

Hello @VictorIvanidze,

Thanks for your response. Have you tried this with success?

I tried this before, and while I can access the graph endpoint in general, I can't access the /me/chats endpoint. I get a 403, which makes total sense to me as this API requires the Chat.Read permission scope, and there is no way to control the scopes when creating a connection for this action. Did I miss something?

I wonder how this whole thing is implemented and how to get more control over it. Any advice? Could you please check what you suggested?

Was this reply helpful? Yes No
Verified answer

VictorIvanidze 13,079 on at

Like (0)

Report
Copy link

Link copied!

Hi again @BenAffleck,

at first please accept my apologies - I made a mistake.
In fact "Invoke an HTTP request" doesn't work.

However, I've just created a custom connector following the instructions from https://docs.microsoft.com/en-us/graph/tutorials/flow
and tested it. It works as it should at least for my own account.

Regards,
Victor

Was this reply helpful? Yes No
BenAffleck 25 on at

Like (0)

Report
Copy link

Link copied!

No worries @VictorIvanidze!

Thanks for testing it. I wanted to make sure that a custom connector is the only option I have.
Furthermore, I assume you did this by using OAuth authentication on the connector, which requires an app registration (clientId and secret).

I was looking for a way to get around this and don't involve tenant administrators. I was looking for a solution that can be entirely done by a citizen developer.

Would you agree that there is no such solution right now? Any other thoughts?

Was this reply helpful? Yes No
VictorIvanidze 13,079 on at

Like (1)

Report
Copy link

Link copied!

>I assume you did this by using OAuth authentication on the connector, which requires an app registration (clientId and secret).
Yes, correct.

>I was looking for a way to get around this and don't involve tenant administrators. I was looking for a solution that can be entirely >done by a citizen developer.
>Would you agree that there is no such solution right now? Any other thoughts?

I do not see other way. I guess somebody from MS developers could inform us.

Was this reply helpful? Yes No