Assigning Public IP to your virtual machine

Manage public IP in User-Portal

Users can manage public IP addresses for virtual machines (VMs) in their workspace after Research Support enables this feature for the workspace. This guide explains how to request access, assign a public IP to a VM, and remove it when it is no longer needed.

Introduction

Public IP management allows workspace Accountable and or Privileged members to add or remove a static public IP address for their VM(s). Before this is possible, the feature must be enabled for the workspace by Research Support after a request has been submitted via ticket.

Note: Linux VMs do not support public IP assignment in myDRE. This functionality applies to Windows VMs only.

By default myDRE workspace VMs have private IP. Only Windows VMs can have public IP assigned to them, for this, please submit a request at your local Research Support.

Before you begin

Submit a ticket to request public IP management for your workspace at your local myDRE Research Support.
After evaluation by our local Research Support, the permission to modify public IP can be enabled for your workspace.

Once public IP management is enabled, the option to add or remove a public IP becomes available on the VM card in your workspace.

Assign a public IP

Note that this action can be performed only by workspace Accountable and/or Privileged member after Research support has enabled it for your workspace.

Log in to your workspace.
Locate the VM for which you want to assign a public IP.
On the VM card, click +PublicIP.
Once a warning pop-up, confirm the action by typing assign.

After confirmation, the public IP is assigned to the selected VM.

Remove a public IP

Log in to your workspace.
Locate the VM from which you want to remove the public IP.
On the VM card, click the Public IP trash can icon.
Confirm the action by typing remove.

After confirmation, the public IP is removed from the selected VM.

Important information

Adding a public IP to a VM creates additional costs.
Only request a public IP if your use case requires direct external access.
Please consult your local Research Support regarding the necessity of having a public IP assigned to your VM.
Adding a public IP can increase exposure and may introduce security risks, especially since your VM uses a static public IP. The actual impact depends on how the workspace is configured and how it is exposed to the internet

For example, a public IP may be required for specific use cases such as direct RDP access from a local client or when using IP allowlisting with external services. However, these scenarios are increasingly uncommon.

Many organisations block direct RDP access, and alternatives such as Azure Bastion can be used instead without requiring a public IP. Similarly, domain-based allowlisting can often be used instead of IP allowlisting.

Review all implications above carefully before assigning a public IP.
You can remove a public IP at any time when it is no longer needed.
Research Support can disable public IP management for the workspace from the Admin Portal at any time.
If public IP management is disabled, existing public IPs are not automatically removed.

Enabling public IP management gives workspace members the ability to manage public IPs for their VM(s), but it does not automatically assign a public IP. A public IP must still be added manually for each VM that requires one.