Visual studio: MSDN offer-Rebuilding Demo/test environments

thtgrldiana 21 Reputation points

I am trying to figure out the proper order of operations for rebuilding my test environment after locking myself out of my DC. Additionally my demo tenant will expire in 30 days and I'll need to "transfer" my Global admin user (associated with my custom domain) to my new demo tenant.

  • Original build
  • test environment built with Azure-Base lab configurations
  • used Demo tenant (M365 xxxx-xxxx) from CDX added custom domain
  • Joined to Demo tenant M365 E5 with AD Connect (PTA)
  • Tear down
  • shut down and deleted all VMs in Azure Base Lab
  • removed all users from Azure Directory (Except the cloud created user/global admin)
  • User were removed via the MSOL PS command
  • Used the MSOL command to stop AD Sync
  • Permanently deleted (on-prem users from the deleted users in AAD)

Rebuilt my Azure on-prem environment using Base line configurations:
get an error that my original AD Sync is still associated with the original environment.

Question: without breaking my VSTN environment how would I transition from one demo tenant to a new one using the same Azure Lab, on-prem users, and custom domain

Question: My VSTN (MSDN) account is tied to my Global Admin user (ficticious name); I want to change this to actually be ME and with my personal email account: Is this a transfer? or I would like to make ME at a minimum a owner/co owner of the account and a billing administrator. Is this possible?

Question: Is there documentation consolidate to help me repeatedly build and tear down demo environments?

I feel like the information is out there, but finding it in a logical flow is not easy. My apologies for the wordiness: if Someone could assist with proper order of operations for teardown and share links in the remaining questions I would be ever so grateful!!!

Azure Active Directory
Azure Active Directory
An Azure enterprise identity service that provides single sign-on and multi-factor authentication.
14,849 questions
0 comments No comments
{count} votes

Accepted answer
  1. Dave Patrick 353.6K Reputation points MVP

    Adding an alternate account to your Visual Studio subscription allows you to access the subscription benefits, like Azure DevOps and Azure, with a different identity than that which the subscription is assigned to. In the past, this functionality was available only if your Visual Studio (VS) subscription was assigned to a Microsoft Account (MSA). We have extended this functionality for work or school accounts in Azure Active Directory (Azure AD).
    This doesn’t provide a copy of subscription to the other account; it only provides the ability to access the two benefits with the alternate account.
    For all subscriptions, you can add a “work or school account” so you can use that account with your benefits that require a login (VS IDE, Azure DevOps, and Azure).
    Adding an alternate ID is easy. Connect to, click on “Add alternate account”, enter the email address and click “Add”. For more information on using alternate identities, check out our Alternate identities article.

    --please don't forget to Accept as answer if the reply is helpful--

    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

    0 comments No comments

0 additional answers

Sort by: Most helpful