Forum Discussion
IP Public for VM in Azure Stack HCI
my organization recently setup azure stack HCI in our datacenter. I have created virtual machine in my azure stack HCI cluster. I want the VM could be accessed using RDP or it could be accessed from internet. How to assign IP Public to VM that already created in Azure Stack HCI environment ?. in my azure stack, i dont have virtual switch that contain IP Public Pool. do i need to created virtual switch containing IP Public Pool for my azure stack HCI ?
- If these are VMs on a physical HCI cluster, the requirements to access the VM are pretty much the same as any other Hyper-V VM. The VMs must be connected to an external virtual switch on the host and be assigned an IP address on a subnet/VLAN that is routable. These can be statically or DHCP assigned. If the VMs are domain-joined, then the 'Domain' firewall profile would likely be active so these rules are usually sufficient to allow access. If not, the firewall rules may need to be adjusted to allow the specific traffic you need. If you are attempting to access RDP or shares, you would need to ensure you have the appropriate permissions to do so.
If these VMs are in a nested virtualization environment, then besides the standard requirements above, you may also need to enable MAC address spoofing on each of the virtual NICs for communication to work to the nested VMs.
If these VMs are in Azure, then you would additionally need to be sure you have connectivity to the Azure VNET itself. This could be either via ExpressRoute or a VPN if you are trying to simply access the VM from an on-prem resource.
- If these are VMs on a physical HCI cluster, the requirements to access the VM are pretty much the same as any other Hyper-V VM. The VMs must be connected to an external virtual switch on the host and be assigned an IP address on a subnet/VLAN that is routable. These can be statically or DHCP assigned. If the VMs are domain-joined, then the 'Domain' firewall profile would likely be active so these rules are usually sufficient to allow access. If not, the firewall rules may need to be adjusted to allow the specific traffic you need. If you are attempting to access RDP or shares, you would need to ensure you have the appropriate permissions to do so.
If these VMs are in a nested virtualization environment, then besides the standard requirements above, you may also need to enable MAC address spoofing on each of the virtual NICs for communication to work to the nested VMs.
If these VMs are in Azure, then you would additionally need to be sure you have connectivity to the Azure VNET itself. This could be either via ExpressRoute or a VPN if you are trying to simply access the VM from an on-prem resource.- thank you Mr. Arya for your helpfull answer.
Dear Rendy,
Welcome to HYBR!
You can connect the created virtual machines in your Azure Stack HCI clusters without assigning public IP for the VM through Hybr®.
We have a remote access server that enables you to connect to Azure Stack HCI VMs without assigning a public IP to the VMs.
Access your Azure Stack HCI VMs via browser using console connect or connect using the private IP address of the VM through HYBR: https://www.cloudassert.com/Blogs/access-your-vms-via-browser-using-console-connect-in-hybr-276589
Enable multi-tenancy and self-service provisioning experience in Azure Stack HCI with consumption-based metering and billing solutions for your customers by leveraging Hybr. Read more: https://www.cloudassert.com/Solutions/Azure-Stack-HCIAn overview of Azure Stack HCI for your reference:
Azure Stack HCI solution overview - Azure Stack HCI | Microsoft Learn
