office365api

I have a simple web app that for the past month or so the following was working: outlook.office365.com/api/beta/Me/userphotos('120x120')/$value but now it returns: {"error":{"code":"RequestBrokerOld-ParseUri","message":"Resource not found for the segment 'userphotos'."}} I get the same error if I try any of the following: https://outlook.office365.com/api/beta/Me/userphoto https://outlook.office365.com/api/beta/Me/userphotos https://outlook.office365.com/api/beta/Me/userphoto/$value It is possible that my organisation has changed something to cause this? Or has there been a general change in

Where I am right now? I have subscribed to calendar notifications via office365's REST API. When any event in that calendar are created/updated/deleted office365 sends notification to my app's endpoint which I assigned when I created this subscription. Subscription code works like a charm and notifications are coming immediately. I really want to make my code error tolerant and here comes the problem: what happens if notifications are coming in non-incremental order? For example if someone first creates event and then removes it. Can those notifications come in opposite order? 1. remove event,

I'm trying to load data from Office365 email without need for user interaction. I've created Azure App and I have Client ID and Client secret. I also have user information (email + password). I need to call Office365 API to download emails from mailbox. But I need application to download them in background without user interaction (redirecting to MS/Office365 login page) to get authenticated/logged into mailbox. Is there any way how to do this only through Office API, without need of redirection? Thanks for any info. Yes, you are able to create a daemon service app using the Client Credential

I'm using office 365 mail Microsoft Graph API , trying to create new message following the Doc: https://developer.microsoft.com/en-us/graph/docs/api-reference/beta/api/user_post_messages POST https://graph.microsoft.com/beta/me/messages Content-type: application/json { "subject":"Did you see last night's game?", "importance":"Low", "body":{ "contentType":"HTML", "content":"They were <b>awesome</b>!" }, "toRecipients":[ { "emailAddress":{ "address":"AdeleV@contoso.onmicrosoft.com" } } ] } { OUTPUT: "@odata.context":"https://graph.microsoft.com/beta/$metadata#users('ad787b4f-1fda-4523-8e48

Occasionally when sending an email through the Office365 API, we get an error back: excerpt: {"httpCode":503,"headers":"HTTP/1.1 100 Continue\r\n\r\nHTTP/1.1 503 Service UnavailableX-MS-Diagnostics: Routing Validation; Mailbox database change detected; moved from database 31f16b42-8c32-43a3-a05f- f554bb4c579f to 78f2e7a1-e65f-4148-8be4-b98ac0635fdf\r\nX- BEServerRoutingError: Mailbox database change detected; moved from database 31f16b42-8c32-43a3-a05f-f554bb4c579f to 78f2e7a1-e65f-4148- 8be4-b98ac0635fdf"} Does anyone know why this happens,its annoying when the client thinks your app is