GET https://graph.microsoft.com/beta/me/presence (/communications/getPresencesByUserId, /users/{id}/presence)
{
"error": {
"code": "Unauthorized",
"message": "Unauthorized",
"innerError": {
"request-id": "b13dbf1b-16b2-4c41-90ee-103b46d9890f",
"date": "2020-05-27T09:18:43"
}
}
}
Checked in jwt, token has scopes:
"scp": "... Presence.Read Presence.Read.All ..."
Logged in with the same user in Graph Explorer. The response was Forbidden but after giving consent it works fine in Graph Explorer.
Microsoft Graph Explorer will not interact with your application,So you need to provide permissions for Graph Explorer
I use #microsoft/teams-js for authorization. I updated version from 1.5.0 to 1.6.0 and now I have no issues with getting presence.
Related
The GetChat API (https://graph.microsoft.com/v1.0/chats/{chatid}) from Microsoft Graph returns error 403 (Forbidden) for some chats when using application permissions. The application being used has Chat.Read.All permissions with admin consent granted. Also, the same application returns success for other chats.
Following are errors for couple of requests to get chat, that were tried using Postman:
1:
{
"error": {
"code": "Forbidden",
"message": "Forbidden",
"innerError": {
"date": "2021-10-18T13:16:26",
"request-id": "79c2ca6f-5b85-44ed-a3da-ef3607630a41",
"client-request-id": "79c2ca6f-5b85-44ed-a3da-ef3607630a41"
}
}
}
2:
{
"error": {
"code": "Forbidden",
"message": "Forbidden",
"innerError": {
"date": "2021-10-18T13:18:37",
"request-id": "5cfd4f22-8c25-4ecf-aa88-0c0c3df560d4",
"client-request-id": "5cfd4f22-8c25-4ecf-aa88-0c0c3df560d4"
}
}
}
You could try couple of things here -
Try the same API call in Graph explorer and observe if you still see this error. This will help in identifying if there is any issue with the token that you have generated.
You may have changed your API permissions after giving your application admin consent. When you give admin consent, Azure AD will take a "snapshot" of the permissions at the time of consent. Then if you change the permissions later, you will need to re-do the admin consent process again.
Personal accounts are not supported. Refer permissions here.
I'm trying to get the chat messages from MS team channel using API.
https://graph.microsoft.com/v1.0/teams/{team-id}/channels/{channel-id}/messages
It works in graph explorer and returns the list of all chat messages. But when I hit the same API within Postman it return the following error:
I have consented all the required permission in azure app. What else am I missing here. Has anyone faced similar issues?
Please let me know.
{
"error": {
"code": "UnknownError",
"message": "",
"innerError": {
"date": "2021-04-20T04:01:46",
"request-id": "e32d3a2e-001c-4478-8c9c-8d5ff0c5e125",
"client-request-id": "e32d3a2e-001c-4478-8c9c-8d5ff0c5e125"
}
}
}
list channel messages is under protected API in MS teams. Before calling this API with application permissions, you must request access. To get the access you have to apply request access form
I am trying to add user using Microsoft graph API.
I have provided the consent for all the permissions required.
POST https://graph.microsoft.com/v1.0/users
Request body that is send to the post request.
{
"accountEnabled": true,
"displayName": "Adele Vance",
"mailNickname": "AdeleV",
"userPrincipalName": "AdeleV#contoso.onmicrosoft.com",
"passwordProfile": {
"forceChangePasswordNextSignIn": true,
"password": "xWwvJ]6NMw+bWH-d"
}
}
Error that is received in response
{
"error": {
"code": "",
"message": "No HTTP resource was found that matches the request URI 'https://outlook.office365.com:444/profile/v1.0/users('CID:0ff49e4749deeaf2')/profile?api-version=AGSV1-internal'.",
"innerError": {
"date": "2021-02-04T10:41:56",
"request-id": "025218e1-191c-464f-adf3-f0cdc5fcebfd",
"client-request-id": "c071d220-2f14-d7fa-956e-cd45ccbdc735"
}
}
}
Is there something that I am missing?
I have also gone through the docs for adding user provided by Microsoft.
https://learn.microsoft.com/en-us/graph/api/user-post-users?view=graph-rest-1.0&tabs=http
What you said in the comment is correct, the document has detailed instructions, it does not support Microsoft personal accounts.
You will have to check the end point are you using to authorize in order to obtain the token.
If you are using a tenant specific end point
https://login.microsoftonline.com/{tenant}/oauth2/v2.0/authorize?
client_id=6731de76-14a6-49ae-97bc-6eba6914391e
Try replacing with the common endpoint
https://login.microsoftonline.com/common/oauth....
I'm using the Microsoft Graph Explorer on the Microsoft Planner (formerly Tasks) API.
I can requests users fine, e.g. /beta/users.
But when I try to access my plans using /beta/me/plans or /beta/plans/{ID}, I get an unknown error with the details below:
Status Code: 403
{
"error": {
"code": "UnknownError",
"message": "",
"innerError": {
"request-id": "62299f57-1792-4b0c-8b60-8613c54f4f50",
"date": "2017-01-17T21:12:51"
}
}
}
I'm trying to query the tasks on a plan that I own.
This API has changed. This URL should be
GET https://graph.microsoft.com/v1.0/me/planner/plans
At this moment I'm working with the personal contacts. But I want to expirment with the Organizational contacts but when I try to do a request to https://graph.microsoft.com/beta/contacts I got this response
{
"error": {
"code": "Authorization_RequestDenied",
"message": "Insufficient privileges to complete the operation.",
"innerError": {
"request-id": "882e70df-d89c-4d9a-a028-cd3ad2e497cb",
"date": "2016-04-13T09:14:21"
}
}
I suspect that I'm missing a persmission scope but the documentation isn't showing any requiered scopes(created a issue for that https://github.com/OfficeDev/microsoft-graph-docs/issues/24.) Does anyone else has expirence with the Organizational contacts
The scope that's needed at present is Directory.Read.All. We are still working out what scope will be required when we move from beta to v1.0.