I did try to research a lot but couldn't find it. I have to set "send as permission" for some users in an Office 365 group mailbox. I have an Office 365 group created and I need to assign the "send as" permission to some users in a group via API. I didn't find this information in the Microsoft documentation. Do we have any other way to make this automated?
As of September 2022, this cannot yet be done through Microsoft Graph. Your only option for automation is to use Exchange PowerShell's Add-RecipientPermission cmdlet:
Add-RecipientPermission "Help Desk" -AccessRights SendAs -Trustee "Ayla Kol"
Related
i want to add a permission to a file on sharepoint online using the Microsoft Graph API.
the special thing is that i want to grant permission to the sharepoint group "visitors of ".
i think the possibility using https://learn.microsoft.com/en-us/graph/api/driveitem-invite?view=graph-rest-1.0&tabs=http is not successful.
thanks everyone
https://learn.microsoft.com/en-us/graph/api/driveitem-invite?view=graph-rest-1.0&tabs=http
tried this with different recipients and roles.
I am using the Graph API with app permission & with a certificate.
I know how to send emails with the sender which is different from the requestor's email.
I go to admin.exchange.com, select the user and add a mailbox delegation then add the user in "Send as".
My question is how to add user with "Send As" option via Graph API only.
I would like use this method microsoft permission: but from graph api
Thanks for your help
No this (and all the other Exchange Admin tasks) aren't currently in the Graph API, the only option for doing this programmatically is to use the Powershell cmdlets https://learn.microsoft.com/en-us/powershell/module/exchange/add-mailboxpermission?view=exchange-ps. The good news is that the v2 Powershell module does now support the client_credentials flow https://techcommunity.microsoft.com/t5/exchange-team-blog/modern-auth-and-unattended-scripts-in-exchange-online-powershell/ba-p/1497387
Does Microsoft Graph API require Microsoft 365 subscription to work with Microsoft To Do task list? I understand a typical outlook.com account comes with a To Do task list for free.
You can go ahead and simply test it on Graph Explorer. According to the overview page of Microsoft Graph To-Do API there is no sign that we need a license.
I have tried testing it by disabling the To-Do Plan 3 of my Microsoft 365 subscription, and it still worked for me.
In searching the Microsoft Graph API documentation I have been unable to find any documentation on any APIs that would allow me to get the "Send as" or "Send on behalf of" settings for an Office 365 mail user.
I'd like to fetch these prior to sending an email so that my application can allow users to choose which emails to send from.
Anyone have any insight as to if this information is behind any of the v1.0/beta graph APIs or whether it is just completely unavailable.
Here's the documentation for how Microsoft informs users how to set up send-as aliases https://learn.microsoft.com/en-us/office365/admin/add-users/give-mailbox-permissions-to-another-user?redirectSourcePath=%252farticle%252fSend-email-from-another-user-s-mailbox-in-Office-365-2B828C5F-41AB-4904-97B9-3B63D8129C4E&view=o365-worldwide#bkmk_sendemailanotheruser
You can find this under the Send Outlook messages from another user section of the documentation.
Two types of permissions apply to sending messages from another user: Microsoft Graph permissions, and mailbox permissions.
I'm trying to use the graph explorer to access the beta Office 365 usage reports. I can see that these report require the "Reports.Read.All" permission and I'm seeing that the account I'm using doesn't have that permission yet, but when I click on the "Modify your permissions" link it doesn't display this permission. How do you add this permission to an account, so that you can use the graph explorer with this API?
The reports.read.all permission has been added to the Graph Explorer code repository at https://github.com/microsoftgraph/microsoft-graph-explorer/commit/093600ec7bc7bd32befe5d118270ea71ca8008b4 and will be deployed to our website in the next update. We're working on a process to get new scopes added to the explorer automatically so we don't have this delay in the future.
You need to be an administrator to be able to consent to that permission scope