Unable to delete resources

Nathan Hofstee 105

When I try to delete a resource such as an API or subscription from my APIM instance, I receive error messages such as:

API Management

Could not delete operation Create resource. Please try again later. Correlation ID: 010ee6a0-1559-436f-8ba5-f9104704cd83 Timestamp: 2024-06-19T12:47:00.618Z

Failed to delete subscription

Invalid payload format. Contract should have 'properties' specified. Correlation ID: b11bc2d3-475b-4c7a-b982-e6c33288d3aa

I receive the error messages in multiple Azure regions, and in different Azure subscriptions.

Does someone have an idea what might be the issue?

issue1

issue2

Amol Shelar 421 Reputation points

2024-06-19T13:04:58.52+00:00
Hello @Nathan Hofstee

Use the Azure CLI to get detailed information about your APIM instance and resources.

az apim show --name <apim-name> --resource-group <resource-group-name>

Retry the delete operation using the CLI to see if it provides more detailed error messages.

az apim api delete --name <api-name> --resource-group <resource-group-name> --service-name <apim-name>

Additionally, Check the Activity Log under the Monitoring section for any failed operations. Look up the correlation IDs in the log to get more detailed error information.

Don't forget to mark my reply as Answer if it resolves your issue.

Regards,

Amol Shelar
Nathan Hofstee 105 Reputation points

2024-06-19T13:19:24.94+00:00

Thank you for the quick reply! Unfortunately the CLI delete operation returned the same errormessage as the Azure Portal:

(ValidationError) Invalid payload format. Contract should have 'properties' specified.

Code: ValidationError

Message: Invalid payload format. Contract should have 'properties' specified.
Kola Ojubanire 0 Reputation points

2024-06-19T16:44:56.4266667+00:00

A temp work around is to delete the Api tag on that APIM then try again, That has worked for us
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Michael G 5 Reputation points

2024-06-20T20:44:43.98+00:00

I am able to delete an APIM User using the RESTful call: https://video2.skills-academy.com/en-us/rest/api/apimanagement/user/delete?view=rest-apimanagement-2022-08-01&tabs=HTTP
Michael G 5 Reputation points

2024-06-21T22:26:19.27+00:00

This is working for me now. APIM stv2 / West US

11 answers

JananiRamesh-MSFT 23,251 Reputation points

2024-06-19T13:28:01.8533333+00:00

@Nathan Hofstee Thanks for reaching out. There is an ongoing issue at service end where DELETE requests with api-version 2023-03-01-preview to APIM are returning 400 Bad Request with error message 'Invalid payload format. Contract should have 'properties' specified'.

Sorry for the inconvenience caused by this issue. Our product team is actively investigating and we don't have any ETA/workaround for this. once we have any updates, I will update you here.

do let me know incase of further queries, I would be happy to assist you.
Please sign in to rate this answer.

8 people found this answer helpful.
Nathan Hofstee 105 Reputation points

2024-06-19T13:43:12.7166667+00:00

@JananiRamesh-MSFT I also deployed an APIM instance with version 2022-08-01 which also gives me the error messages.

Looking forward to any new updates. Thank you for informing me.

Linus Sundqvist 10 Reputation points

2024-06-19T14:19:22.22+00:00

We're also having this issue (Sweden Central region). It's wreaking complete havoc with our Terraform deploys. Since we're using Terraform I don't exactly know which API versions are used.

Kola Ojubanire 0 Reputation points

2024-06-19T16:10:30.11+00:00

We're having the same issue in the UK.. Wreaking havoc for us as it is for Linus

Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Cecils 5 Reputation points

2024-06-19T19:13:50.3933333+00:00

Howdy,

-same issue here-

Checking in to know if by chance the team has been able to resolve this matter.

Sergei Moukhnitski (Consultant) 5 Reputation points

2024-06-19T22:18:27.7233333+00:00

Please keep us updated. We had to cancel an important deployment today because of this issue. Terraform failed on deleting APIM resources, an attempt to delete manually gave us the same error.

Matt Bernard 10 Reputation points

2024-06-19T23:24:13.2366667+00:00

I'm having this issue with terraform.
westus2
api version 2022-08-01 @JananiRamesh-MSFT

mtrobaugh 5 Reputation points

2024-06-20T02:10:54.0933333+00:00

We are also seeing this when trying to delete revisions or operation via any method tried (powershell, portal, vscode). It is causing issues with our deployment pipelines.

Björn Ångbäck 0 Reputation points

2024-06-20T06:09:10.7933333+00:00

Chiming in, we have the same issue in sweden central and europe west. I don't think it's related to region though.

naman ajmera 0 Reputation points

2024-06-20T06:46:56.9433333+00:00

Remove-AzApiManagementOperation giving same issue

Zak W 10 Reputation points

2024-06-20T13:59:25.31+00:00

Is there an official issue reference we can follow for updates with this issue?

Dan P 5 Reputation points

2024-06-20T14:01:48.3566667+00:00

Hello,

We too are facing this issue.

