I have set up our corporate AD to sync with our Azure AD and have a question for the community or WAAD team about subdomains and best practise.

On WAAD I have verified our corporate.net domain, but our on-premises AD is at the domain hq.corporate.net.

From my CTO I am told that this is normal to create sub AD domains within a corporation. This means that when the users is synced they just get username@<waad-name>.onmicrosoft.com as their email/username in WAAD.

I solved that by verifying hq.corporate.net also to WAAD and all users was updated such they now can log on with username@hq.corporate.net on applications with WAAD.

Is this the intended way to go about this? My first impression would be that I would like all our employees to be able to log on with username@corporate.net and not have to include that ADs "branch" prefix/subdomain.

What options do I have to make this happen? If not, is the best practise to tell our mail server that username@hq.corporate.net should give the mail to username@corporate.net instead? The reason why username@hq.corporate.net is not that great is that users have to remember the hq. prefix and also it's the email passed to applications as the identity when they sign on, where their real email is actually username@corporate.net.