ErrorMissingEmailAddress error in Outlook REST API - outlook-restapi

I am developing an app to retrieve mail/calendar information. I am using the App model v2.0 OAuth2 and the Outlook REST API. I have a personal Live (...#live.nl) account which can use the outlook.com web interface to view mail/calendar data.
When I use the same account with Outlook REST API I get the following error (also in OAuth Outlook Sandbox) while doing this request:
https://outlook.office.com/api/v2.0/me/mailfolders/inbox/messages?$top=10
"error": {
"code": "ErrorMissingEmailAddress",
"message": "When making a request as an account that does not have a mailbox, you must specify the mailbox primary SMTP address for any distinguished folder Ids."
}
What is the cause of this error and how can it be solved ?

You are receiving this error because your account hasn't yet been upgraded yet to Office 365 infrastructure and this is required for the REST APIs to work. You can confirm this by logging into outlook.com and see "Outlook.com" in the top left corner. If you have been upgraded, you will see "Outlook Mail (Preview)" instead. We are in the process of deploying a fix to v2.0 endpoint return a more informative error for this case - MailboxNotEnabledForRESTAPI.
We are actively upgrading all accounts to Office 365, so no action needed from your side. In the meantime, to request an Outlook.com developer preview account with the REST APIs enabled, send us an email at outlookdev#microsoft.com.

Related

This Account lacks sufficient permissions. Account lacks permission to send Envelopes over SMS

We are working on integrating e-signing over SMS feature with our application using the Docusign APIs. In the production account, it gives this error:
This Account lacks sufficient permissions. Account lacks permission to send Envelopes over SMS.
We have enabled Allow SMS delivery to recipients in 'Sending Settings' of eSignature Admin .
Our existing 'Embedded' and 'Remote (over email)' esigning operations are working fine.
Only with this new SMS feature, we get above error.
We are also sure that our account supports SMS. Our older plan had embedded + email + API support. We upgraded recently for SMS.
Let me know if any other information is needed
I would suggest opening a case through our support center and check if this feature is enabled. It may be the case where is in your plan but is not enabled

Purchase SendGrid Twilio Email Activity Feed API when using Azure Resource Groups

I want to be able to see the status and activity of an email through SendGrid API. There is a help page for getting started with the Email Activity Feed API however it says i need to purchase history. Purchasing is controlled through the Azure web portal which has completely different pricing tiers from the normal SendGrid portal. It also has no option for purchasing the Activity History as the documentation indicates i should do.
I've tried making the purchase through the SendGrid Portal, but it seems to be blocked for my account. It says "You don't have permissions to view this page. You can request access from your account administrator." even though I created this resource.
Is this API even available to Azure users?

Email bouncing back with error code 550 5.7.708 Service unavailable

we have an application that is using the Outlook REST API v2 to allow the users to send emails from the app.
Today one of our clients send us a bug report, that after they created a new Office365 account for their company they can't send emails through our app. The current case was for sending email to hotmail.com account. The email bounces back with error code
550 5.7.708 Service unavailable. Access denied, traffic not accepted
from this IP.
The user also reports that they are able to send the same email from the Outlook web client.
I have found this issue on the network: https://social.technet.microsoft.com/Forums/ie/en-US/608d046b-755a-4264-8cdd-fc34c72ccf8f/office-365-tenant-blacklisted-on-all-emails-sent-by-ms-outlook-2016?forum=onlineservicesexchange and am now wondering if this is just a bug on Outlook side or we have missed something on our end?
You have to go here: https://sender.office.com/ and put the incriminate ip to delete it from the list.

Office cloud storage partner program registration

I am traying to make a registration for Office cloud storage partner program
From this link Office cloud storage partner program registration
I get this error "Error: Something went wrong while submitting the form."
When i use the form on this page Office Cloud Storage Partner Program
The form is submitted. But i get no receipt or any other response
Any suggestion for completing a registration
Got reponse from Microsoft one week after sign up. Signede a NDA and now i am up and have now joined the program

Testing the Outlook REST API leads to suspended account issue

I'm trying to integrate Outlook Mail with a web app I'm working on. I need to do some tests with the API during the development. I'm using the node-outlook library in my NodeJS app. However, after sending a few test emails to both real and dummy addresses, I encountered the following error:
"REST request returned 530; body: {"error":{"code":"ErrorAccountSuspend","message":"Account suspended.
Follow the instructions in your Inbox to verify your account., WASCL
UserAction verdict is not None. Actual verdict is Suspend,
ShowTierUpgrade."}}"
It seems that Microsoft detected unusual activity with my account and suspends the account. I followed the directions and verified my account in a process that included mobile phone verification. It seemed the problem was resolved.
Now, I see that I can read the messages through the API, however I cannot use the API to send new emails or send draft emails. Also it seems I cannot send emails in the Outlook web app, too. I receive the same "suspended account" error.
One question is how can I solve this problem? Do any restrictions of "suspended account" error remain in place even after verifying the account and resolving the problem?
Another general question is, how can I do different tests with the Outlook API during development, without causing this "suspended account" error? I did much more tests with the Gmail API without any such problems.

Resources