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.
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.
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.
MLoncarMicrosoft
StephenFeltmate do you know if this is possible to make without using credit card, but having azure consumption going to corporate enterprise enrollment?
MLoncar |
Yes, you can configure and run a sandbox test environment:
More on that here: https://learn.microsoft.com/en-us/microsoft-365/enterprise/modern-desktop-deployment-and-management-lab?view=o365-worldwide
Here is the direct link : https://www.microsoft.com/en-us/evalcenter/download-lab-kit
Dont forget the download the guides too (ZIp download for lab env and guides on the page I linked above)
Enjoy!
- Thanks a lot for sharing your experience. It look to be good way to proceed and it is really close to ideas that I have in mind.
We already have a AD test domain, so we just need to add an AAD test tenant and an AD Connect to sync all testing stuffs! 🙂
