Update Feed REST API 404 Error: "Packaging.Feed.AllowDisablingFeeds"

Question

While using feeds in Azure DevOps, an attempt to update a feed through the API (Update Feed API) results in a 404 error with the following response:

[{"$id":"1","innerException":null,"message":"Packaging.Feed.AllowDisablingFeeds","typeName":"Microsoft.TeamFoundation.Framework.Server.FeatureDisabledException, Microsoft.TeamFoundation.Framework.Server","typeKey":"**FeatureDisabledException**","errorCode":0,"eventId":3000}]

What can be done to resolve this error? Is there a specific setting to enable “AllowDisablingFeeds”?

API URL: https://feeds.dev.azure.com/<ORGNAME>/<PRJ_NAME>/_apis/packaging/feeds/f6d908a9-679b-49ec-8f23-cf9dc49c7ee1?api-version=5.1-preview.1

Payload: This issue arises when passing “isEnabled” as true:

{ "name" : "test2", "isEnabled" : "true" }

Answer 1

Hi Akash S

1. Check Feed Permissions by navigating to Azure DevOps -> Artifacts -> Feed Settings -> Permissions tab -> Ensure you are part of Feed Owner or Administrator roles.
2. If you do not want to disable or enable the feed, you can avoid using the isEnabled property in your payload:

      name": "test2" } 
   

   The feed can still be renamed or updated in other ways (like permissions, views) without touching this disabled feature.
3. Ensure you are using the latest API version (7.1-preview.1 or higher) instead of 5.1-preview.1. Try updating the API Version call to: https://feeds.dev.azure.com/<ORGNAME>/<PRJ_NAME>/_apis/packaging/feeds/<FEED_ID>?api-version=7.1-preview.1

Azure DevOps does not provide a direct setting labeled "AllowDisablingFeeds" in the UI or API documentation.

Additional References:

Feed permissions

Hope this helps!

Please Let me know if you have any queries.

Answer 2

1. I am the feed owner and I am using my PAT to execute the update feed api.
2. Using ?api-version=7.1-preview.1 also returns the same erroneous result.
3. Is there any other alternative to make this API work rather than removing the isEnabled feed from the payload?? Because this seems like a ADO error that needs to be resolved. Is there a way we can enable some configuration to allowing passing this field in the payload? It is strange that Azure DevOps is blocking requests when this field is set with error "Feature Disabled exception" but provide no option to enable the feature.

Answer 3

Hi Akash S

If the feed is already enabled, you might not need to explicitly set isEnabled: true. This bypasses the feature flag and will successfully rename or update other editable properties. I guess this works.

Instead of using the REST API, try using Azure DevOps CLI to update the feed:

az devops feed update --name "test2" --organization "https://dev.azure.com/<ORGNAME>" --project "<PRJ_NAME>" --is-enabled true

This sometimes bypasses API restrictions.

Hope this helps!

Please Let me know if you have any queries.

Answer 4

I am currently using REST API without using CLIs. Is there any other alternative to removing the isEnabled field from the payload? This seems like a recent problem. Even any workaround to resolve this issue by making some changes in the Azure Environment or etc would be greatly appreciated.

Answer 5

Hi Akash S

I can suggest you remove isEnabled: true, or else test with "isEnabled": false to see if the API allows disabling feeds but not enabling them.

Since you've already tested 7.1-preview.1, try: Stable API versions like api-version=6.0

Could you please try these workarounds and let me know if you have any queries