What causes OAuth2ClientIdColonNotAllowed?

Colon not allowed in OAuth2 client ID. Integration runtime configuration is incorrect or outdated. Authentication credentials or permissions are insufficient. The feature or setting is not supported for the selected connector or copy mode

How do I fix OAuth2ClientIdColonNotAllowed?

Open the linked service in ADF Studio and locate the 'Client ID' field in the OAuth2 authentication section — check the value for a colon character (:).. Remove the colon from the client ID — a valid OAuth2 client ID should not contain a colon; the colon is a delimiter used in HTTP Basic authentication encoding, and ADF rejects it in the client ID field.. If the value is a combined 'client_id:client_secret' string copied from API documentation, split it: place the part before the colon in the Client ID field and the part after in the Client Secret field.. Verify the correct client ID format with the API provider — most OAuth2 client IDs are UUIDs, alphanumeric strings, or names without special characters.. Save the linked service and test the connection to confirm the fix before running the next pipeline.

Medium severityconfiguration

Power BI Refresh Error:
OAuth2ClientIdColonNotAllowed

What does this error mean?

The OAuth2 client ID configured in the ADF linked service contains a colon character, which is not permitted. Update the client ID to remove the colon.

Common causes

1Colon not allowed in OAuth2 client ID
2Integration runtime configuration is incorrect or outdated
3Authentication credentials or permissions are insufficient
4The feature or setting is not supported for the selected connector or copy mode

How to fix it

1Open the linked service in ADF Studio and locate the 'Client ID' field in the OAuth2 authentication section — check the value for a colon character (:).
2Remove the colon from the client ID — a valid OAuth2 client ID should not contain a colon; the colon is a delimiter used in HTTP Basic authentication encoding, and ADF rejects it in the client ID field.
3If the value is a combined 'client_id:client_secret' string copied from API documentation, split it: place the part before the colon in the Client ID field and the part after in the Client Secret field.
4Verify the correct client ID format with the API provider — most OAuth2 client IDs are UUIDs, alphanumeric strings, or names without special characters.
5Save the linked service and test the connection to confirm the fix before running the next pipeline.

Frequently asked questions

Does this configuration error affect every pipeline run?

Yes — configuration errors are deterministic. Every run fails until fixed; retrying does not help.

How do I validate an ADF pipeline configuration before running it?

Click 'Validate' in the ADF authoring UI for configuration checks. For data flows, use Debug mode with a small sample to validate expressions and mappings.

Can dynamic content expressions in ADF cause configuration errors at runtime?

Yes — @activity(), @pipeline(), or @dataset() parameters that resolve to null or an unexpected type cause runtime failures even when design-time validation passes.

Do configuration errors appear in the ADF activity output?

Yes — the ADF Monitor activity detail shows the error code and the specific property that is invalid or missing.

Official documentation: https://learn.microsoft.com/en-us/azure/data-factory/connector-troubleshoot-guide