You’re offline. This is a read only version of the page.
Hello,
created my first Custom Test Connector with a simple wrapper for the Graph API with one simple Action to clone a team
But I'm having trouble with the Scope. The error message is always the same
Share
Report{
"error": {
"code": "Forbidden",
"message": "Missing scope permissions on the request. API requires one of 'Team.Create, Group.ReadWrite.All, Directory.ReadWrite.All'. Scopes on the request 'User.Read'",
"innerError": {
"date": "x",
"request-id": "x",
"client-request-id": "x"
}
}
}
I have done the following:
Now in Postman I have tried the exakt same thing but with Scope "https://graph.microsoft.com/.default" which postman tells me as I get the error Error: AADSTS1002012: The provided value for scope Teams.Create is not valid. Client credential flows must have a scope value with /.default suffixed to the resource identifier (application ID URI)
In Postman the POST REQUEST works as expected as I get a valid 200 Header and with Operations ID
So now how can I make this work in my custom connector ?
What to put in Ressource URL and Scope ?
Many Greetings and thx for the help
Erik
Hi
I am having a very similar issue to the above as well.
In my case I've created a custom connector to post a message to a teams chat, using the code shown in example 5 here https://docs.microsoft.com/en-us/graph/api/chatmessage-post?view=graph-rest-1.0&tabs=http I created the app registration for this connector initially with different permissions and then added the required ChatMessage.Send, Chat.ReadWrite afterwards and the error I get suggests that the connector is not seeing these new rights, only the 2 rights I created the app registration with.
I've tried adding the scopes to in the custom connectors OAuth2 section as mentioned above but that makes no difference.
I've also tried recreating the both the custom connector and flow from scratch and still it doesn't see the 2 chat permissions I've added.
Does anyone have any clues as to anything else I can try here?
Hi there,
It looks like you have commas between your scopes -- based on what I read here, you should only have spaces, no commas. Give it a shot again after updating that and let us know how it goes!
Cheers,
Rhia
#1
DBO_DV
25
Super User 2025 Season 1
#2
CU09051456-0
22
#3
Michael E. Gernaey
21
Super User 2025 Season 1
All responses (
Answers (