Why I cant add new email account in new outlook but in old it works?

This is not true. As admin of our email accounts I have NEVER applied a policy to block any version of Outlook. Why not just admit that it is an issue that Microsoft has to fix? I've read elsewhere that Microsoft is aware of the issue and that New Outlook is still in development.

So, if I've never turned off access to new outlook, why can't we add E1 accounts to it? They've worked in every other version of Outlook except this one.

Thanks,

Jessica

It looks like Microsoft wants every Microsoft 365 email account to be licensed for desktops apps in order to work on new Outlook.

On the old desktop Outlook as long as one account is licensed you can use the app for any other account.

This creates the absurd situation where Microsoft have created a version of Outlook where Apple Mail works but not their own paid-for email service.

Companies with more email accounts than desktop app users (e.g. with 'sales' or 'info@' email accounts) are also stung because this set up means a company managing multiple inboxes will now needs to be licensed for desktop apps for each account even though nobody is using the apps.

This isn't going to work. You can't force people to pay extra for what they already had.

Hi, I have the same problem.

I am an admin in my Exchange plan.

I enabled access to the feature and verified the configuration:

❯ Set-CASMailbox -Identity email@***************** -OneWinNativeOutlookEnabled true  

❯ Get-CASMailbox -Identity email@***************** | Format-List Name,OneWinNativeOutlookEnabled 

Name                       : email 

OneWinNativeOutlookEnabled : True  

I still don't have access via the new Outlook app. It still shows the same error as mentioned above.

There are a lot of people reporting the same problem on Reddit: https://www.reddit.com/r/Office365/comments/16nv5sb/adding_e1_account_to_outlook_for_windows_disabled/

I think this should be addressed. The new Outlook does not work with some Exchange accounts.

To help keep us on track, let me summarize what we know:

The problem is not with customers, their laptops, or their company administrators. The problem is not with tenant settings.

The problem is with Microsoft.

Microsoft has made the conscious decision to prevent less-expensive Microsoft 365 licenses from using New Outlook for Windows. If you have an A1/E1/F1/Business Basic/EXO P1/EXO P2 or similar "low-cost' Microsoft 365 license, you will not be able to use it with New Outlook for Windows. Microsoft has officially confirmed that they've made this choice, and they have not provided any explanation as to why.

There are some anecdotal suggestions that some people have made it work. These can be grouped into three categories:

1. People who switched to New Outlook before Microsoft issued the restrictive update seem to be okay for now.
2. People who have copied one or more settings database files or registry entries from a working computer to a new computer can sometimes make it work.
3. People who purchase a more expensive license, then add their account to New Outlook, then downgrade that license, have in some cases reported success.

The reasons for these exceptions seem to be that - at the moment - New Outlook only checks the license when the account is first added to New Outlook. However, all of these workarounds seem unreliable (not everyone can make them work) and none of them are supported. Moreover, if Microsoft continues to pursue this destructive course, it's only a matter of time before they modify New Outlook to do a periodic license check, which will invalidate all of these workarounds and disconnect all of these users. But in ALL of these cases, if you remove the account from New Outlook, you will not be able to re-add it, and if you try to migrate to New Outlook from any other program with any of these licenses, they will not work, and if you buy new licenses for the inexpensive accounts, they will also not work. So these workarounds are not solutions in any real way, they're just some people finding a loophole for a specific case.

It is unfathomable to us why Microsoft is doing this, but we hope to get this reversed. But the only way we can get it reversed is if enough people complain. But it's critical to realize that Microsoft does not participate in this forum, and they are not seeing this thread. The only way to complain about this is to do it in the place where Microsoft actually pays attention, which is in their feedback portal.

To that end, we have created a master feedback item here: https://feedbackportal.microsoft.com/feedback/idea/2f7925cb-3a80-ee11-a81c-000d3ae46fcb . If you are upset about this issue - and you should be! - the best thing to do is to go to that link, and comment and upvote it. They read that feedback, and act on the highest upvote count and highest comment count items. That is the only way to get Microsoft's attention.

And don't stop there. Get your co-workers, get your company administrators, get everyone you know who is a Microsoft 365 customer to go to that same item and upvote it. If we could get many employees from just a few impacted companies to upvote and comment, we could get this on Microsoft's radar much more quickly. The issue is gaining more traction and attention as more people trip over this, but the more votes we can get, the faster the outcome will be.

All of the details of the issue are documented there so, please, if you're reading this, take a moment now to go upvote and comment so that we can get this insanity reversed as quickly as possible.

Thanks,

Glen

I have the same problem. I can add Outlook.com, Gmail and even Apple Mail accounts to the New Outlook Windows app.

I cannot add either of my Microsoft 365 accounts. I get the same error.

I am the admin for my M365 accounts and I've troubleshooted via Exchange Admin Centre and Exchange Online PowerShell. I haven't done anything to block the use of the app.

The problem is inside Microsoft.

Have you seriously launched a new version of Outlook that is compatible with Apple Mail but not Microsoft 365?