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

Probably sorted by now, but I found a fix after dozens of searches - by going /help/classic view. Everything came back, POP3, IMAP, disallowed accounts (run by and paid for through microsoft) even the pst's and ost's, calendars etc...

So, so, so simple. And yet impossible to find.

Very poor form Microsoft - and all the MS 'tech support' - rubbish.

I think everyone is missing the point. Microsoft is moving to restrict the use of their software and services to require the exclusive use of outlook.com email addresses with no exceptions other than shelling out a huge pile of money for enterprise level services.

Supposedly browsers are doing away with third party cookies to eliminate user tracking. Now if all of your OS users are forcibly locked into your email services you can offer guaranteed user identity to advertisers for a price.

"Give us the email address, or mobile number, of our users and we can provide you with their complete history."

This concept has been sold to consumers as way to protect our privacy. It's a lie. It's nothing more than extorting third party advertising networks to pay them for user tracking.

If you haven't noticed yet...the new outlook client only works by requiring you to give Microsoft Cloud services complete access to your email account, then you use your microsoft account in order to view your email that has been consolidated into a single inbox after it has been processed, cataloged, and searched by their servers. And do not forget that your microsoft account has been associated to your real world identity with a credit card and mobile phone number.

End-to-end encryption is starting to look even more appealing every day.

Did I miss something?

I'm gonna toss my name into this hat as well. I'm having an issue with only two basic license-planned emails giving this error, all others have added just fine. I've never changed the settings to block these emails to not accessing the new Outlook. If I add them on the old Outlook, ALL of the emails add no issue. If I add them to ANY other email client, they work just fine. Outlook needs to admit this issue is on their end and fix it. The fact that only a couple of my paid-for business accounts can't be added, but any free one can make no sense.

I will continue to encourage my team to NOT use the new Outlook until they decide to make it a mandatory thing, and then we may look into going to a different provider for our email services if this isn't resolved. Do better Outlook.

Wow, that's easy and straightforward. My grandmother could probably set her email up with ease. I have a better idea, why doesn't MS fix their terrible email client so it works like all the 3rd party email clients that actually do work. I'm not bashing you, and I appreciate you trying to help. This is just absurdity to the nth degree. If I ran my business like MS handles email, I'd have no business in a couple of weeks.

If you have the extra mailboxes you wish to add are part of the same company you could use permissions to add them to outlook.

I know one issue with permission-based mailboxes such as shared mailboxes is that they don’t work the same way in Outlook when compared to a full mailbox but a work around for this would be to apply the permissions via power shell and is the auto mapping option is turned off.

This will mean you would have to add the account to Outlook manually just like adding a full mailbox, the only difference is when it prompts for the user password you can select the option to sign in with another account and then use your main mailboxes log in information.

The Permission based mailbox is now set up to work the same way as a standard mailbox in Outlook with its own OST file and it uses your Office application license.

This method also helps with 2FA set up for generic email addresses and not all users will need to be added to the generic account 2FA as they will use their own account to access the mailbox.

If it would help here is a guide I set up for my staff on how to do permission based mailboxes via Power shell, Ir can only be done by 365 Admins

If you have never ran the PowerShell commands for Exchange from a PC you first have to install the Power Shell module by running the following command in PowerShell

Install-Module -Name ExchangeOnlineManagement

Click Y to all question

Now you need to set your user to allow scripts to run from Power Shell by running the following command

Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser

Now you can connect to PowerShell using the commands below and next time you can skip this part

To connect PowerShell to your Office 365 Email Exchange:

Open Powershell (Run as an admin)

Type the following commands

Import-Module ExchangeOnlineManagement

Connect-ExchangeOnline

It will then prompt for 365 admin log in details

To add a user without auto mapping use the following command changing the (MailboxIdentity) to the mailbox address and the (UserIdentity) to the user who you want to access the mailbox, the brackets are not required.

Add-MailboxPermission -Identity (MailboxIdentity) -User (UserIdentity) -AccessRights FullAccess -AutoMapping $false

Look at the example below to see how it should be formated, the red and blue is just to make it easier to see what needs changing

In this example full access permissions are added to Kathleen mailbox with automapping disabled for the admin account.
So admin@ has full access to view all of Kathleens emails but wont add to Outlook by itself.

*Add-MailboxPermission -Identity ******@contoso.onmicrosoft.com -User *****@contoso.onmicrosoft.com -AccessRights FullAccess -AutoMapping $false

The power shell will display the following to show it has worked

Identity             User                                                       AccessRights                 IsInherited           Deny
--------               ----                                                        -----------                     -----------             ----
KathleenR        (DCServer)(AdminSAMAccountName)        {FullAccess}                       False              False

Repeat the previous steps for every mailbox where the user has full access permission and you want to disable automapping for the mailbox

If the users had auto mapping permissions then remove them via the web UI befor adding them via power shell again.

Once the permissions have been added it will show in the web UI against the full access permissions but only power shell can tell you if it has auto mapping enabled or disabled