Use of own domain name with Office 365 Home/Premium

IT IS SAD! Every time my O365 acct or my domain or email hosting comes up for renewel, I look for a better, cheaper solution. Its going to show itself sooner or later and MS will see huge losses of Home users.

I do not think that there is a huge number of Home users that ask for family domains, so I do not think there is huge loss there. It is a minority.

I have found alternative solutions to both online storage, email, calendar and address book. What is stopping others from doing that?

IT IS SAD! Every time my O365 acct or my domain or email hosting comes up for renewel, I look for a better, cheaper solution. Its going to show itself sooner or later and MS will see huge losses of Home users.

There are no issues in adding whatever mail account to Office 365 Home, its all dependent on who hosts the domain & mail server

It appears that some posters are trying to add their domain/mail as an alias in an outlook.com mail account, which is where any problem would arise.

Sorry. You're completely missing the point here.

What people want is to have the MS Office mailservers accept mail for their domains. No one wants aliases. No one wants boxes residing at external 3rd party providers.

There is NO way to appoint the O365 home Exchange server to be the mail server for an external domain.

What is possible right now is some kind of an "IMAP sync".  Meaning:

• DNS MX entry points to a 3rd party provider where the IMAP boxes for a domain are hosted. 
• mail flows from sender into the (IMAP) boxes hosted by the 3rd party provider.
• MS O356 Server pulls email from there.

That's a pretty sorry excuse for a decent concept.

It adds enormous complexity, you still have to pay for the original box at the other provider and it deprives you of properly using the kind of deep integration between email and office/cloud features that MS offers and is so proud of.

For outgoing email, the MS Server allows you to send under your external mail adress. However, if I understood some somplaints correctly, since a while it does not any more allow you to send with a proper "From: abc@external domain.com", but only with a "sent on behalf of:".

What a strange idea.

Also obviously it is painful to have proper SPF and other mail-relevant DNS settings done because you do not know and MS doesn't publish what you would need to set (server addresses of where your outlook-box resides etc.)

What we want is to be able to send and receive (natively!!!) email in O365 email box. Because who on earth wants to communicate a new email address @outlook.com if he owns his personal domain?

For this function you need two things: 

• MS to display the required URLs of the Servers that receive email for the O365 mailboxes (which I as a client then would put as MX, SPF record etc.
• MS to configure this very server then as to accept incoming mail for the respective domain and put incoming mails into the respective mailboxes.

As this feature has already existed until late last year and as this is standard feature of Office 365 business/enterprise, is it hard to understand why it is not being done here. I strikes me as unbelievable that we even have to discuss this in the year 2018.

In uservoice this is the second-highest rated feature request for O365 for private use; and it seems to be the only one that people are so furious about that they actually are quitting their O365 contracts because of MS decision not to offer this. 

So sad.

There are no issues in adding whatever mail account to Office 365 Home, its all dependent on who hosts the domain & mail server

It appears that some posters are trying to add their domain/mail as an alias in an outlook.com mail account, which is where any problem would arise.

I aggree - it seems quite obvious to me that this decision derives from the fear of cannibalising the Business product.

To me this is quite a strange reason - looking at the problems that you would have trying to migrate from the "Office for private use world" to "business world".

But anyhow, it is as it is and it is a shame.