Graph API

(1) Share

Report

Posted on by srduval

1,760 Moderator

I'm trying to hit the rooms end point with Graph API. From the graph explorer site, I am able to query that endpoint, but from power automate, I am not. I'm using the HTTP With Entra ID preauthorized connection. Is there another action i need to be using or something else I'm doing wrong? I tried creating a new connection, but it didn't work
This is the action

Connector
HTTP with Microsoft Entra ID (preauthorized)
Operation note
Invokes an HTTP endpoint.
Learn more
Connector type
Shared
Tags
None

This is the "raw inputs"
{
"host":{
"connectionReferenceName":"shared_webcontents",
"operationId":"InvokeHttp"},
parameters":{
request/method":"GET",
request/url":"https://graph.microsoft.com/v1.0/places/microsoft.graph.room"

}

from Graph Explorer
Graph Explorer | Try Microsoft Graph APIs - Microsoft Graph

https://developer.microsoft.com/en-us/graph/graph-explorer

Categories:

Building flows

Screenshot 2025-0...

I have the same question (0)

All responses (6)

Answers (0)

Suggested answer

Michael E. Gernaey 53,429 Super User 2025 Season 2 on at

Like (0)

Report

Hi @srduval

Use the HTTP Connector

How to use Microsoft Graph API in Power Automate - Beginner Tutorial

if this solves your problem please mark the answer as such and maybe a like.

Thanks!

Was this reply helpful? Yes No
Suggested answer

Riyaz_riz11 3,878 Super User 2025 Season 2 on at

Like (0)

Report
Hi,

Step 1: Use the Correct Connector Action

Use the “Invoke an HTTP request” action under HTTP with Microsoft Entra ID (preauthorized).

Do not use the basic HTTP connector or “Send a Microsoft Graph HTTP request”—those are either limited or require manual token management

Step 2: Set Up the Preauthorized Connection

When you insert the action, you'll be prompted to create/configure a connection. You must input:

Base Resource URL: https://graph.microsoft.com/

Microsoft Entra ID Resource URI: also https://graph.microsoft.com/ .......

If the connector was created without those values, delete it and recreate in the classic editor .

Step 3: Grant Graph Permissions

The underlying Microsoft-managed enterprise app needs proper Graph scopes (like Place.Read.All, Place.ReadWrite.All, etc.). You may see a 403 Forbidden even after connection if scopes haven’t been admin-consented

✔ Workaround: Ask a Global Admin to:

Go to Azure AD > Enterprise Applications

Find the service named something like "Power Platform HTTP with Entra ID"

Under Permissions, grant admin consent for required Graph scopes.

Wait ~1 hour for the change to propagate techcommunity.microsoft.com+3rishandigital.com

Step 4: Configure the Action

Once connected with proper access:

Method: GET

URL: https://graph.microsoft.com/v1.0/places/microsoft.graph.room

You don’t need to supply Authorization headers—they’re handled by the connector. If you get 403 or Insufficient privileges, go back and ensure the admin has consented to needed scopes.

Alternative: App-Only with Custom Connector

If the preauthorized method fails or you prefer app-only (daemon) authentication:

Register an Azure AD App

Assign Application permissions (e.g., Place.Read.All)

Generate a client secret or certificate

Either:

Use HTTP (premium) action + manual token fetch (client credentials flow)

Or create a custom connector pointing to Graph using OAuth

If I have answered your question, please mark it as the preferred solution ✅ . If you like my response, please give it a Thumbs Up 👍.
Regards,
Riyaz

Was this reply helpful? Yes No
srduval 1,760 Moderator on at

Like (0)

Report

Thanks @Riyaz_riz11 & @Michael E. Gernaey, I did all that and just now recreated the connection in the classic editor to make sure and still get a 403 forbidden error. I am able to successfully run the same API from the graph explorer, which when I first found the end point I was not able to run it in the graph explorer, so I requested and was given admin consent for it. So i know that I should be able to access it, but it seems PA isnt running the SSO correctly, although i am able to hit the users endpoint successfully.

I don't think this is my problem, where the graph connection needs to be given permissions as it looks like i'd have the issue creating the connection not running the call. So I suspect I am missing a scope permission (which if so why can I query it in graph explorer) or flow is trying to access the places endpoint under a different user name
HTTP With Microsoft Entra ID - Connectors | Microsoft Learn

Screenshot 2025-0...

Screenshot 2025-0...

Was this reply helpful? Yes No
Suggested answer

srduval 1,760 Moderator on at

Like (0)

Report

A work around for this issue appears to be using a beta endpoint:

https://graph.microsoft.com/beta/me/microsoft.graph.findRooms()

Was this reply helpful? Yes No
Michael E. Gernaey 53,429 Super User 2025 Season 2 on at

Like (0)

Report

Hi @srduval

Thank you for coming back.

Agree it can be the scope but the only reason using the beta would work is if the action doesn't exist on the 1.0. I am not sure thats the case.

So changing nothing but the URI fixed your issue?

Was this reply helpful? Yes No
srduval 1,760 Moderator on at

Like (0)

Report

@Michael E. Gernaey that's correct. Nothing else changed. I can still run the original call from the "try it" page at MS using the same account in the same environment. So I have the correct permissions, unless there is some other layer in-between power automate, graph and the API endpoint that's not being allowed through.

Was this reply helpful? Yes No