The createOrUpdate operation of Key Vault Managed Hardware Security Module should fail when this resource is soft deleted

[neil-yechenwei]

After tested, I found the createOrUpdate operation of Key Vault Managed Hardware Security Module would always succeed even if this resource is soft deleted. Per my understanding, this operation should fail and throw error message like below this or others when this resource is soft deleted. So could you help take a look this issue? Thanks.

The example of the error:

{
    "error": {
        "code": "ConflictError",
        "message": "A KV MHSM with the same name already exists in deleted state. You need to either recover or purge existing KV MHSM."
    }
}

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @RandalliLama, @schaabs, @jlichwa.

Issue Details

---

After tested, I found the createOrUpdate operation of Key Vault Managed Hardware Security Module would always succeed even if this resource is soft deleted. Per my understanding, this operation should fail and throw error message like below this or others when this resource is soft deleted. So could you help take a look this issue? Thanks.

The example of the error:

{
    "error": {
        "code": "ConflictError",
        "message": "A KV MHSM with the same name already exists in deleted state. You need to either recover or purge existing KV MHSM."
    }
}

Author:	neil-yechenwei
Assignees:	-
Labels:	KeyVault, Service Attention, needs-triage
Milestone:	-