Azure Deployment
NCache Cloud is provisioned as an Azure Managed Application within your tenant subscription. This section covers the end-to-end lifecycle for deploying and operationalizing NCache Cloud on Microsoft Azure - from pre-provisioning network prerequisites to post-deployment verification and telemetry dashboards.
Deployment Lifecycle Overview
A standard deployment follows these core stages:
Prerequisites Verification: Prepare target resource groups, virtual networks, subnets, and licensing requirements (including Microsoft Entra ID P2 for Just-In-Time access).
Marketplace Provisioning: Launch the marketplace offer, select your licensing plan, configure node topology (Single-Region, Multi-Zone, or Multi-Region Geo-Replication), define maintenance windows, and configure technical support access.
Automated Infrastructure Orchestration: Azure deploys the Managed Resource Group (MRG), provisioning the VMSS cluster, load balancers, private endpoints, DNS zones, and runbooks.
Post-Deployment Access & Testing: Connect client applications via private endpoints, verify cluster health with the stress test tool, access the NCache Cloud Portal, and inspect telemetry in Azure Monitor.
In This Section
Prerequisites
Learn about the prerequisites for deploying NCache Cloud on Azure including resource groups, VNet subnets, Entra ID P2 JIT licensing, permissions, and marketplace image terms.
Get NCache Cloud from Azure Marketplace
Step-by-step guide to deploying NCache Cloud via Azure Marketplace. Configure plans, VMSS clustering, geo-replication, JIT access, and Entra ID authentication.
Azure Monitor Dashboards
View real-time NCache performance metrics, cache operations, and service logs using Azure Monitor dashboards with Grafana.
Azure Resources Created
Detailed reference for Azure resources deployed with NCache Cloud: VMSS scale sets, private DNS endpoints, Front Door URLs, NSG rules, and node health probing.
Connect to VMSS
Learn how to connect to NCache Cloud VMSS host instances in Azure using SSH and Azure Bastion via private IP addresses.