Set up your system in a way which will allow you to receive incoming emails.
Your users might be invited into a different Tenant to access resources. To accept these invitations - which will arrive in email form - you’ve to receive these invitation emails.
You might get into a situation where you want to purchase one or more HTTPS certificates to run your services with your own domain name and not just with the standard https://something.azurewebsites.net  URL.
As part of this process, the Certificate Authority will try to validate your ownership over your domain name and send you an email for confirmation. They will probably use one of these addresses:
Without MX records and a system receiving these email you’ll face some challenges.
When you’re using the standard issued login names like: email@example.com you will have to use Office 365 to receive emails because the MX records of something.onmicrosoft.com are pointing to Office 365 and you cannot change them.
Of course you can purchase the cheapest service to receive emails because you’ll only need Exchange Online licenses and nothing else.
When you’re using your own domain to logon into Azure, for example: firstname.lastname@example.org and you’ve the control over your MX records, you can use whatever system you’d like to use to receive those emails.
You can still use Office 365 but you can also use any other emails you’re currently using.
I have multiple subscriptions both for Azure and Office 365, I run production and developer subscriptions as well.
I use the sub-domains under my production domain to run non-production subscription so I can have the control over the email flow:
- kolislab.com for production
- dev.kolislab.com for development
- demo.kolislab.com for demo purposes