Skip to main content

Link16 Identify

Automate and Enforce Naming Standards

Manage and generate collision-free resource names directly in the portal or in your CI/CD pipelines.

Starter template

az-plat-prod-uks-kv-01

CloudazWorkloadplatEnvprodRegionuksServicekvCounter01

Also works for

Azure Key Vault

az-plat-prod-uks-kv-01

AWS RDS

aws-fin-prod-euc1-rds-01

Shared app

corp-idp-shared-global-app-03

Ready-made standards

Start with cloud-ready templates

Skip the blank page. Link16 includes ready-to-use naming templates for common Azure and AWS services, helping teams standardize faster and adapt conventions to internal structures, environments, and regions.

Azure and AWS starter templates

Begin with curated patterns for common services and adapt them instead of inventing every rule from scratch.

Adapt to your structure

Tailor prefixes, regions, environments, workload codes, and counters to match company standards.

Roll out consistently

Turn a proven template into a reusable standard that projects can apply with the same logic everywhere.

DevOps & CI/CD

Infrastructure as Code, governed by default

Use Link16 naming modules directly in Terraform and Bicep so every resource name follows approved conventions. Validate through CI pipelines and automate governance via REST API - no manual naming reviews required.

Terraform & Bicep modules

Reference central naming templates as native IaC modules - names resolve at plan time against live governance rules.

REST API access

Generate, validate, and reserve names programmatically from any automation, script, or internal tooling through a versioned API.

CI pipeline validation

Run pre-deployment checks that catch naming conflicts, policy violations, and reserved-word collisions before changes reach production.

module "naming" {
  source  = "link16/naming/azurerm"
  version = "~> 1.0"

  template_id = "azure-resource-group"
  parameters  = {
    environment = var.environment
    region      = var.location
    workload    = "payments"
  }
}

resource "azurerm_resource_group" "main" {
  name     = module.naming.result
  location = module.naming.region
}

resource "azurerm_key_vault" "main" {
  name                = module.naming.resources["key-vault"]
  location            = azurerm_resource_group.main.location
  resource_group_name = azurerm_resource_group.main.name
  sku_name            = "standard"
}
Names resolve from central Link16 governance at plan time

Integration flow

Name Request

API or portal trigger

Link16 Engine

Validate, approve & route

Approved Name

Compliant & ready to distribute

CMDB

Service Portal

Ticket System

Approval

Integrations

Integrate with your delivery ecosystem

Link16 connects to the systems your teams already use - CMDBs, service portals, ticketing platforms, and approval workflows - so naming governance happens in the flow of work, not alongside it.

CMDB synchronization

Push approved names and metadata directly into your configuration management database so asset records stay aligned with what's deployed.

Service portal & ticketing

Embed naming requests into existing self-service portals and ticket workflows so teams get compliant names without leaving their tools.

Approval process hooks

Route naming requests through configurable approval chains that connect to your existing change management and governance processes.

Try it yourself

See It in Action

Generate a name from a template to see how naming conventions work in practice.

Create and Use Naming Templates

Build templates with clear rules that catch mistakes before you name resources.

One-Click Name Generation

Produce accurate names instantly and avoid manual errors.

Share and Track

Let your team use your templates, approve names and see a full history of every name you create.

Virtual Machine Template

  • vm
  • -
  • text
  • -
  • environment
  • -
  • counter
00 / 99
Press Generate