Create new users on development machines


Dynamics 365 for Finance and Operations is now being licensed as Dynamics 365 Finance and Dynamics 365 Supply Chain Management. For more information about these licensing changes, see Dynamics 365 Licensing Update.

This article explains how to enable another user account as a developer on a development VM.


This topic only applies to downloaded local virtual machines (VMs) or VMs that are hosted in a customer’s subscription. You can't create new users on Microsoft-managed developer and build machines where developers have no administrator acces to the VM (Platform update 12 or newer).

When an environment is first deployed, only one user account is enabled as a developer on the virtual machine (VM). This user is preconfigured by Microsoft Dynamics Lifecycle Services (LCS) or is the local administrator account on downloaded virtual hard disks (VHDs). However, you can enable a new user account to develop on the VM. Even after you enable a new account, only one developer can develop at a time on the same VM/application.


To enable a new user account to develop on the VM, the user account must be an administrator on the VM. Additionally, you must log on to the VM by using the credentials of the default developer account. If the VM is a Microsoft Azure VM, the account information is available on the environment page in LCS. If the VM is a local VM that runs on the downloaded VHD, use the local administrator account. For more information, see Deploy and access development environments.


  1. Download the following script: ProvisionAxDeveloper.ps1, the script is available at

  2. Open a Microsoft Windows PowerShell Command Prompt window as an administrator.

  3. Run the ProvisionAxDeveloper.ps1 script. Specify the following parameters:

    • DatabaseServerName – Typically, this is the machine name.
    • Users – Use the following format: <domain or machine name>\user1, … <domain or machine name>\user n


    > ProvisionAxDeveloper.ps1 RDXP00DB20RAINM RDXP00DB20RAINM\username1
    > ProvisionAxDeveloper.ps1 -databaseservername RDXP00DB20RAINM -users RDXP00DB20RAINM\username1,RDXP00DB20RAINM\username2
  4. If more than one user account will be developing on the same version control workspace, you need to make the workspace public.

    1. In Visual Studio, open Source Control Explorer, select the workspace drop-down and select Manage workspaces.
    2. Select the application workspace, click Edit, then click Advanced and set the workspace to Public workspace.