Azure Data Factory resources and linked service disappeared. Error code 401 Failed to load resource in console.

Hi @Dylan Johns

Thank you for providing the additional information.

Based on your findings, the Azure CLI returning an empty list indicates that the pipelines are no longer present in the live Data Factory. Since Git integration was not configured, there is unfortunately no source control repository available to recover any unpublished changes. Additionally, the absence of delete or deployment operations in the Azure Activity Log suggests there is no evidence of an intentional deletion.

The ResourceNotFound response for the managed virtual network is expected if your Data Factory was not configured to use a Managed Virtual Network, so it is unlikely to be related to the missing pipelines.

Given these findings, this issue would require further investigation by the Azure Data Factory product team. I recommend opening an Azure Support request and including your Data Factory name, Azure region, the approximate UTC timestamps when the pipelines were last visible and when they disappeared, the Azure CLI output showing that no pipelines are returned, confirmation that Git integration was not enabled, and the Activity Log results showing no delete or deployment operations. This information will help the engineering team review the backend logs and determine whether a service-side issue occurred.

If the pipelines were never published and there is no Git repository or ARM template backup, there is unfortunately no customer-side recovery mechanism available. However, Azure Support can verify whether this behavior was caused by an unexpected backend issue.

For more information, please refer to:

• https://learn.microsoft.com/azure/data-factory/source-control
• https://learn.microsoft.com/azure/data-factory/data-factory-troubleshoot-guide

I hope this helps. Please let us know if you open a support request or if you have any further updates.

Hello Dylan Johns,

Welcome to the Microsoft Q&A and thank you for posting your questions here.

I understand that your Azure Data Factory resources and linked service disappeared. Error code 401 Failed to load resource in console.

What you need to do first is to verify the real state of the Data Factory service, not the ADF Studio left pane. Run each after one another:

az login
az account set --subscription "<subscription-id>"
az datafactory pipeline list </span>
  --resource-group "<resource-group-name>" </span>
  --factory-name "<factory-name>" </span>
  --output table
az datafactory linked-service list </span>
  --resource-group "<resource-group-name>" </span>
  --factory-name "<factory-name>" </span>
  --output table
az datafactory dataset list </span>
  --resource-group "<resource-group-name>" </span>
  --factory-name "<factory-name>" </span>
  --output table
az datafactory trigger list </span>
  --resource-group "<resource-group-name>" </span>
  --factory-name "<factory-name>" </span>
  --output table

If the pipelines are returned by CLI, the resources still exist and the issue is ADF Studio loading, browser/session, RBAC, or client-side blocking. Use Microsoft Edge or Chrome, disable ad blockers/privacy extensions for adf.azure.com, allow required cookies, clear ADF site data, sign out/in again, and confirm the correct tenant/subscription. Microsoft documents that ADF Studio depends on browser cookies and can fail when cookies, incognito mode, or blockers interfere. - https://learn.microsoft.com/en-us/azure/data-factory/data-factory-ux-troubleshoot-guide

If the pipelines are not returned by CLI, check whether the factory is connected to Git. Switch to the correct branch and inspect the pipeline, linkedService, dataset, and trigger folders. If the artifacts exist there, merge them into the collaboration branch and publish. Git integration is the supported way to keep partial saves, track changes, revert errors, and protect ADF authoring work. - https://learn.microsoft.com/en-us/azure/data-factory/source-control

If the artifacts are not in live service and not in Git, check Azure Activity Log for delete/write/deployment events during the disappearance window. Filter for Data Factory pipeline, linked service, dataset, trigger, and ARM deployment operations. Azure Activity Log records management operations such as create, update, delete, and deployment failures and keeps them for 90 days by default. - https://learn.microsoft.com/en-us/azure/azure-monitor/platform/activity-log

If Activity Log shows a delete or overwriting deployment, restore from Git, ARM template, CI/CD artifact, or another environment, then restrict direct edits and use CI/CD going forward. Azure Data Factory CI/CD uses ARM templates to store and promote ADF entities such as pipelines, datasets, and data flows between environments. - https://learn.microsoft.com/en-us/azure/data-factory/continuous-integration-delivery

If there is no live copy, no Git copy, no ARM export, and no deployment artifact, then the missing unpublished pipelines cannot be reliably restored by ADF. Rebuild them and immediately enable Git integration before continuing. Without Git, ADF does not provide a source-control repository for draft JSON entities, and publishing is the durable save path for service-side resources. - https://learn.microsoft.com/en-us/azure/data-factory/source-control

I hope this is helpful. Please! Do not hesitate to let me know if you have any other questions, steps or clarifications.

Please do not close the thread by upvoting and accepting the answer if any part of it is helpful.

hi & thx for sharing urs issue here at Q&A portal,

From the screenshot, the net::ERR_BLOCKED_BY_CLIENT errors are almost certainly a red herring. Those requests are to eu-mobile.events.data.microsoft.com (Microsoft telemetry), and they're commonly blocked by ad blockers, Brave Shields, uBlock Origin, Pi-hole, or enterprise filtering. They don't normally cause Azure Data Factory resources to disappear.

The more important symptom is that all pipelines, datasets, and most linked services disappeared. That points to one of these You're connected to a different Data Factory (subscription/resource/branch).

Git integration is enabled and you've switched branches or are viewing a branch without your changes. The changes were never published or committed and were lost after the browser session. A backend service issue or authorization problem prevented ADF Studio from loading the authoring metadata. I'd check

Whether Git mode is enabled and which branch you're on.

Whether Manage > Git configuration still points to the expected repository.

Whether the missing pipelines exist under the Develop branch in your Git repo.

Azure Activity Log to confirm nobody deleted the resources.

Network tab (not Console) to identify any ADF REST calls returning 401/403/500, especially requests to management.azure.com or *.datafactory.azure.net.

If the only failures are telemetry requests, they aren't the cause. If authoring API calls are returning 401, capture the failing request URL, Request ID, and timestamp those will help Microsoft determine whether this is an authentication or service-side issue.

If the factory is in Git mode, it's also worth checking whether you're simply on the wrong branch before assuming the resources were lost.

Based on ur description, I'd investigate Git/source control or a backend authoring issue before focusing on the ERR_BLOCKED_BY_CLIENT messages. Those are very common and, by themselves, shouldn't make pipelines disappear.

rgds,

Alex

&

If my answer was helpful pls mark it and additional thx if u follow me at Q&A portal

and at my blog https://ctrlaltdel.blog/