Hi @Ilman Hamzatov ,
Thank you for reaching out to Microsoft Q&A.
I understand that the IT department is advocating for the setup of three separate Azure tenants, and here are my thoughts on the proposed environments:
Yes, the public tenant does expose resources to the internet, which allows for user flexibility. However, you can enhance the security of a public tenant by configuring Conditional Access, Multi-Factor Authentication (MFA), and Private Endpoints.
While implementing policies at the subscription or management group level to isolate environments is a good approach, I suggest using only two tenants: a Test Tenant and a Production Tenant. This is because enabling certain policies might affect the entire Production environment, so having multiple tenants can provide a safer option.
Regarding costs and management, you could use a pay-as-you-go subscription model to avoid additional expenses. For licensing, the Test Tenant could take advantage of a 30-day free trial with a P2 license.
Lastly, the domain name itself does not pose any significant risk if proper precautions are in place. For instance, with a domain like companyname.onmicrosoft.com, users must pass an access token to access resources. Access tokens are security tokens designed for authorization, allowing authenticated users to access specific resources.
For additional information regarding access token: Access tokens in the Microsoft identity platform - Microsoft identity platform | Microsoft Learn
Hope this helps. Do let us know if you any further queries.
If this answers your query, do click **Accept Answer**
and **Yes**
for was this answer helpful. And, if you have any further query do let us know.
Regards,
Goutam Pratti