Learn the recommended naming convention for Azure Data Factories: abbreviation, length limits, allowed characters, uniqueness scope, and real-world examples.
Check out our full Azure resource names reference for abbreviations and naming rules for all Azure resource types and regions.
Azure Data Factory (ADF) is a fully managed, serverless data integration service that lets you orchestrate and automate data movement and transformation at scale. It supports ingesting data from hundreds of sources, transforming it with mapping data flows or external compute, and loading it into analytics destinations.
Data Factory is a core component of modern Azure data platform architectures. Whether you're building an ELT pipeline into a Synapse Analytics workspace, migrating on-premises data to the cloud, or orchestrating a set of interdependent Databricks notebooks, ADF provides the scheduling, monitoring, and lineage tracking to keep your data pipelines reliable and observable.
The Microsoft Cloud Adoption Framework recommends a consistent naming pattern across all resource types. The standard structure is:
<resource-type>-<workload>-<environment>-<region>-<instance>The recommended abbreviation for an Azure Data Factory resource type is:
adfEvery Azure resource type has its own naming rules. Getting these rules wrong causes deployment failures, CI/CD pipeline breaks, and Azure Policy violations. The following rules apply to Azure Data Factory names.
The minimum and maximum length of the data factory name.
3 - 63Data Factory names may only contain alphanumeric characters and hyphens. The name must start and end with a letter or digit.
a-z, A-Z, 0-9, -Scope determines where a name must be unique. The scope of a data factory is:
GlobalThe name must be globally unique across all Azure customers and subscriptions.
The examples below follow a <resource-type>-<workload>-<environment>-<region>-<instance> pattern, aligned with Microsoft CAF guidance.
adf-ingest-prod-we-001Production ingestion pipeline in West Europeadf-etl-dev-eus-001Development ETL pipeline in East USadf-reporting-stg-ne-002Staging reporting pipeline in North Europeadf-migration-prod-wusProduction data migration factory in West USManually checking this reference before every data factory deployment is error-prone and slow. A better approach is to automate name generation and validation so that compliant names are produced by default and violations are caught before they reach your pipelines.
Clovernance applies all of these rules automatically. Configure your naming convention once, share it across your organization, and generate validated, CAF-compliant names for any resource type in seconds.
Stop cross-referencing naming rules manually. Let Clovernance handle it.