![]() Organisations having standalone O365 tenants don’t use (they could if they wanted to), in fact, they don’t need it. ![]() The purpose of this domain is to facilitate email migrations / co-existence scenarios. Microsoft manages DNS records for this domain and we cannot control that. This domain is fully functional and we can send/receive emails through this domain to/from the internet. Well, when we register an O365 tenant, by default it creates one default domain as ". The question becomes a priority question for companies having a hybrid setup with MX pointing to on-premise custom domains and emails to IDS directly hit to O365 bypassing the on-premise gateway and thus causing a compliance issue. I have clients asking if how we can stop email delivery on (O365 / Exchange online) email addresses since we don’t have any control on this email domain along with DNS entries.
0 Comments
Leave a Reply. |