Any ETA on when this will be resolved?

Thanks

Szczepankowski Maciej (CI/PLS5) 35 Reputation points

2024-06-20T14:05:05.4066667+00:00

Hello,
I have received information for MS support that the fix should be rolled out in all regions by 10 PM PST (7AM CEST)

Manuel Nunez 0 Reputation points

2024-06-21T13:23:03.3866667+00:00

Checking in to see if this is working for anyone right know we are blocked from even spinning up a new apim instance

Zak W 10 Reputation points

2024-06-21T13:30:12.51+00:00

The issue seems to have resolved itself for us now. We've had no failures and multiple successful pipeline runs since this morning (UK South region).

Sergei Moukhnitski (Consultant) 5 Reputation points

2024-06-21T13:31:19.4233333+00:00

Looks like things are back to normal. We are in the West US 2

Flavio Eiholzer 0 Reputation points

2024-06-21T13:38:05.4266667+00:00

Fine for me, Switzerland North region.

Sergei Moukhnitski (Consultant) 5 Reputation points

2024-06-21T13:38:12.47+00:00

The US WEST 2 seems to work

Sai Yadavelli 0 Reputation points

2024-06-21T15:44:12.3166667+00:00

Still Same for West US and West US 3. Any idea when they will be back here?

JananiRamesh-MSFT 23,251 Reputation points

2024-07-01T05:44:15.0433333+00:00

Apologies for the delay, I was on vacation and this issue has been mitigated on 6/21 5pm UTC.
Sign in to comment
Don van Meel | Twyzer 20 Reputation points

2024-06-19T17:50:16.8966667+00:00

We also had this problem in region West-europe. I have managed to delete an Api from Api Management.

Workaround

Go to Resources.azure.com

Select Read/write (Default Read Only).

Browse to your Resource Group.

Find the Microsoft.ApiManagment provider.

Select you api in the apis section.

On the right side select the tab Actions (Post,Delete)

Delete the api with the button Delete. Your api will be deleted. You can see the delete call to the api in the textbox near the button. It uses https://management.azure.com apiversion 01-01-2018 to delete the api.
Please sign in to rate this answer.

4 people found this answer helpful.
Steven Rasmussen 6 Reputation points

2024-06-19T22:55:10.17+00:00

Thanks for posting your workaround! Worked for me!

Matt Bernard 10 Reputation points

2024-06-19T23:30:33.13+00:00

from a new apim install with the echo-api @JananiRamesh-MSFT

{ "data": { "error": { "code": "MissingOrIncorrectVersionParameter", "message": "API version query parameter is not specified or was specified incorrectly. Supported versions: 2022-08-01,2022-09-01-preview,2023-03-01-preview,2023-05-01-preview,2023-09-01-preview Example query param format: api-version=SupportedVersion", "details": null } }, "status": 400 }

Versteegden, Aschwin 0 Reputation points

2024-06-20T09:34:55.1+00:00

Don you are the greatest

Bichel, Yauhen 0 Reputation points

2024-06-20T11:21:31.01+00:00

Thanks. It is working for me
Sign in to comment
Dirkx 1, Frank 5 Reputation points

2024-06-19T14:20:41.1966667+00:00

We experience the same issues when deleting an API, so keep us also informed.
Please sign in to rate this answer.

1 person found this answer helpful.

0 comments No comments
Sign in to comment
Herre Kuijpers 5 Reputation points

2024-06-20T08:23:51.36+00:00

For a client we're experiencing the same problem. Trying to remove an API from a Product results in: "Invalid payload format. Contract should have 'properties' specified."

This problem occurred only after moving to the new API Managment stv2.1 instance.

The problem is quite easy to reproduce: via the portal, in API Management create a new Product. Then assign the new product to the Echo API. Then go to the product details and try to remove the Echo api from the product. It will result in this error above.

Still not clear how to resolve this issue.
Please sign in to rate this answer.

1 person found this answer helpful.
Herre Kuijpers 5 Reputation points

2024-06-24T13:37:33.3566667+00:00

It looks like the issue has been resolved (West europe, Apim st2.1)
Sign in to comment
Alain Sarkisian 0 Reputation points

2024-06-19T16:24:20.2933333+00:00

Hello,

I am facing the same issue by creating a new APIM with Terraform, deployments of the APIM ends in failure:

Api: "echo-api"): unexpected status 400 with error: ValidationError: Invalid payload format. Contract should have 'properties' specified.
Please sign in to rate this answer.
Kola Ojubanire 0 Reputation points

2024-06-19T16:45:43.06+00:00

A temp workaround is to delete any API tags and try again

Corey D Sheerer 0 Reputation points

2024-06-20T15:55:15.2466667+00:00

We dont have any API tags and still get the error

John Wesley 0 Reputation points

2024-06-21T02:00:47.7233333+00:00

I'm having the same issue updating APIM global policy via terraform on STV1. I was able to update policy in the portal, but cannot do any deployments via terraform.
Sign in to comment

Share via

Unable to delete resources

11 answers

Workaround