...

To add an additional network interface to an instance or to remove an interface from your instance perform the steps described below.

 The Please note: The steps below only provide a basic overview. The exact tasks required will vary depending on your network design. Please refer to the Azure documentation for details.

...

It is possible to add additional NICs to the Charon host system in the cloud. Additional NICs can be used to connect the instance to additional subnets. And an additional NIC can also be used to provide an emulated SPARC system running in the emulator with a dedicated network interface. This section shows the basic steps to add a NIC to an existing Azure cloud instance.

Please note: The VM must be stopped before the new interface can be attached to the system. The VM also must be stopped before detaching an interface.

...

Step 2: Click on Attach network interface at the top. This will either let you choose an existing interface or offer the option to create a new one as shown in the sample below:

...

Step 3: Click on Create network interface to open the interface creation screen.

...

Step 4: Attach the selected or newly created interface to your cloud VM.

Make Please note: make sure to stop the instance before attaching the interface.

On the Networking screen, you should now see the new interface (if required, open the subsection of the screen by clicking on
Attach network interface). Click on OK to add the NIC to your VM. The image below shows an example:

...

Adding a Public IP address to the Second NIC

Please note: If this NIC is used as a dedicated NIC for a Solaris guest system, it is not recommended to expose the Solaris guest to the Internet by adding a public IP to the dedicated NIC. It is highly recommended to use a secure, encrypted VPN connection for any external traffic of the the guest system. The user is responsible for making sure that any external connection complies with the relevant rules and policies of the environment.

...

Add the necessary data, in particular the following:

• Name
• Dynamic (changes every time the instance is restarted) or Static (persistent)
• Resource group (same as your interface)
• Location

...

Then click on Save to save the changes.

Do Please note: do not forget to add an appropriate Network Security Group to protect the interface.

Address Assignment Information

...

• x.x.x.0: network address
  
• x.x.x.1: default gateway
  
• x.x.x.2, x.x.x.3: DNS services
  
• x.x.x.255: broadcast address
  

Please note:

• The automatically configured default router of a subnet does not respond to a ping command.

...

• The traceroute command does not work.

...

• Multicast, broadcast, and GRE are not supported.

Public IP addresses:
By default, public IP addresses are dynamic and the address associated to them may change when the VM is stopped or deleted. To ensure that the VM always uses the same public IP address, create a static public IP address. One public IP address can be assigned to an instance at instance creation. Additional public IP addresses can be created using by creating a new resource
(Home > Create a Resource > search for Public IP address and select resource > Create) and assigning the resource to an instance interface.