Categories About Us Contact Us Become a Member

How to fix “the service provider does not support it” in Outlook

This means you tried a PST operation on an account type that does not support it, such as IMAP or Outlook.com. Using a supported account or a local PST resolves it. Jump to your situation below or work through the methods in order.

By Neeraj Singh ~6 min Updated Jun 2026 87% found this helpful
Error message
Could not complete the operation because the service provider does not support it.
Summary

The error could not complete the operation because the service provider does not support it appears when you attempt a PST import, export or local-database operation against an account type that does not support it, typically an IMAP or Outlook.com account. Those account types do not use the local MAPI database in the same way Exchange and Microsoft 365 do, so certain PST mapping operations are not available. The fix is to perform the operation against a supported account, an Exchange, Microsoft 365 or POP account, or to export to a local PST first and then work with that file. Using a classic Outlook profile that fully supports PST operations also resolves it. In short, route the operation through an account or file that supports the local PST database rather than directly against the unsupported provider.

What this error means

Outlook talks to different account types through different providers. Exchange and Microsoft 365 use the full MAPI database that PST operations rely on, while IMAP and Outlook.com providers do not expose all of that. The error means the operation you asked for is not available on that provider.

So the fix is not to force the operation but to route it through something that supports it. Performing it against an Exchange, Microsoft 365 or POP account, or exporting to a local PST and working with that file, gives the operation the local database it needs.

Common causes

The operation was run against an IMAP account.
The account is an Outlook.com provider that lacks the feature.
The provider does not support local PST database operations.
A PST mapping action was attempted directly on an unsupported account.
Expert insight

“This error is Outlook politely saying that account type cannot do what you asked. IMAP and Outlook.com accounts do not use the local PST database the way Exchange and Microsoft 365 do, so some PST operations simply are not available on them. The trick is to not fight it, route the job through a supported account, or export to a local PST first and then work with that file. Done that way, the operation has the database it needs and just works.”

How to fix it

Method 1

Use a supported account type

1Perform the operation against an Exchange, Microsoft 365 or POP account rather than IMAP or Outlook.com.
2These use the local database the operation needs.
3Retry the import or export there.
Method 2

Export to a local PST first

1Export the data to a local PST file, then perform the operation on that file.
2Add the PST via File, Account Settings, Data Files if needed.
3Work with the local PST rather than the unsupported account.
Method 3

Use a classic Outlook profile

1Classic Outlook with a profile that fully supports PST handles these operations.
2Switch from New Outlook to classic for the import or export.
3Then complete the operation.
Method 4

Reconfigure the account if appropriate

1Where supported, add the mailbox as an Exchange or Microsoft 365 account instead of IMAP.
2This exposes the full set of PST operations.
3Then retry.

This error means the account type does not support the PST operation, common with IMAP and Outlook.com. Route the job through a supported account (Exchange, Microsoft 365 or POP), or export to a local PST first and work with that file. A classic Outlook profile that fully supports PST also resolves it.

Frequently asked questions

What does the service provider does not support it mean?
It means you tried a PST import, export or local-database operation on an account type that does not support it, typically IMAP or Outlook.com, which do not use the local PST database the same way.
How do I fix it?
Run the operation against a supported account such as Exchange, Microsoft 365 or POP, or export the data to a local PST first and then work with that file.
Why does IMAP cause this?
IMAP and Outlook.com providers do not expose the full local MAPI database that certain PST mapping operations require, so those operations are not available on them.
Can classic Outlook help?
Yes. A classic Outlook profile that fully supports PST handles these operations. Switch from New Outlook to classic to perform the import or export.
Should I export to a local PST?
Yes, that is a reliable workaround. Export to a local PST file, then perform the operation on that file rather than directly against the unsupported account.
Can I reconfigure the account?
Where the mailbox supports it, adding it as an Exchange or Microsoft 365 account rather than IMAP exposes the full set of PST operations and avoids the error.

Still not working?

If a supported account and a local PST both still report the operation as unsupported, the specific action may not be available in your Outlook build at all; checking Microsoft's documentation for that operation, or using the classic Import/Export wizard, clarifies what is supported. You can also submit your error to us for a tailored fix.

Was this fix helpful? Thanks for your feedback!