Yes, https://my.example.com is an example of a vanity URL. Vanity URLs are customized, branded URLs designed to be easily recognizable, memorable, and aligned with a company's branding. In this case, the subdomain my and the domain example.com create a branded, user-friendly URL. Vanity URLs are often used for simplifying access to services like IdentityNow and for improving user experience.
Key Reference from SailPoint Documentation:
* Vanity URL Usage in IdentityNow: SailPoint allows customers to configure vanity URLs to provide a more personalized and branded login experience for their users.

No, when deploying the Virtual Appliance (VA) in Azure, the IdentityNow engineer does not necessarily need to use the Azure CLI to deploy the VA image. While using the Azure CLI is one option, SailPoint provides multiple ways to deploy the VA in Azure, including using the Azure portal or ARM (Azure Resource Manager) templates. The process does not mandate using the CLI specifically.
Key Reference from SailPoint Documentation:
* Azure VA Deployment Methods: SailPoint supports multiple methods for deploying the VA in Azure, including through the Azure portal or ARM templates, without requiring the CLI.

The default non-production tenant does not have the same full performance scalability as a production tenant.
Non-production environments are typically configured with reduced resources since they are intended for testing, development, or demonstration rather than handling large-scale, live workloads.
Key Reference from SailPoint Documentation:
* Performance Differences Between Tenants: SailPoint non-production tenants are generally scaled down compared to production environments to reflect their testing and demonstration purposes, not for high-performance or large-scale operations.

The virtual appliance (VA) private key is not stored in both the IdentityNow tenant and the VA. The VA private key, which is critical for secure communications, is stored only on the Virtual Appliance (VA) itself.
It is used to authenticate and encrypt communications between the VA and the IdentityNow tenant. Storing such sensitive information in the IdentityNow tenant would violate best practices for key management and security.
Instead, the IdentityNow tenant only holds the public key or a reference to the key to facilitate secure exchanges with the VA. The private key remains secured locally within the VA, protecting it from potential security vulnerabilities associated with external storage.
References:
* SailPoint IdentityNow Virtual Appliance Architecture Guide.
* SailPoint IdentityNow Security and Encryption Documentation.

SailPoint IdentityNow API documentation is indeed located at https://docs.sailpoint.com. This official documentation site contains all the information developers need to interact with IdentityNow through APIs. It includes guidelines on how to authenticate, make requests, and use the API endpoints to automate and integrate with other systems.
Key Reference from SailPoint Documentation:
* SailPoint API Documentation: The site docs.sailpoint.com hosts the official API documentation for SailPoint IdentityNow, covering all aspects of using IdentityNow's APIs.