Am receiving "REST API is not yet supported for this mailbox" on configuring outlook flow
What kind of flow are you gong to create with Outlook.com? Have you already created a connection to Outlook.com?
I can create a flow using Outlook.com without an error message, such as below:
This happens for mailboxes that have not been migrated to O365. Your mailbox is likely still on a dedicated exchange server. You'll need to request your Outlook administrator migrate your mailbox.
Documenation on how this can be done by an administrator can be found here: https://support.microsoft.com/en-us/help/2798131/how-to-migrate-mailbox-data-by-using-the-exchange-a...
I don't see any of below options Sign in to the Office 365 portal (https://portal.office.com).
Click Admin, and then click Exchange.
Click Migration, click New (), and then click Onboarding.
The reason you don't see these options is likely because you're not an administrator of the tenant. This is likely not something you'll be able to do on your own. I'm not sure who that would be in your case, but if you're in a large organization it's likely someone in the IT department that needs to handle this migration.
Some companies may have internal tools that allow you to do this yourself, but I'd start with contacting an IT administrator.
One further option that actually just lit up is the Send email action:
This doesn't require an outlook account, as the mail will come from "Microsoft PowerApps and Flow". I had some problems with this going to my spam folder, so you may need to be cognizant of that.
Would this solve your problem, or does the mail need to come from your account?
This use case is not about sending an email from outlook account or power flow account.
The use case that am trying to set up is about creating a VSTS work item upon receiving an email in outlook. Let me know if am not clear with the scnerio.
Since you're internal to Microsoft, we have tooling to perform this migration for you. I've PMed you details about this.
For those external to Microsoft, the steps in the documentation I provided will need to be performed by a Tenant/Outlook administrator (likely someone in the IT department).
In my case, this error occurred for only 1 user. Found that the user executing the Flow did not have the E1 license yet. Updated license and flow ran fine.