It is unlikely that the account that I'm using to call Graph API doesn't have adequate permissions, but whenever I modify proxyAddress property of a Office 365 Group, I receive the following error,
{
"error": {
"code": "Authorization_RequestDenied",
"message": "The requesting application is not authorized to set group proxy addresses.",
"innerError": {
"date": "2022-01-17T12:01:39",
"request-id": "328be4b4-eb20-483e-adf7-bb02dfae3be2",
"client-request-id": "cabb604f-b315-be14-9ba0-9b0571ba7b1b"
}
}
}
If I PATCH without modifying the proxyAddress property at all, then I don't get this error, but whenever I modify the payload for proxyAddress at all, I get this error.
Example, PATCH:
{
"proxyAddresses": [
"SPO:SPO_269b2269-296d-43f4-b67e-88b6f32a7fcd#SPO_af6dd7da-54b5-411e-bab8-0b31f96e9e42",
"smtp:twg35#lincdev.com",
"SMTP:twg35aaa#lincdev.com",
"smtp:twg35#linc.onmicrosoft.com",
"smtp:twg35aab#lincdev.com"
]
}
I can change other properties and I can successfully set proxyAddress when I create the group, but updates always fail with error. Also, I've tried updating the mailNickname property and this has no effect. I can also update this value from the Office 365 Admin UI by modifying the email (primary / alias) and accomplish exactly what I'm after.
Can someone confirm that this isn't possible via Graph API or can you confirm / help me with the process or permission to accomplish this?
According the documentation group proxyAddresses is read-only property. It cannot be updated.
Related
When attempting to update a Planner Plan's group using PATCH, updates to the owner field fail with 403. The attempt is being made using the Graph Explorer (and also fails using PostMan).
An attempt to change the title field succeeds (no issue with permissions, using eTag, etc.) for the call.
The documentation indicate Groups.ReadWrite.All are required, and that the owner can only be changed by the Group Owner, but the account being used is the owner of the unified group.
Are there any additional permissions required?
Example info:
If-Match: W/"JzEtUGxhbiAgQEBAQEBAQEBAQEBAQEBARCc="
PATCH https://graph.microsoft.com/beta/planner/plans/Vk_27olfLESU6vWJNgzVT2UABrBj
BODY:
{
"title": "Updated plan with new group owner",
"owner": "0ab4b389-7c7c-4757-ac75-2ba5de8c8197"
}
RESPONSE:
{
"error": {
"code": "",
"message": "You do not have the required permissions to access this item, or the item may not exist.",
"innerError": {
"request-id": "7696b78c-474f-4fc0-bba9-4554bfe303c4",
"date": "2018-11-14T16:50:59"
}
}
}
The documentation in this case is misleading/incorrect (it is trying to say the field owner can only be updated by the principal identified by the value of the owner field, which is a group that cannot actually perform operations, not the owner of that group). We'll update the documentation and clarify.
We currently do not allow Plans to be moved between groups, as some of the related items mostly live within the group itself (e.g. membership, comments, document links). We'd like to understand your scenario better to see if we could support it, so please provide feedback on https://planner.uservoice.com.
We are trying to integrate SPOnline in our product for which we need cancel checkout.
I saw the
https://graph.microsoft.com/beta/sites/<siteid>/drive/items/01QLNXZVV4M75S2HYNTBF32HGY3ZZ6MAGT/discard
api but it is giving
{
"error": {
"code": "BadRequest",
"message": "Unsupported segment type. ODataQuery: sites/<siteid>/drive/items/01QLNXZVV4M75S2HYNTBF32HGY3ZZ6MAGT/discard",
"innerError": {
"request-id": "a3e5a861-3dd6-47a2-b111-fc9087a07b03",
"date": "2018-06-08T03:51:30"
}
}
}
Is there any way we can cancel a checkout using our code?
Also another issue which I saw was if I checkout file from user "A" in a different org then a user "B" in another org is not able to see the checkout. It appears in the UI but the api ?select=publication gives status published to user B? Is it as designed or an issue?
I'm not sure where you got /discard from but there is no such endpoint in Microsoft Graph.
You can revert a file to a previous version using /restoreVersion but there is currently not a method to simply "undo" or "discard" a /checkout. You would need to /checkin in order to unlock the file and then restoreVersion to back out any bump in the version number.
I am attempting to create an upload session in the special app folder for my OneDrive app using the Graph API. My app have the following permissions:
Files.ReadWrite
Files.ReadWrite.AppFolder
offline_access
The request looks like this
https://graph.microsoft.com/v1.0/users/xxxxxx96-2e02-4300-8ab0-a05d73xxxxxx/drive/special/approot:/documentname.docx:/createUploadSession
gives the following error:
{
"error": {
"code": "itemNotFound",
"message": "The resource could not be found.",
"innerError": {
"request-id": "7447aa01-6685-4af0-998a-64abc9b14825",
"date": "2017-04-06T10:07:46"
}
}
}
I can create an upload session on the normal root folder without any errors:
graph.microsoft.com/v1.0/users/xxxxxx96-2e02-4300-8ab0-a05d73xxxxxx/drive/root:/documentname.docx:/createUploadSession
result:
{
"#odata.context": "https://graph.microsoft.com/v1.0/$metadata#microsoft.graph.uploadSession",
"expirationDateTime": "2017-04-06T10:32:48.5252565Z",
"nextExpectedRanges": [
"0-"
],
"uploadUrl": "......."
}
The createuploadsession method does not support special/approot. As mentioned in the documentation, these are the only paths to use:
POST /drive/root:/{path_to_item}:/createUploadSession
POST /drive/items/{parent_item_id}:/{filename}:/createUploadSession
Just wanted to clarify, since people are sometimes referring to this thread still: This syntax actually is supported. Due to the flexibility of OData syntax/support, the docs are not always 100% comprehensive about every request path that works.
I believe the actual issue is that Files.ReadWrite.AppFolder is not supported on ODB/SPO/business accounts yet (as of 2022) - it is only for personal/MSA accounts. However, there is work in progress to bring this support to SPO in the future.
The two scopes that are mentioned above are:
Files.ReadWrite - grants access to content on the caller's mysite only
Files.ReadWrite.AppFolder - has no effect on SPO/business
Files.ReadWrite.All should work in the short term, until Files.ReadWrite.AppFolder is implemented on SPO/ODB.
I am attempting to update the responsibilities field on a user account through the Graph API.
I am attempting to do this using the following request:
PATCH https://graph.microsoft.com/v1.0/users/<upn>
{
"responsibilities":[
"ApprovalLimit:0"
]
}
When i make this request, I get the response:
{
"error": {
"code": "-2147024809, System.ArgumentException",
"message": "Invalid attribute update\r\nParameter name: attributeUpdates",
"innerError": {
"request-id": "1be313f3-880b-47de-858d-1bea74951715",
"date": "2017-03-06T09:29:21"
}
}
}
However, when I attempt to update the schools collection, which is also a String collection, this works without issue.
This is the same with both beta and v1.0 and also with the /me endpoint rather than /users/<upn>.
Is this a bug within the API?
Any ideas about how to set this?
Thanks in advance.
I am also able to reproduce this issue too. Based on the error message, it seems this attribute is not support update at current version of Microsoft Graph.
If you want to this attribute is update-able, I suggest that you submit the feedback from here.
I've encountered a problem while trying to update organization's properties using Microsoft Graph API. I've followed these docs and tried it in graph explorer.
My request looks like this:
{ "displayName": "My Company Name" }
Whatever I do I always get the following error:
"error": {
"code": "Request_BadRequest",
"message": "Specified HTTP method is not allowed for the request target.",
"innerError": {
"request-id": "dfd9ae19-2774-4b10-8d74-f6f6cd21f712",
"date": "2016-05-16T14:48:02"
}
}
What am I doing wrong?
I have tried in my test tenant and results in the same error.
https://graph.microsoft.io/en-us/docs/api-reference/v1.0/resources/organization
In the above document it is mentioned that we can update "marketingNotificationMails" and "technicalNotificationMails" properties alone through Update API. So I think you can't update the organization display name.
It does appear as though updates are limited on the organization entity. Please file a request to Uservoice to ask for this feature.