Update delete-operation-issues.md

[chenlonglab198]

Add one more TS guide about how to troubleshoot issues when failed to delete ACR rep with error "disallowed"

Pull request guidance

Thank you for submitting your contribution to our support content! Our team works closely with subject matter experts in CSS and PMs in the product group to review all content requests to ensure technical accuracy and the best customer experience. This process can sometimes take one or more days, so we greatly appreciate your patience.

We also need your help in order to process your request as soon as possible:

• We won't act on your pull request (PR) until you type "#sign-off" in a new comment in your pull request (PR) to indicate that your changes are complete.

• After you sign off in your PR, the article will be tech reviewed by the PM or SME if it has more than minor changes. Once the article is approved, it will undergo a final editing pass before being merged.

[prmerger-automator]

Invalid command: '#sign-off'. Only the assigned author of one or more file in this PR can sign off. @genlin

[learn-build-service-prod]

Learn Build status updates of commit 064b2bd:

✅ Validation status: passed

File	Status	Preview URL	Details
support/azure/azure-container-registry/delete-operation-issues.md	✅Succeeded

For more details, please refer to the build report.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[chenlonglab198]

@microsoft-github-policy-service agree company="Microsoft"

[prmerger-automator]

@chenlonglab198 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

[AndreiBarbu95]

@JarrettRenshaw @chenlonglab198 the changes are correct from the technical point of view. We have similar content publicly mentioned here: https://learn.microsoft.com/en-us/troubleshoot/azure/azure-container-registry/troubleshoot-push-error-operation-disallowed-timeout#error-1-the-operation-is-disallowed-on-this-registry --> but this article it focuses on push error, while the mentioned locks can also lead to delete errors, so I agree the content should be present also in the delete TSG (https://learn.microsoft.com/en-us/troubleshoot/azure/azure-container-registry/delete-operation-issues).

As mentioned in the push doc "This issue might be caused by the write operation being disabled for repositories or images. This state denies the delete and push operations. " so you can copy that part from there, or just grammarly adjust the suggestions from Jacky.