Skip to content

Cloud Import#

Coming Soon

Direct cloud account import is coming in March 2026 (Azure) and Early July 2026 (AWS) as part of our cloud sync features.

Cloudeval currently works with Infrastructure as Code files (ARM templates). For cloud sync features, view our roadmap.

Join our waitlist to be notified when this feature launches.

Current Status#

Cloudeval currently supports:

Infrastructure as Code

  • Infrastructure as Code - Upload ARM templates and Bicep files
  • Web Editor - Edit your IaC files directly in the browser
  • AI Analysis - Get insights about your infrastructure code
  • Diagram Generation - Visualize your infrastructure from code

Coming Soon: Azure Cloud Import#

We're working on direct Azure account connections. Here's what's planned:

Automatic Discovery#

  1. Connect Azure Subscription - Provide read-only API access
  2. Resource Scanning - Cloudeval scans your Azure subscription
  3. Metadata Collection - Gathers resource properties and relationships
  4. Relationship Mapping - Identifies connections and dependencies
  5. Diagram Generation - Creates interactive visualization

Planned Features#

Connection Methods:

  • Service Principal (recommended)
  • Managed Identity
  • OAuth for personal accounts

Supported Azure Services:

  • Virtual Machines
  • Virtual Networks (VNets, Subnets)
  • Storage Accounts
  • SQL Databases
  • App Services
  • Resource Groups
  • Key Vaults
  • Load Balancers
  • Azure Functions
  • And 40+ more services

Discovery Methods:

  • Azure Resource Manager API
  • Resource Graph queries
  • ARM template analysis
  • Resource tagging

Current Workflow: Infrastructure as Code#

While cloud import is in development, use Infrastructure as Code:

Step 1: Export Your Infrastructure#

From Azure:

# Export resource group as ARM template
az group export --name my-resource-group --output-file template.json

From Bicep:

# Use Bicep files directly, or compile to ARM
az bicep build --file main.bicep

Step 2: Upload to Cloudeval#

  1. Create a new project
  2. Upload your ARM template or Bicep file
  3. Cloudeval parses and generates diagram
  4. Edit and analyze your infrastructure

Step 3: Keep in Sync#

  • Export templates regularly
  • Upload updated files
  • Compare versions over time
  • Track changes

Benefits of Current Approach#

Advantages:

  • Works with any IaC setup
  • Version control friendly
  • No cloud credentials needed
  • Works offline
  • Review before deployment
  • CI/CD integration ready

Best Practices:

  • Keep templates in source control
  • Export regularly
  • Use modular templates
  • Document changes

Get Notified#

Join our waitlist to be notified when cloud import features launch.

Next Steps#

Questions? Contact support or join our community