* SMTP Server Configuration:To send alert emails from Prism Central, it is essential to configure an SMTP server in the Prism Central settings. This server handles the email sending process, ensuring that alerts generated by Prism Central are properly delivered to the specified email addresses.
* Email Notification Setup:The SMTP server settings include the server address, port, and authentication details. Once these settings are correctly configured, Prism Central can use the SMTP server to send out alert emails reliably.
References:
* Nutanix Prism Central Administration Guide
* SMTP Configuration for Email Alerts in Prism Central

NAT Gateways: Necessary for providing outbound internet access to resources in the private subnet. It ensures that the virtual network can communicate with external services securely.
Delegated Subnets: Required for deploying specific Azure services within the virtual network, allowing controlled access and management of the resources within these subnets.
Flow Gateway Subnets: These subnets are used for managing traffic flow within the network, ensuring efficient routing and connectivity between different parts of the NC2 infrastructure.
VNet Peers: Establish connections between different virtual networks within Azure, enabling seamless communication and resource sharing across various parts of the NC2 deployment.
Reference:
Azure Virtual Network Documentation
Nutanix NC2 Networking Setup Guide

Floating IP Address Limitation: The cluster already has 25 floating IP addresses in use by other VMs. If the administrator cannot assign a floating IP address to the new VM, it is because the pool of available floating IPs is exhausted.
Requesting Additional Floating IPs: To resolve this issue, the administrator needs to request additional floating IP addresses to be allocated to the NAT subnet. This will ensure that there are enough IP addresses available for all VMs requiring inbound connectivity.
Reference:
Nutanix Networking Configuration Guide
Azure IP Address Management Documentation

Outbound Rule Necessity: For successful cluster deployment, certain outbound connections must be allowed to ensure proper download and configuration of resources.
Critical Destination: "Https://downloads.cloud.nutanix.com/*" is a critical endpoint from which the Nutanix software and updates are downloaded during the cluster deployment process.
Functionality: Ensuring an outbound rule for this destination allows the deployment to fetch necessary files and updates, enabling smooth cluster setup and operation.
Other Destinations:
Https://portal.nutanix.com/: Used for accessing the Nutanix portal, not directly related to deployment downloads.
Https://support.nutanix.com/: Used for support-related tasks, not for deployment-specific downloads.
https://nutanix.dev/: Related to development and API documentation, not necessary for initial deployment.
Conclusion: Outbound connectivity to "Https://downloads.cloud.nutanix.com/*" is essential for downloading deployment resources.
Reference:
Nutanix NC2 on Azure Network Configuration Guide
Azure Network Security Documentation

Azure Monitor Overview: Azure Monitor is a comprehensive monitoring service that collects, analyzes, and acts on telemetry data from Azure resources.
Key Metrics Monitoring: Azure Monitor enables the monitoring of various Azure services such as virtual networks, virtual machines, and bare metal hosts, providing insights and visibility into their performance and health.
Comparison of Services:
Resource Manager: Manages Azure resources but does not provide detailed monitoring capabilities.
Azure Service Health: Provides personalized alerts and guidance when Azure service issues affect you but is not a comprehensive monitoring solution.
Azure Network Watcher: Focuses on network performance monitoring and diagnostics but does not cover all resource types.
Conclusion: Azure Monitor is the most suitable service for monitoring key metrics across a wide range of Azure services.
Reference:
Azure Monitor Documentation
Nutanix NC2 on Azure Monitoring Guide