Xero 2.0 ADF connector not supporting the same tables as Xero 1.0 connector

Question

Xero 2.0 ADF connector not supporting the same tables as Xero 1.0 connector

Michael van Leent 0

The Xero 2.0 connector in ADF no longer supports the ProjectTasks and Time tables while the Xero 1.0 connector does. This is also mentioned in the documentation:

https://learn.microsoft.com/en-us/azure/data-factory/connector-xero?tabs=data-factory#dataset-properties

The Xero 1.0 connector is being deprecated and is end of life in a few days (March 31, 2026) and being removed completely (April 30, 2026):

https://learn.microsoft.com/en-us/azure/data-factory/connector-release-stages-and-timelines

What is the timeline for the Xero 2.0 connector to support the same tables again?

Michael van Leent 0 Reputation points

2026-03-25T13:33:13.6133333+00:00

Obviously this does not help at all. A bit strange that you are deprecating something that offers more functionality and cannot even offer a timeline on your own products.
Manoj Kumar Boyini 14,495 Reputation points Microsoft External Staff Moderator

2026-03-25T13:42:54.0233333+00:00

Hi Michael van Leent,

I understand the concern. The deprecation is driven by Xero retiring legacy APIs, not by Azure Data Factory removing functionality. The Xero 1.0 connector relied on those legacy APIs, which is why it supported additional tables.

The Xero 2.0 connector is built on Xero’s current, supported APIs, and only exposes what those APIs provide today. Because of that dependency, Microsoft can’t commit to a timeline for adding entities that aren’t currently available through the newer APIs.

I agree this is a disruptive change, but it reflects a necessary move to supported and maintainable integrations going forward. Please share the requested details for further process.
Michael van Leent 0 Reputation points

2026-03-25T13:47:28.5533333+00:00

Xero fully supports these through their API:

https://developer.xero.com/documentation/api/projects/tasks

https://developer.xero.com/documentation/api/projects/time

It appears the Xero 2.0 Azure Data Factory connector simply has not implemented this yet and cannot give a timeline on their implementation.
Manoj Kumar Boyini 14,495 Reputation points Microsoft External Staff Moderator

2026-04-21T18:13:27.9266667+00:00

Hi @Michael van Leent

We would like to clarify that workloads currently using the Xero 1.0 connector are covered under the automatic connector upgrade process in Azure Data Factory. This means that existing pipelines built on the 1.0 connector will be automatically upgraded on the service side as part of the retirement process, and you can continue to use them without requiring changes prior to the published removal timeline.

As such, there is no immediate requirement to migrate your existing 1.0 connector–based pipelines before April 30, 2026 in order to maintain continuity of ingestion for entities such as ProjectTasks and Time.

Reference : Automatic connector upgrade - Azure Data Factory | Microsoft Learn

Please let us know if you have any questions and concerns.
Manoj Kumar Boyini 14,495 Reputation points Microsoft External Staff Moderator

2026-04-22T17:01:38.2466667+00:00

Hi @Michael van Leent

I hope you had a chance to review the information shared earlier, and I hope this information has been helpful! If you still have questions, please let us know what is needed in the comments so the question can be answered.
Manoj Kumar Boyini 14,495 Reputation points Microsoft External Staff Moderator

2026-04-23T20:27:03.8633333+00:00

Hi @Michael van Leent

By the way regarding pagination, default value of pageSize is 100 in autoupgrade. So, If you want it to increase apgeSize to reduce the number of API requests, you can just add "pageSize" : 500 in V1 payload. There are two ways to add

At pipeline level payload "source": {

  "type": "XeroSource",

  "pageSize": 500

},

2. At DataSet level

{

  "name": "XeroObject1",

  "properties": {

  "linkedServiceName": {

  "referenceName": "XeroV1",

  "type": "LinkedServiceReference"

},

  "annotations": [],

  "type": "XeroObject",

  "schema": [],

  "typeProperties": {

  "tableName": ""Global"."Invoices"",

  "pageSize": 500

}

},

  "type": "Microsoft.DataFactory/factories/datasets"

}

Either of this is fine. 2nd is better option.

On supporting ProjectTasks & Time in V2, Currently PG team is working on It, will share the ETA Soon.
Manoj Kumar Boyini 14,495 Reputation points Microsoft External Staff Moderator

2026-04-24T19:51:45.3766667+00:00

Hi @Michael van Leent

Just checking in to see if the information provided earlier was helpful. Please let us know if you need any additional details or assistance, and we’ll gladly continue supporting you.

2 answers

Your answer

Michael van Leent 0 Reputation points

2026-03-25T13:33:13.6133333+00:00

Obviously this does not help at all. A bit strange that you are deprecating something that offers more functionality and cannot even offer a timeline on your own products.
Manoj Kumar Boyini 14,495 Reputation points Microsoft External Staff Moderator

2026-03-25T13:42:54.0233333+00:00

Hi Michael van Leent,

