Choose your operating system:
Windows
macOS
Linux
This tutorial provides a step-by-step guide to setting up an Unreal Engine 4 virtual machine (VM) instance on Microsoft Azure using the Azure Marketplace.
Prerequisites
Azure Account and Subscription
You need an Azure account and at least one subscription for which you have the proper permissions to create resources. For information on creating a new subscription, refer to this guide. Subscriptions also require that you have a billing account set up.
While Unreal Engine is available at no cost, Azure resources do have an associated cost. If your account is linked to your employer or another party, check that they are prepared to accept responsibility for the costs involved before setting up your deployment instance. For a more accurate estimate of your cost, review the pricing information on the Virtual Machine Pricing page, filter by desired region, and search for "NCas_T4_v3" to see the "pay as you go" pricing.
Remote Access
Accessing your Azure instance where Unreal Engine is deployed requires a remote access application. We will be using Windows Remote Desktop Connection (Windows RDP), which already comes installed on most editions of Windows 10.
Using the Azure Portal and the Azure Marketplace
The Unreal Engine VM offer is hosted on the Azure Marketplace. Navigate to the offer page here.
Sign in to the Azure Marketplace using the button at the top right. Use the same account you use for all other Azure services.
Click Get It Now below the Unreal Engine icon.
A dialog will pop up asking you to choose your software plan, select Unreal Engine 4, confirm your information, and add this app to your account. Fill it out and click Continue.
The Azure Portal will open up to the Unreal Engine product in your account. From here, choose Unreal Engine 4 under the Plan dropdown and then click Create to begin setting up the virtual machine.
Configuring the Virtual Machine
First, select a Subscription where your virtual machine will reside. You must select an existing subscription for which you have the permissions to create resources.
Select a Resource Group for the virtual machine. Resource groups are used to organize resources and can be re-used for other VMs. If you do not already have a resource group, click Create new. Give it a valid name and click OK.
Provide a valid name for the virtual machine itself.
Select a region to deploy this VM in. You should select a region that is as close as possible to you to minimize latency when using the VM. It must be a region that supports the NV12s_v3 VM size, and you will receive an error if it does not. Different regions may change the price estimation shown in Size below.
Leave the Image as "Unreal Engine", click See All Sizes, and select the Size "NCas_T4_v3". You may encounter a warning saying "Family vCPUs are insufficient to deploy these sizes". Click Request quota.
A blade appears with the options for increasing your quota. The NCas_T4_v3 needs 4 vCPUs per VM instance, so that is the minimum amount needed for this tutorial.
Click Save and Continue.
After a few minutes, you should receive confirmation of your new quota. If it is unsuccessful, you may need to select a different region or create a support ticket.
Under Administrator account, create your own Username and Password for this virtual machine, and make sure to remember these for later. You cannot access the machine without these credentials.
This VM comes with a 250 GB SSD by default. If you want to add an extra storage disk, you can configure settings with Next : Disks. Otherwise, select Review + create. If your organization has Software Assurance for Windows Server licenses, you can select this option before creating.
The next page is the confirmation for the VM you're about to create. If it looks good, click Create.
A new page appears, showing the progress of the deployment. It may take a few minutes until you receive a notification that the deployment is complete. Click Refresh to confirm, then click Go to resource.
Connecting to the Instance
You should now be on the Overview page of the VM resource, where you can see or configure all the technical settings of the instance. Now you have everything you need to start a remote desktop session into this workstation and start using it.
Launch the Windows RDP client on your PC. Copy the Public IP address from the instance overview into the Computer field in the login window, then click Connect.
Under More choices, select Use a different account. Enter the username and password that you defined earlier. You can optionally select Remember me then click OK.
You will get a warning about the certificate of the VM. Select Don't ask me again for connections to this computer, then click Yes.
Launch Unreal Engine
After a few moments, you may see a Windows boot screen at first, and then the Unreal Engine EULA shows. Select the relevant option and click Verify EULA. You only need to do this on the very first connection to the instance.
Next, you are presented with the Epic Games log-in menu. Log in with your Epic Games account.
Once you log in, you will see a desktop with Unreal Engine and the Epic Games Launcher already present. You can run Unreal Engine directly from the shortcut or run the Epic Games Launcher to login again and access content as you normally would.
Upon logging into the Launcher for the first time you may be presented with a prompt to update the launcher and a prompt to associate project files with the engine.
Cost Optimization
Due to the ongoing hourly cost of using an Azure VM, we recommend stopping your instance when you're not using it.
Stopping Your VM
From the VM overview page, click the Stop button at the top. This is similar to shutting down your home or work computer. All running applications quit, but whatever data was stored on persistent storage is preserved. Once the instance is stopped you are no longer charged any hourly fees for its use, although you are charged a small amount to store the data on its hard drive.
Restarting Your Stopped VM
From the VM overview page, click the Start button to turn a stopped instance back on. After a short time, the VM will be available to connect over RDP again, and any persistent storage volumes will be restored.
Deleting Your VM
If you are done using the VM indefinitely and want to clean up your resources, click Delete at the top of the overview page. You are then prompted to confirm the deletion and you can also select the associate storage and networking resources to delete along with it. Once all these resources are deleted, you are no longer charged for them. This action cannot be undone.
You can also delete the entire Resource Group where all your created resources are stored.
In your Azure portal, navigate to your Subscription, and then select Resource groups from the blade on the left.
Select the relevant resource group from the available list.
From the resource group overview page, you can click Delete resource group at the top, or select and then Delete individual resources. You need to confirm your deletion.
This resource group page is also where you can access and manage these resources in the future.