Azure AD App Registration: When setting up an application registration in Azure AD, specific permissions are required to delegate access.
User Access Administrator Role: This role has the necessary permissions to manage user access to Azure resources, including delegating permissions for app registrations.
Comparison of Roles:
Azure Reader Role: Grants read-only access, insufficient for managing app registrations.
Azure Contributor Role: Allows creation and management of resources but does not include permissions to manage access.
Azure Custom Role: While it can be defined to meet specific needs, the User Access Administrator role is predefined to handle access delegation.
Conclusion: The Azure User Access Administrator role is required to delegate minimum permissions for Azure AD App registration.
Reference:
Azure Role-Based Access Control Documentation
Azure AD App Registration Guide

* NC2 Cluster Node Limit: NC2 on Azure has specific limitations regarding the maximum number of nodes supported in a single cluster.
* Maximum Nodes: According to the current NC2 on Azure guidelines, a single cluster can support up to
18 nodes.
* Workload Support: This limitation ensures optimal performance and management of resources within the Azure environment.
* Comparison of Options:
* 14 nodes: Less than the maximum supported.
* 24 nodes and 28 nodes: Exceed the maximum supported, potentially leading to performance and management issues.
* Conclusion: For supporting new workloads, the maximum number of nodes in an NC2 on Azure environment is 18.
References:
* Nutanix Clusters on Azure Technical Specifications
* Azure Virtual Machine Scale Sets Documentation

* Local Key Manager (LKM):The native local key manager in Nutanix requires a minimum number of nodes to function correctly and provide key management services.
* Minimum Node Requirement for LKM:To support the Nutanix native LKM, at least three nodes are needed. This configuration ensures that the key management service can achieve the necessary quorum and redundancy for secure operations.
References:
* Nutanix Data Encryption Documentation
* Nutanix Cluster Configuration 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.
References:
* Nutanix Networking Configuration Guide
* Azure IP Address Management Documentation

* Cloud Hardware Support: For issues related to cloud hardware, such as EC2 instances or VPC configurations, the responsible entity is typically the public cloud vendor.
* Nutanix Responsibility: Nutanix manages the software layer and integration aspects of the NC2 service, but the underlying hardware support is managed by the cloud provider (e.g., AWS, Azure).
* Support Process:
* Public Cloud Vendor: Contact the public cloud vendor for issues directly related to the hardware, as they own and manage the physical infrastructure.
* Nutanix: For software and configuration issues specific to the NC2 service, contact Nutanix support.
* Conclusion: For cloud hardware-related support, the appropriate contact is the public cloud vendor.
References:
* Nutanix Support Guide
* Azure Support Documentation