I understand the concern. The deprecation is driven by Xero retiring legacy APIs, not by Azure Data Factory removing functionality. The Xero 1.0 connector relied on those legacy APIs, which is why it supported additional tables.

The Xero 2.0 connector is built on Xero’s current, supported APIs, and only exposes what those APIs provide today. Because of that dependency, Microsoft can’t commit to a timeline for adding entities that aren’t currently available through the newer APIs.

I agree this is a disruptive change, but it reflects a necessary move to supported and maintainable integrations going forward. Please share the requested details for further process.
Michael van Leent 0 Reputation points

2026-03-25T13:47:28.5533333+00:00

Xero fully supports these through their API:

https://developer.xero.com/documentation/api/projects/tasks

https://developer.xero.com/documentation/api/projects/time

It appears the Xero 2.0 Azure Data Factory connector simply has not implemented this yet and cannot give a timeline on their implementation.
Manoj Kumar Boyini 14,495 Reputation points Microsoft External Staff Moderator

2026-04-21T18:13:27.9266667+00:00

Hi @Michael van Leent

We would like to clarify that workloads currently using the Xero 1.0 connector are covered under the automatic connector upgrade process in Azure Data Factory. This means that existing pipelines built on the 1.0 connector will be automatically upgraded on the service side as part of the retirement process, and you can continue to use them without requiring changes prior to the published removal timeline.

As such, there is no immediate requirement to migrate your existing 1.0 connector–based pipelines before April 30, 2026 in order to maintain continuity of ingestion for entities such as ProjectTasks and Time.

Reference : Automatic connector upgrade - Azure Data Factory | Microsoft Learn

Please let us know if you have any questions and concerns.
Manoj Kumar Boyini 14,495 Reputation points Microsoft External Staff Moderator

2026-04-22T17:01:38.2466667+00:00

Hi @Michael van Leent

I hope you had a chance to review the information shared earlier, and I hope this information has been helpful! If you still have questions, please let us know what is needed in the comments so the question can be answered.
Manoj Kumar Boyini 14,495 Reputation points Microsoft External Staff Moderator

2026-04-23T20:27:03.8633333+00:00

Hi @Michael van Leent

By the way regarding pagination, default value of pageSize is 100 in autoupgrade. So, If you want it to increase apgeSize to reduce the number of API requests, you can just add "pageSize" : 500 in V1 payload. There are two ways to add

At pipeline level payload "source": {

"type": "XeroSource",

"pageSize": 500

},

2. At DataSet level

{

"name": "XeroObject1",

"properties": {

"linkedServiceName": {

"referenceName": "XeroV1",

"type": "LinkedServiceReference"

},

"annotations": [],

"type": "XeroObject",

"schema": [],

"typeProperties": {

"tableName": ""Global"."Invoices"",

"pageSize": 500

}

},

"type": "Microsoft.DataFactory/factories/datasets"

}

Either of this is fine. 2nd is better option.

On supporting ProjectTasks & Time in V2, Currently PG team is working on It, will share the ETA Soon.
Manoj Kumar Boyini 14,495 Reputation points Microsoft External Staff Moderator

2026-04-24T19:51:45.3766667+00:00

Hi @Michael van Leent

Just checking in to see if the information provided earlier was helpful. Please let us know if you need any additional details or assistance, and we’ll gladly continue supporting you.

Answer 1

Manoj Kumar Boyini 14,495 Microsoft External Staff Moderator

Hi @Michael van Leent

The support for ProjectTasks and Time tables has already been added in Xero connector version 2.0 and is currently in the final stages of deployment. This update is expected to be available around mid-May 2026.

Once the deployment is completed, these tables should be accessible in the Xero 2.0 connector, bringing it closer to parity with version 1.0 for your use case.

Please let us know if you have any questions or concerns

Manoj Kumar Boyini 14,495 Reputation points Microsoft External Staff Moderator

2026-05-01T18:35:47.85+00:00

Hi @Michael van Leent

Just checking in to see if the information provided earlier was helpful. Please let us know if you need any additional details or assistance, and we’ll gladly continue supporting you.

Answer 2

Hi Michael van Leent,

You are correct. The Xero 2.0 connector in Azure Data Factory currently supports only the tables listed under Dataset Properties and does not include ProjectTasks or Time. This is expected behavior based on the APIs used by the V2 connector.

At this time, there is no publicly available timeline for adding these entities to the Xero 2.0 connector.

If ProjectTasks or Time data is required, the recommended approach is to retrieve this data directly from Xero using REST/HTTP activities in ADF, as these entities are not exposed through the native Xero 2.0 connector.

Add your ask on the Azure Data Factory feedback forum:
https://feedback.azure.com/forums/270578-azure-data-factory

Hope this helps, Please let us know if you have any questions and concerns

Share via

Xero 2.0 ADF connector not supporting the same tables as Xero 1.0 connector

2 answers

Your answer