office365api

I'm having some trouble figuring out how to use the office365 api to fetch messages given a conversationId . Let's say my conversationId is AAQkADlkOGJmMTFmLTc2NjMtMKL3My04ZDhkLTVmZWNjMzA1ODY0NAAQAB11Xh2opSpBiXifMEJjhow= I'll make a request like https://outlook.office.com/api/v1.0/me/Messages?$filter=ConversationId%20eq%20AAQkADlkOGJmMTFmLTc2NjMtMKL3My04ZDhkLTVmZWNjMzA1ODY0NAAQAB11Xh2opSpBiXifMEJjhow= This results in a 400 response like this: { "error": { "code": "RequestBroker-ParseUri", "message": "Syntax error at position 98 in 'ConversationId eq

Is it possible to set up a single "Native app" which can be used by users on different Azure accounts/directories so they can get data from their Office 365 Sharepoint Online? We can get this working using a "Web app" because in the Azure portal where you set this up it has the "Multi-tenanted" option which can be set to Yes - the notes for this support this: Designates whether users in external organizations are allowed to grant your app access to data in their organization's directory. This control affects only the ability to grant access. It does not affect any access that has already been

I am developing an outlook plugin.I want use one drive API's in it.I easily got the client Id and client secret for using API's for one drive personal accounts.But, when I registered my application for one drive business API's in azure active directory, it created only a client Id for me, but didn't create any client secret.I chose native app while registering, as my app is a native app.I can't authenticate the user without the client secret.Please let me know , how to get the client secret?Thanks in advance. Native clients don't have any secrets associated to them - given that they are meant

Stuck here writing JS code to send out an email via REST within a custom Outlook add-in. Scenario is following report \ \---- another message (item attachment) \ \------- attachment (file attachment) In words, I am sending a new report message which includes another message as an Item Attachment (that works fine). But now, the problem is that, when sending with another message that has attachments, then this fails. Opening the report which has the other message attached doesn't show the attachments. Query is POST https://outlook.office365.com/api/v2.0/me/sendmail Returns 202 Accepted Body is

Recently we've noticed that the Microsoft Graph API has been returning file attachments as message entities returned from the /me/messages endpoint. The scenario to reproduce is as follows: Send yourself an email (or have someone else send you an email) with one or more file attachments Run the following query in Graph Explorer: https://graph.microsoft.com/v1.0/me/messages Notice that there will be one object which represents the email itself (this is correct behaviour) and one or more objects which are representations of the file attachments. It's also worth noting that these attachment