Data Factory: HubSpot Connector Out of Date — Errors with Certain Endpoints

Question

Data Factory: HubSpot Connector Out of Date — Errors with Certain Endpoints

Noah Daniels 0

Problem description

I am experiencing errors when using the Azure Data Factory HubSpot connector 2.0, particularly when accessing certain endpoints like the marketing campaigns table during a source-data update pipeline. The behavior did not meet my expectations for newer HubSpot API coverage, and I suspect the connector might be outdated.

Environment

Azure Data Factory using the HubSpot connector 2.0 in the region not specified in the case information.

What I've already tried

I reviewed the Azure Data Factory HubSpot connector documentation, tested different endpoints including the marketing campaigns table, and monitored API calls from HubSpot. I also compared the connector's last update date (03/25/2026) with HubSpot API update dates (06/23/2026).

Current status

Currently, errors persist on certain endpoints, especially the marketing campaigns table, when trying to access newer API data. I am seeking guidance on whether the connector needs an update, what specific error messages indicate, and how to resolve the issue.

Current Error Example

Endpoint: /marketing/campaigns/v3

Status Code: 400

Error Response Body:


{"status":"error","message":"Forbidden
properties: [createdAt, id, updatedAt] in the provided property set. Correct
ones are [hs_start_date, hs_end_date, hs_color_hex, hs_notes, hs_audience,
hs_goal, hs_owner, hs_currency_code, hs_created_by_user_id, hs_campaign_status,
hs_object_id, hs_name, hs_utm, hs_budget_items_sum_amount,
hs_spend_items_sum_amount, hs_business_unit_ids] and custom properties you have
defined for
Campaign.","correlationId":"[REDACTED]","context":{"forbidden-properties":["[createdAt,
id,
updatedAt]"]},"category":"VALIDATION_ERROR","subCategory":"CampaignApiError.PROPERTY_SET_CONTAINS_VALUES_FORBIDDEN_FOR_READ"}

Ganesh Chelluri 195 Reputation points Microsoft External Staff Moderator

2026-09-16T23:57:52.9233333+00:00
Hi @Noah Daniels ,

Thank you for sharing the detailed error.

Azure Data Factory HubSpot Connector version 2.0 is supported, but it supports only the HubSpot tables listed under Dataset properties in the connector documentation.

Please verify whether Marketing Campaigns is included in that supported table list:

If Marketing Campaigns is listed, review the source query or column mapping and remove createdAt, id, and updatedAt from the requested property set because HubSpot is rejecting those properties for read access. Then rerun the pipeline and confirm that the PROPERTY_SET_CONTAINS_VALUES_FORBIDDEN_FOR_READ error no longer occurs.

If Marketing Campaigns is not listed, this is an unsupported scenario for the native Azure Data Factory HubSpot Connector 2.0. In that case, use the Azure Data Factory REST connector to call the required HubSpot API endpoint.
Noah Daniels 0 Reputation points

2026-09-17T18:51:49.1966667+00:00
Hi Ganesh,

The Connector version 2.0 does support that HubSpot table. We are only looking to to access tables that are available through the Connector in the documentation and have looked through as much as we can on our end: https://learn.microsoft.com/en-us/azure/data-factory/connector-hubspot?tabs=data-factory#dataset-properties

Since I am using the Connector, I am limited in what fields I am able to pull and the functionality of the API calls used in the Connector. In the "Mapping" tab of Azure Data Factory's Copy data Activity, I am only mapping a single correct field (hs_start_date; this was explicitly labeled as correct in the API Error Response Body) and still receiving the same error. This suggests that this needs to be fixed within the Connector itself -- the incorrect fields are being pulled regardless.

The "Import schemas" and "Preview source" buttons in the above screenshot also yield the same 400 Error in the response:

Failed to read from the source connector. Error code: 'Unknown', message: 'Bad Request' Bad Request

Please let me know if I can check anything else on my end!

Best,

Noah
Noah Daniels 0 Reputation points

2026-09-18T17:23:35.3866667+00:00

Hi Ganesh,

After review, it looks like my comment was submitted as an answer by mistake. Bumping this thread to make sure this is updated properly.Best,

Noah
Ganesh Chelluri 195 Reputation points Microsoft External Staff Moderator

2026-09-20T22:05:10.9+00:00
Hi @Noah Daniels ,

Apologies for the delay,

The HTTP 400 response is generated because the source request includes createdAt, id, and updatedAt. HubSpot identifies these values as forbidden for Campaign read operations. Changing the Copy Activity mapping does not correct this because Preview source and Import schemas fail before sink mapping is applied.

Please use the following resolution:

Confirm that the HubSpot linked service is configured with connector version 2.0.

Create a new HubSpot dataset and select Marketing.Campaigns.

In the Copy Activity source settings, use a custom query instead of the default full-table read.

Explicitly select only the readable Campaign properties required by the pipeline, such as hs_start_date and the other hs_ campaign fields returned as valid by HubSpot.

Do not include createdAt, id, or updatedAt in the custom source query.

Run Preview source again.

If Preview source succeeds, import the resulting schema and complete the sink mapping.

Run the Copy Activity with a limited test dataset and confirm that the activity completes successfully.

The documented connector supports Marketing.Campaigns, but the default schema-discovery request is incompatible with the current HubSpot Campaign API when it includes the forbidden properties. Using the connector’s documented custom-query option allows the pipeline to request only the supported Campaign fields.

If the same forbidden-property response occurs even with a new dataset and an explicit custom query containing only allowed hs_ properties, the native HubSpot connector cannot complete this Campaign read in the current configuration. The reliable alternative is to use an Azure Data Factory REST source for the HubSpot Campaign API so the requested property list is controlled explicitly.
Noah Daniels 0 Reputation points

2026-09-21T05:13:46.2466667+00:00
Hi @Ganesh Chelluri ,

We do not have the capability to change the Source settings for querying on our end.

Confirm that the HubSpot linked service is configured with connector version 2.0.

When creating a new Linked Service, there is only one option for the HubSpot connector. This follows the 2.0 version documentation and what we are using on our end:

Create a new HubSpot dataset and select Marketing.Campaigns.

This is how we have set this up. Here is a screenshot:

In the Copy Activity source settings, use a custom query instead of the default full-table read.

This is not currently possible with the Connector, unless I am missing something somewhere in the Copy Activity:

We have tried these things and attempted to raise an Azure Support ticket but we were routed to a public Q&A forum. Is it possible to escalate this to our Account's support to get this resolved more directly? This is unfortunately starting to have some more significant business impact for our team.

Please let me know what's possible as soon as you can and if you have any other questions. If you can provide screenshots or examples from your end where you are successfully using the Connector 2.0 to connect to Marketing.Campaigns, that would be extremely helpful as well.

Best,
Noah
Noah Daniels 0 Reputation points

2026-09-23T17:33:34.2033333+00:00

Hi @Ganesh Chelluri ,

I wanted to follow up here because we need this data ASAP. We figured we could escalate this fix through Azure Support but we are reaching a week since we've reached out with no solution or proposal in place.

It does not seem like there is clear documentation and understanding of the Connector through this Support channel. Is there any way to escalate this to the Connector team or should we start looking at other alternatives to Azure Connectors?

Please let me know as soon as possible.

Best,

Noah

Your answer

Ganesh Chelluri 195 Reputation points Microsoft External Staff Moderator

2026-09-16T23:57:52.9233333+00:00

Hi @Noah Daniels ,

Thank you for sharing the detailed error.

Azure Data Factory HubSpot Connector version 2.0 is supported, but it supports only the HubSpot tables listed under Dataset properties in the connector documentation.

Please verify whether Marketing Campaigns is included in that supported table list:

If Marketing Campaigns is listed, review the source query or column mapping and remove createdAt, id, and updatedAt from the requested property set because HubSpot is rejecting those properties for read access. Then rerun the pipeline and confirm that the PROPERTY_SET_CONTAINS_VALUES_FORBIDDEN_FOR_READ error no longer occurs.

If Marketing Campaigns is not listed, this is an unsupported scenario for the native Azure Data Factory HubSpot Connector 2.0. In that case, use the Azure Data Factory REST connector to call the required HubSpot API endpoint.
Noah Daniels 0 Reputation points

2026-09-17T18:51:49.1966667+00:00

Hi Ganesh,

The Connector version 2.0 does support that HubSpot table. We are only looking to to access tables that are available through the Connector in the documentation and have looked through as much as we can on our end: https://learn.microsoft.com/en-us/azure/data-factory/connector-hubspot?tabs=data-factory#dataset-properties

Since I am using the Connector, I am limited in what fields I am able to pull and the functionality of the API calls used in the Connector. In the "Mapping" tab of Azure Data Factory's Copy data Activity, I am only mapping a single correct field (hs_start_date; this was explicitly labeled as correct in the API Error Response Body) and still receiving the same error. This suggests that this needs to be fixed within the Connector itself -- the incorrect fields are being pulled regardless.

The "Import schemas" and "Preview source" buttons in the above screenshot also yield the same 400 Error in the response:

Failed to read from the source connector. Error code: 'Unknown', message: 'Bad Request' Bad Request

Please let me know if I can check anything else on my end!

Best,

Noah
Noah Daniels 0 Reputation points

2026-09-18T17:23:35.3866667+00:00

Hi Ganesh,

After review, it looks like my comment was submitted as an answer by mistake. Bumping this thread to make sure this is updated properly.Best,

Noah
Ganesh Chelluri 195 Reputation points Microsoft External Staff Moderator

2026-09-20T22:05:10.9+00:00

Hi @Noah Daniels ,

Apologies for the delay,

The HTTP 400 response is generated because the source request includes createdAt, id, and updatedAt. HubSpot identifies these values as forbidden for Campaign read operations. Changing the Copy Activity mapping does not correct this because Preview source and Import schemas fail before sink mapping is applied.

Please use the following resolution:

Confirm that the HubSpot linked service is configured with connector version 2.0.

Create a new HubSpot dataset and select Marketing.Campaigns.

In the Copy Activity source settings, use a custom query instead of the default full-table read.

Explicitly select only the readable Campaign properties required by the pipeline, such as hs_start_date and the other hs_ campaign fields returned as valid by HubSpot.

Do not include createdAt, id, or updatedAt in the custom source query.

Run Preview source again.

If Preview source succeeds, import the resulting schema and complete the sink mapping.

Run the Copy Activity with a limited test dataset and confirm that the activity completes successfully.

The documented connector supports Marketing.Campaigns, but the default schema-discovery request is incompatible with the current HubSpot Campaign API when it includes the forbidden properties. Using the connector’s documented custom-query option allows the pipeline to request only the supported Campaign fields.

If the same forbidden-property response occurs even with a new dataset and an explicit custom query containing only allowed hs_ properties, the native HubSpot connector cannot complete this Campaign read in the current configuration. The reliable alternative is to use an Azure Data Factory REST source for the HubSpot Campaign API so the requested property list is controlled explicitly.
Noah Daniels 0 Reputation points

2026-09-21T05:13:46.2466667+00:00

Hi @Ganesh Chelluri ,

We do not have the capability to change the Source settings for querying on our end.

Confirm that the HubSpot linked service is configured with connector version 2.0.

When creating a new Linked Service, there is only one option for the HubSpot connector. This follows the 2.0 version documentation and what we are using on our end:

Create a new HubSpot dataset and select Marketing.Campaigns.

This is how we have set this up. Here is a screenshot:

In the Copy Activity source settings, use a custom query instead of the default full-table read.

This is not currently possible with the Connector, unless I am missing something somewhere in the Copy Activity:

We have tried these things and attempted to raise an Azure Support ticket but we were routed to a public Q&A forum. Is it possible to escalate this to our Account's support to get this resolved more directly? This is unfortunately starting to have some more significant business impact for our team.

Please let me know what's possible as soon as you can and if you have any other questions. If you can provide screenshots or examples from your end where you are successfully using the Connector 2.0 to connect to Marketing.Campaigns, that would be extremely helpful as well.

Best,
Noah
Noah Daniels 0 Reputation points

2026-09-23T17:33:34.2033333+00:00

Hi @Ganesh Chelluri ,

I wanted to follow up here because we need this data ASAP. We figured we could escalate this fix through Azure Support but we are reaching a week since we've reached out with no solution or proposal in place.

It does not seem like there is clear documentation and understanding of the Connector through this Support channel. Is there any way to escalate this to the Connector team or should we start looking at other alternatives to Azure Connectors?

Please let me know as soon as possible.

Best,

Noah