Deploy builds using Game Manager

This article lists the general steps to deploy/create builds for VMs using Game Manager.

If this is your first time deploying a build, we recommend deploying a build using the Windows Runner C# sample or Wrapper sample. Both will come with all the assets you need to actually deploy servers.


In order to use and view the PlayFab Multiplayer Servers, you need to enable the feature from Game Manager. For instructions, see Enable the PlayFab Server feature.

For details about the values you can use for each parameter, see Build definition.

Steps to deploy through Game Manager

  1. Sign in to Game Manager

  2. Go to My Studios and Titles page and select your game title to display the dashboard

  3. Go to Multiplayer > Servers page, select New Build at the top right to create a new build

  4. Starting with the Build details, use a descriptive string as the Build Name

  5. Select a server with limited-free usage, such as Dasv4 during development. To learn more about pricing, see Billing for PlayFab Multiplayer Servers

  6. Set a value you want for Servers per machine

    Image below shows values used in the info section. Build details including, Build name, Virtual machine selection of Dasv4, and 2 servers per machine

  7. Next we have the server details portion where you'll need to select an OS type either Windows or Linux. Then you'll select your server type, either process or container based on the OS you choose.


For Linux platform, you need to create your own container image. For more instructions, see Create and deploy Linux container images. If you've already uploaded a container image, it will appear in the Image dropdown. To use it, select the image.

Once you've selected your OS type, you can then choose the server type. Based on the OS/Server type you'll have the following features you can enable.

  • Virtual Machine Metrics Preview: By enabling the metrics it allows you to see system level metrics such as CPU, memory, network, etc. To learn more, read our VM performance metrics (preview) article
  • Windows Core Preview: Allows you to test the newest versions of Windows operating system on test builds to see how your game will run with the newer operation system. To learn more, read OS patch level updates for Windows
  • Automatic Crash Dump Collection: Allows you to enable automatic crash dump collection on your Windows Container server types. You can choose between doing a full, mini, or custom dump. To learn more, read Enabling automatic collection of crash dumps

Server details for Process mode

Image below shows values used in the OS section when you select Windows as the platform but use Process based server type. There's also the option of using Linux process based servers as well. Server details with Windows Process selected as OS and server type

Server details for Container mode

Image below shows values used in the OS section when you select Linux as the platform but use Container based server type. There's also the option of using Windows container based servers as well. Server details with Linux Container selected as OS and server type

Assets for builds

  1. Under Assets, select Upload. Navigate to folder with the compiled PlayFab Multiplayer Server Build and then select the .zip package to upload.

Assets for Windows servers

  • For Windows platform, you must upload a PlayFab Game Server Build as an asset. To learn how to create a PlayFab Game Server Build, see Author a game server build. Upload assets to modify and customize the Windows container image. Mount path for the assets in windows servers should be rooted in C drive.

Assets for Windows container servers

Assets for windows servers will need to be in the C drive otherwise the API may return an error. The mount path is only necessary for containers.


Do not provide a mount path for process based servers.

Assets for Linux servers

  • For Linux platform, uploading an asset is optional as the Game Server can be included as part of the container image. But you must still have a Game Server, make sure the mount path is valid within the container you're uploading.

If you're uploading assets:

  • Set C:\Assets or select a different path as the mount path
  • Set C:\Assets\YourGameServerBuild.exe as the Start Command

Asset section for new build on MPS along with start command.

Network settings

  1. For network, set the port number, name, and protocol.

Setting port for container server types

If you're using a container server type, you should specify the port number.

For example, in Game Manager for a container server type, you could specify:

  • Port name: "gameServerPort"
  • Port number: 7777
  • Protocol: UDP

Network settings in Game Manager for container server type

Then in your code you would do something like the following

int port = 7777; // since you already know the port
GameServer gs = new GameServer(port);


In container mode, each game server runs on its own network namespace. This is the reason why every game server can listen to the same port. The container port is dynamically mapped to a unique port on the virtual machine. However, on process mode, all game servers run on the same network namespace. Having all game servers listen to the same port would create conflicts, so this is why you'll need to get the ServerListeningPort from the GSDK.

Setting port for process server types

For process server type, you should use the GSDK to retrieve your port number. Don't include a port number as part of the build definition.

Network settings in Game Manager for process server type

Then in your code you would do something like:

var gsc = GameServerSDK.GetConnectionInfo();

var gp = gsc.Where(x=>x.Name=="gameServerPort").Single();

GameServer gs = new GameServerPort(gp.ServerListeningPort);

To view the full sample code, go to GameServerConnectionInfo.cs in GSDK/CSharp/GSDK_CSharp_Standard The above code sample that gets the port from the GSDK would work in container mode as well.

Start command

Start command for container based servers

Your start command should be the absolute path (including the mount path) to your game executable that should include any required arguments. For example, your start command could look like C:\Assets\wrapper.exe -g C:\Assets\fakegame.exe arg1 arg2. Adding in the "C:\Assets" portion to your absolute path for your start command is only required if it's a Windows container based server. This is because that's the directory where your game asset would be extracted from.

Start command for windows process based servers

Your start command is the relative path within the uploaded asset. If the executable is directly within the asset folder, then you can just use <yourGameServerBuild.exe>. If it is within another folder (for example GameDirectory), then the start command would be gameDirectory/YourGameServerBuild.exe.

  1. Under Regions, select the region you want to deploy the servers. Then specify the number of standby and maximum servers.
  2. Select Save to start the deployment process. You'll be taken to the build home page. The build will display the Deploying status as show in the image below.

In a couple minutes, your build should be in the Deployed state. This means that servers are deployed and can be allocated. For more information on allocating game servers, you can check here whereas you can use the MpsAllocatorSample to experiment with server allocation.

Configure region information

After deploying builds, you can still modify the following parameters.

  • Regions
  • Standby servers
  • Maximum servers

To configure regional settings:

  • Go to the Servers > Builds page
  • Select the build you want to modify
  • On the Regions tab, go to the Servers by region section
  • Add/remove region and modify the server numbers

Deployed builds in Game Manager


During development, shut off any unused or unhealthy regions to avoid VM core hour usage. Core hour usage begins during VM startup and continues until the VM is shut off. VMs in a region will not automatically be shut off unless the region's target standby servers reach 0, or a region is deleted.

Shutting down VMs

There are three ways to shut down VMs

  1. Set a region's target standby to 0, this will shut down VMs for this region only.
  2. Delete a specific region from a build.
  3. Delete the whole build, this will shut down VMs across all regions for this build.

See also