Azure Jira Connector - Upgraded Version and Dataset Warning.

Question

Azure Jira Connector - Upgraded Version and Dataset Warning.

Gue, David 90

When trying to upgrade my Azure Linked Service to the new (non-deprecated) version of Jira Connector, my dataset referencing the new linked service will not update (still getting the warning "...older version will be deprecated soon. ..." on the dataset.

I've recreated the linked service, and I've recreated the dataset (referencing the newly created linked service).

1 answer

Your answer

Answer 1

Swapnesh Panchal 665 Microsoft External Staff Moderator

Hi Gue, David,
Welcome to the Microsoft Q&A and thank you for posting your questions here.
Warning is attached to the dataset’s connector type, not just the linked service.
If the dataset was created from the older Jira connector (or cloned from one), it will keep the “older version will be deprecated soon” banner even after you point it to a new linked service.

What usually fixes it:

Create a brand-new dataset from the new Jira connector card (don’t clone the old one).
Pick the upgraded linked service and re-select the table/JQL options so the dataset JSON is generated with the new connector schema (OAuth2 props, new type name/fields).
Re-point every activity that used the old dataset to this new dataset. In ADF, use View all references or search the repo for the old dataset/linked-service name to catch any inlined sources in Copy/Data Flows.
Publish the changes, then open Live mode (or refresh the browser) to confirm the banner is gone.
Remove the old dataset and (if still around) the old linked service.

After those steps the dataset warning should disappear. If it doesn’t, there’s likely still an old dataset/inlined source in the pipeline referencing the deprecated connector.

Gue, David 90 Reputation points

2025-10-14T15:41:09.74+00:00

Hi, Swapnesh ... thank you for the quick & detailed reply!

I'm still getting the warning message (at step #2). I created a new linked service, and I created a new Dataset - when creating the new dataset and selecting the new linked service, the warning message appears.

Thx. Dave.
Abhisek Mishra 845 Reputation points Microsoft External Staff Moderator

2025-10-15T06:32:05.5966667+00:00
Hi Gue, David,

The warning is still being triggered despite creating a new linked service and dataset. We have reached out to you, over private message for some information, please share the details over private message. This will help us to investigate further.

Please follow the below links to Upgrade the connectors.

https://free.blessedness.top/en-us/azure/data-factory/connector-upgrade-advisor?source=recommendations

https://free.blessedness.top/en-us/azure/data-factory/connector-deprecation-frequently-asked-questions?source=recommendations

https://free.blessedness.top/en-us/azure/data-factory/connector-upgrade-guidance?source=recommendations

Thanks,

Abhisek
Gue, David 90 Reputation points

2025-10-15T16:51:37.0333333+00:00

Hi Abhisek ... please see details in the private chat.

Also, I'll look through the URLs you provided for upgrading the connector.

Thank you!
Swapnesh Panchal 665 Reputation points Microsoft External Staff Moderator

2025-10-16T22:06:31.17+00:00

Hi Gue, David,
Just checking in, if you have any questions or need clarification, feel free to let us know. We’d be happy to continue the conversation whenever you’re ready
Gue, David 90 Reputation points

2025-10-21T21:00:36.12+00:00

Hi, Swapnesh & Abhisek ... I went through the 3 support URLs provided and entered my responses in the private conversation.
Swapnesh Panchal 665 Reputation points Microsoft External Staff Moderator

2025-10-22T15:02:38.11+00:00
Hi Gue, David,
Appreciate your patience. We’ll do a deeper pass with additional steps. please do share any observations below. If you If still a workaround is needed, we’ll outline options.

as i can see the banner was coming from the dataset’s connector type, not the linked service. The dataset had been created from the old Jira tile, so the legacy type stuck around even after we pointed it at a new LS.

What we did /show

Opened the dataset “View code” and confirmed the connector type differs from the legacy one.

Published, checked in Live (fresh InPrivate window) to rule out cache.

Found one Mapping Data Flow parameter still referencing the old dataset; updated it.

JSON shows the new connector type with regenerated typeProperties.

Live view has no deprecation banner.

Test copy run succeeded with the new dataset.

If the banner ever reappears Send/reshare the dataset JSON, the UTC time you opened the blade, and the x-ms-client-request-id from the browser Network tab so we can trace it quickly.

Thanks for the screenshots—they made it easy to spot the leftover reference.
Swapnesh Panchal 665 Reputation points Microsoft External Staff Moderator

2025-10-23T17:43:11.1633333+00:00

Hi Gue, David,
Checking in! If you need any clarification or have questions, let us know. We’re here whenever you’d like to continue.
Gue, David 90 Reputation points

2025-10-24T15:01:08.22+00:00

Hi, team ... I just noticed Swapnesh Panchal's entry from 10/22/25, I'll review and provide an update. Thx!
Gue, David 90 Reputation points

2025-10-24T15:28:28.7966667+00:00

Hi, Swapnesh Panchal ... in the dataset json view, the "type:" is set to "JiraObject". I did create a new Linked Service (does not have any warning message), and I did create a new dataset - after pointing to the newly created linked service, I get the warning message. I also cleared my browser cache.

Share via

Azure Jira Connector - Upgraded Version and Dataset Warning.

1 answer

Your answer