Forum Discussion
Solved
Azure AD test tenant
Hello Community, I'm stating this discussion because I likely wanted your input regarding the best way to build a test tenant in Azure. We have a Prod tenant and for some feature testing or some wi...
- What I did is set up a parallel AD domain using our as-built documentation and then registered a new domain name used exclusively for this project. Then I created an Azure tenant with a pay-as-you-go subscription linked to a credit card. Then I used Azure AD Connect to connect the test domain with the test tenant. The AD DS domain is on a completely separate VLAN and the test tenant is completely separate from our production tenant.
What this does is keep the production environment completely separate from the test environment. I can try new things on the test domain and have a pretty good idea about how it's going to affect the production environment. The best part about this is that I can experiment with new services to deeply understand them before presenting them as potential projects. The idea is to be very thorough and build a deep understanding of a service before anyone else in the company (or our team) puts time into it.
This is everytime s big discussion😉
From my perspective a test tenant is needed, when you will evaluate services at Azure AD level.
It make sense to create a isolate AD domain in the same way like the production system and also use a domain name and use the same account sync solution.
When you start with a separate test tenant, please be aware of the additional management overhead and handle it like the same way as the prod system.
Define the scope and the goal for the rest tenant and who is responsible for it.
For testing Azure services they running inside subscriptions it can be a better way to use different subscriptions and group this with management groups and associate Azure policies.
From my perspective a test tenant is needed, when you will evaluate services at Azure AD level.
It make sense to create a isolate AD domain in the same way like the production system and also use a domain name and use the same account sync solution.
When you start with a separate test tenant, please be aware of the additional management overhead and handle it like the same way as the prod system.
Define the scope and the goal for the rest tenant and who is responsible for it.
For testing Azure services they running inside subscriptions it can be a better way to use different subscriptions and group this with management groups and associate Azure policies.
