Hello @Myo Min Hein (Ray)
Thank you for sharing this detail and I apologize for the misunderstanding.
For this case scenario, I would like to recap the following relevant details to proceed further. Let me mention them below:
The forest in Azure contains a domain that does not exist on-premises. Because of the trust relationship, logons made against on-premises domains can be trusted for access to resources in the separate Azure domain.
Typical uses for this architecture include maintaining security separation for objects and identities held in the cloud and migrating individual domains from on-premises to the cloud.
Furthermore, the topologies considerations or design are the ones down below:
- -Single forest, single Azure AD directory
- -Multiple forests, single Azure AD directory
- -Multiple forests, separate topologies
- -Staging server
- -Multiple Azure AD directories
Forest level trusts are transitive. If you establish a forest level trust between an on-premises forest and a forest in the cloud, this trust is extended to other new domains created in either forest. If you use domains to provide separation for security purposes, consider creating trusts at the domain level only. Domain level trusts are non-transitive.
https://learn.microsoft.com/en-us/azure/architecture/reference-architectures/identity/adds-forest
I hope this time I was getting to the right track in order to address your concern buddy.
Looking forward to your feedback,
Cheers,
Please "Accept the answer" if the information helped you. This will help us and others in the community as well.