Sync Azure Tags to LightMesh

Overview

This guide explains how to sync Azure Virtual Network (VNet) tags into LightMesh and use them for subnet filtering.

After you connect an Azure account, LightMesh discovers tags on your cloud networking resources during sync. You choose which tag keys to map onto LightMesh subnets. Once mapped and synced, those tags appear on subnet records and can be used as Cloud Tag filters on the Subnets page.

Prerequisite: You need an Azure cloud account connected in LightMesh. If you do not have one yet, follow Azure Integration (service principal setup), or use Add Azure Integration below.

Permission required: Managing cloud accounts requires an app role of Owner, Administrator, or Contributor. See Roles & RBAC for details.


Sync tags from an existing Azure integration

Use these steps when your Azure account is already connected and showing a Synchronized status.

Step 1: Open Cloud Integration

  1. Navigate to CloudCloud Accounts.
  2. Click your Azure account in the table.

Cloud Accounts list with an Azure account

Step 2: Trigger tag sync

  1. Open the account drawer (Summary tab).
  2. Click Sync Now.

Sync Now button on the Azure account drawer

Step 3: Wait for sync

Sync runs in the background. You can continue using the app while status shows Synchronizing.

Azure account status showing Synchronizing

Initial sync duration depends on the size of your Azure environment and may take a few minutes.

Step 4: View tags

  1. Re-open the Azure account record.
  2. Open the Tags tab.

Tags tab on the Azure account drawer

Step 5: Map tags

LightMesh lists tag keys detected on your cloud resources during the last sync.

  1. Review each Tag Key (for example, Agency, Country, Environment).
  2. Use the Sync to Subnets toggle to choose which keys LightMesh should apply to subnets.
  3. Changes take effect on the next sync — run Sync Now again after enabling toggles if you want them applied immediately.

Tag mapping toggles for Sync to Subnets

Important: Tag mapping is user-controlled. Nothing is auto-applied to subnets until you enable the toggle for that tag key.


Add Azure integration (if not configured)

If you do not yet have an Azure account in LightMesh, add one first, then map tags.

Step 1: Add a cloud account

  1. Go to Cloud.
  2. Click Connect an Azure Account (or + Add Cloud Account → Azure).

Step 2: Enter credentials

  1. Create a read-only service principal in Azure (see Azure Integration for the CLI command and scope options).
  2. In LightMesh, fill in:
    • Azure Cloud Environment (for example, Azure Commercial Cloud)
    • Name
    • App ID
    • Password
    • Tenant ID
  3. Click Finish Adding Account.

Add Azure Account form with service principal credentials

Note: Some credential values are redacted in screenshots for security.

Step 3: Sync starts

After you finish, status becomes Synchronizing while LightMesh discovers networks, subnets, and tags.

Cloud Accounts table showing Synchronizing status

Step 4: Configure tags

  1. Open the new Azure account record.
  2. Go to the Tags tab.
  3. Repeat the tag mapping steps above, then sync again so mapped tags apply to subnets.

Tags tab after initial Azure sync


Filter subnets using tags

After tags are mapped and synced, use them on the Subnets page.

Step 1: Open Subnets and Filters

  1. Open the Subnets page.
  2. Click + Add Filter.

Subnets page Add Filter with Cloud Tag attribute

Step 2: Apply a Cloud Tag filter

  1. Set Attribute to Cloud Tag.
  2. Choose a Tag Key (for example, Agency).
  3. Enter a Tag Value (for example, MPI).
  4. Click Add filter.

Add Filter dialog for Cloud Tag Agency = MPI

Step 3: View results

The subnet list updates to matching resources. Open a subnet to confirm cloud tags on the Summary view.

Filtered subnets for Tag Agency = MPI

Subnet Summary showing CLOUD TAGS Agency MPI and Country US


Notes

  • Tag sync is non-blocking (async). You can keep working while sync runs.
  • Initial sync may take a few minutes depending on Azure environment size.
  • Tag mapping is user-controlled — enable Sync to Subnets for each key you want applied.
  • Cloud Tag filters on Subnets are available only after tags have been synced and mapped.
  • For service principal setup, multiple subscriptions, and management group access, see Azure Integration.