Supported Azure environments, resources, and lines

Written by:  Shanna S
Last updated:  

Lucidscale can be used to import cloud infrastructure data from Azure. For a comprehensive list of the supported environments, resources, and lines from Azure that are available in Lucidscale read this article.

For instructions on importing cloud infrastructure data from Azure and using it to generate diagrams in Lucidscale, refer to our Import and manage Azure infrastructure data in Lucidscale article.

Supported environments

Lucid supports data import from the following distinct Azure cloud environments: 

  • Global Azure (AzureCloud): This is the standard, commercial public cloud available worldwide.
  • Azure Government (AzureUSGovernment): This is a physically and logically isolated cloud instance for US government agencies and their partners.

Note: Other sovereign cloud environments, such as Azure China, are operated as separate instances from Global Azure and cannot currently be imported by Lucid due to technical and regulatory separation.

Supported resources

Lucid provides automated diagramming for the following Azure resources. These resources are referred to as “mapped resources” within Lucid editors.

Analytics

  • Azure Databricks Workspaces
  • Event Hubs
  • Event Hubs Namespaces
  • HDInsight clusters
  • Log Analytics Workspaces

Compute

  • Kubernetes clusters
  • Disks
  • Virtual Machines
  • Virtual Machine Scale Sets

Database

  • Caches for Redis
  • Cosmos Database Accounts
  • Data Factories
  • MySQL Databases
  • MySQL (Single) Servers
  • PostgreSQL Databases
  • PostgreSQL (Single) Servers
  • SQL Servers
  • SQL Databases
  • SQL Managed Instances

Integration

  • Event Grid Domains
  • Event Grid Topics
  • Logic Apps Workflows
  • Service Bus Namespaces

Internet of Things

  • IoT Hub

Management group

  • Management groups (hierarchical container; imported for scoping where available)
  • Resource groups
  • Subscriptions

Networking

  • Application Gateways
  • Application Security Groups
  • DNS Zones
  • ExpressRoute Circuits
  • Firewalls
  • Front Doors (Classic)
  • Front Doors and CDN Profiles (Standard/Premium)
  • Local Network Gateways
  • Load Balancers
  • Network Interfaces
  • Network Security Groups
  • Private DNS Zones
  • Private Endpoints (Cosmos DB, Service Bus, Functions, Key Vault, Web Apps)
  • Public IP Addresses
  • Route Tables
  • Subnets
  • Traffic Manager Profiles
  • Virtual Network Gateways
  • Virtual Network Gateway Connections
  • Virtual Networks
  • Virtual WANs

Security & Management

  • Key Vaults
  • User-Assigned (Managed) Identities

Storage

  • File Shares
  • Storage Accounts
  • Storage Queues

Web & Mobile

  • API Management Services
  • App Service Plans
  • Web Apps

Additional imported resource metadata, also known as unmapped resources, are available in your Cloud Inventory for manual placement.

Supported lines

Lucid provides built-in support for automatically drawing the following line types based on relationships defined in Azure metadata:

Compute

  • Virtual Machines → Disk

Content Delivery

  • Front Door (Classic) → Application Gateways
  • Front Door (Classic) → Traffic Manager Profiles
  • Front Door (Classic) → Web Apps
  • Front Door Standard/Premium → Application Gateways
  • Front Door Standard/Premium → Traffic Manager Profiles
  • Front Door Standard/Premium → Web Apps

Load Balancing

  • Application Gateway → Virtual Machine
  • Application Gateway → Virtual Machine Scale Set
  • Application Gateway → Web App
  • Load Balancer → Virtual Machine

Networking

  • Private Endpoint → Cosmos Database Account
  • Private Endpoint → Key Vault
  • Private Endpoint → Service Bus Namespace
  • Private Endpoint → Subnet
  • Private Endpoint → Web App
  • Virtual Machines → Subnet
  • Virtual Machines Scale Set → Subnet
  • Virtual Network Peerings [VNET → VNET]
  • Virtual Network Gateway → Connection  → Local Network Gateway
  • Virtual Network Gateway → Connection  → Virtual Network Gateway

Note: Lines are only shown for individual resources that are visible on the canvas. Hiding, filtering, or summarizing resources will hide their lines until both connected resources are fully visible again.

Did you find what you were looking for?

Still have a question or want to share what you have learned? Visit our Community   to get help and collaborate with others.