Rules for naming Azure Data Factory entities

Tip

Try out Data Factory in Microsoft Fabric, an all-in-one analytics solution for enterprises. Microsoft Fabric covers everything from data movement to data science, real-time analytics, business intelligence, and reporting. Learn how to start a new trial for free!

The following table provides naming rules for Data Factory artifacts.

Name	Name Uniqueness	Validation Checks
Data factory	Unique across Microsoft Azure. Names are case-insensitive, that is, `MyDF` and `mydf` refer to the same data factory.	Each data factory is tied to exactly one Azure subscription. Object names must start with a letter or a number, and can contain only letters, numbers, and the dash (-) character. Every dash (-) character must be immediately preceded and followed by a letter or a number. Consecutive dashes are not permitted in container names. Name can be 3-63 characters long.
Linked services/Datasets/Pipelines/Data Flows	Unique within a data factory. Names are case-insensitive.	Object names must start with a letter. The following characters are not allowed: “.”, “+”, “?”, “/”, “<”, ”>”,”*”,”%”,”&”,”:”,”\” Dashes ("-") are not allowed in the names of linked services, data flows, and datasets.
Integration Runtime	Unique within a data factory. Names are case-insensitive.	Integration runtime Name can contain only letters, numbers and the dash (-) character. The first and last characters must be a letter or number. Every dash (-) character must be immediately preceded and followed by a letter or a number. Consecutive dashes are not permitted in integration runtime name.
Data flow transformations	Unique within a data flow. Names are case-insensitive	Data flow transformation names can only contain letters and numbers The first character must be a letter.
Resource Group	Unique across Microsoft Azure. Names are case-insensitive.	For more info, see Azure naming rules and restrictions.
Pipeline parameters & variable	Unique within the pipeline. Names are case-insensitive.	Validation check on parameter names and variable names is limited to uniqueness because of backward compatibility reason. When use parameters or variables to reference entity names, for example linked service, the entity naming rules apply. A good practice is to follow data flow transformation naming rules to name your pipeline parameters and variables.

Feedback

Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.

Submit and view feedback for

This product This page

View all page feedback

Rules for naming Azure Data Factory entities - Azure Data Factory (2024)

Related content

Feedback