Azure ExpressRoute with private peering establishes a dedicated, private connection from the on-premises infrastructure to Azure, bypassing the public internet. This provides the predictable low latency, consistent bandwidth, and higher reliability required for sensitive workloads like synchronous database replication, which a standard VPN over a shared internet link cannot guarantee.

For Xi Beam to execute actions like stopping VMs in Azure, it must first have the Azure cloud account (subscription) properly onboarded and scoped within the policy. Furthermore, the service principal used for Beam integration requires the appropriate Azure RBAC permissions (e.g., Virtual Machine Contributor) to perform management operations. An incorrect scope or insufficient permissions is a common cause for policies not executing.

The Foundation VM is a critical, temporary bootstrap component. It is deployed as a standard Azure VM and is responsible for discovering the provisioned bare metal instances, imaging them with the Nutanix AOS and AHV software, and forming the initial cluster. Once the cluster is established, the Foundation VM is typically decommissioned, and management is handled by the CVM on each node and Prism Central.

The statement is true. Nutanix Move is designed for workload portability across different infrastructures and hypervisors. It can migrate live VMs from an on-premises AHV source to a Nutanix cluster on Azure BareMetal (which runs AHV) with minimal downtime. The process handles the necessary conversions and transfers over the network connection (like ExpressRoute or VPN) between the sites.

Azure Network Watcher’s Connection Monitor can be set up to continuously test latency and connectivity between an Azure VM (the new environment) and an on-premises endpoint (like the old application server or a test IP). Prism Central’s Analysis tab can provide deep, historical performance metrics for the VMs and their virtual networks, allowing you to correlate application performance issues with network or host metrics within the Nutanix stack.

In a cloud model like Azure BareMetal for Nutanix, the cloud provider (Microsoft Azure) assumes responsibility for the physical security, power, cooling, and physical network infrastructure of the data center housing the bare metal instances. This is a fundamental aspect of the shared responsibility model. Nutanix AOS continues to manage storage redundancy, data resilience, hypervisor, and virtual networking as it does on-premises.

Prism Central’s alerting policies can be configured to send payloads via webhooks to external systems. An Azure Logic App is a serverless workflow tool that can easily receive this webhook, parse the JSON alert data, and use the built-in Azure DevOps connector to automatically create a new work item (bug, issue, etc.). This creates a seamless, automated integration without requiring constant polling.

In Azure, a floating IP like the CVIP cannot be assigned directly to a NIC outside of Azure’s control. The standard pattern is to create an Azure Internal Load Balancer (ILB) in the same VNet/subnet. The CVIP is configured as the ILB’s frontend private IP address. The individual IPs of the Nutanix nodes (specifically, their host VMs/CVMs) are placed in the ILB’s backend pool. AOS health probes determine the active node, and Azure ILB directs traffic to it.

For Calm to provision and manage resources (like VMs, networks, disks) directly in an Azure subscription, it requires an Azure Service Principal (an application identity) with appropriate RBAC permissions, such as Contributor role on the target subscription or resource group. These credentials are added as a ‘Cloud Account’ in Calm. This allows Calm’s blueprints to use Azure native APIs without needing all resources to be hosted on a Nutanix cluster.

Azure ExpressRoute with private peering establishes a dedicated, private connection from the on-premises infrastructure to Azure, bypassing the public internet. This provides the predictable low latency, consistent bandwidth, and higher reliability required for sensitive workloads like synchronous database replication, which a standard VPN over a shared internet link cannot guarantee.0