Installation · Lesson

Azure

Quick answer

On Azure, run IdentityIQ on VMs or AKS with Azure SQL/managed database behind Application Gateway, using Key Vault for secrets.

Key takeaways

Prerequisites for Azure
Step-by-step install path
Common pitfalls and fixes
Verification after install

On Microsoft Azure, IdentityIQ runs on virtual machines or an AKS cluster, backed by Azure SQL (or a managed database), fronted by Application Gateway, with secrets in Azure Key Vault and access governed by network security groups and Azure identity. The pattern mirrors AWS using Azure equivalents.

Reference architecture

Compute: Azure VMs or AKS pods running Tomcat + the IdentityIQ WAR.
Database: Azure SQL or a managed database offering backups and HA.
Load balancing: Application Gateway (with WAF where required) in front of the nodes.
Secrets: Azure Key Vault for database and integration credentials.

Step by step

1. Provision compute, VMs or AKS, sized for UI and task workloads.
2. Create the managed database and run the IdentityIQ DDL.
3. Configure the datasource to the database endpoint, retrieving credentials from Key Vault.
4. Front with Application Gateway and health probes.
5. Secure networking with NSGs and least-privilege identities.
6. Deploy and verify, then run a test aggregation.

Azure best practice

Choose a database tier with built-in HA and backups.
Keep all secrets in Key Vault.
Use NSGs to restrict access to the database and management ports.
Distribute nodes across availability zones.

Common pitfalls

Secrets outside Key Vault.
Open NSGs exposing the database.
No zone redundancy for the database.

Want to learn this properly?

Our live, instructor-led SailPoint Training covers this hands-on, with real projects and a certification path.

See the course Ask a question

Check your understanding

What are the prerequisites for Azure?
- A. A supported Java runtime, a reachable database, and the IdentityIQ files with correct permissions.
- B. Confirm the app server starts, the schema is present, and login works.
- C. The application and app-server logs, which usually point to database, Java or permission issues.
Show answer
A. A supported Java runtime, a reachable database, and the IdentityIQ files with correct permissions.
A supported Java runtime, a reachable database, and the IdentityIQ files with correct permissions.
How do you verify the install?
- A. Confirm the app server starts, the schema is present, and login works.
- B. A supported Java runtime, a reachable database, and the IdentityIQ files with correct permissions.
- C. The application and app-server logs, which usually point to database, Java or permission issues.
Show answer
A. Confirm the app server starts, the schema is present, and login works.
Confirm the app server starts, the schema is present, and login works.
Where do you look first on failure?
- A. Confirm the app server starts, the schema is present, and login works.
- B. A supported Java runtime, a reachable database, and the IdentityIQ files with correct permissions.
- C. The application and app-server logs, which usually point to database, Java or permission issues.
Show answer
C. The application and app-server logs, which usually point to database, Java or permission issues.
The application and app-server logs, which usually point to database, Java or permission issues.

Frequently asked questions

What else is worth knowing about Azure?

Compute: Azure VMs or AKS pods running Tomcat + the IdentityIQ WAR. Database: Azure SQL or a managed database offering backups and HA. Load balancing: Application Gateway (with WAF where required) in front of the nodes.

What is the practical takeaway on Azure?

1. Provision compute, VMs or AKS, sized for UI and task workloads. 2. Create the managed database and run the IdentityIQ DDL. 3. Configure the datasource to the database endpoint, retrieving credentials from Key Vault.

What tends to go wrong with Azure?

Secrets outside Key Vault. Open NSGs exposing the database. No zone redundancy for the database.