[BUG] Microsoft.RecoveryServices/vaults updating softDeleteState does not work

[Klaas-]

API Spec link

https://github.com/Azure/azure-rest-api-specs/blob/main/specification/recoveryservices/resource-manager/Microsoft.RecoveryServices/stable/2025-02-01/vaults.json

API Spec version

2025-02-01

Describe the bug

Hi,
it seems that updating the soft delete state does not work through the update process.

https://learn.microsoft.com/en-us/rest/api/recoveryservices/vaults/update?view=rest-recoveryservices-2025-02-01&tabs=HTTP&tryIt=true#code-try-0

PATCH https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{vaultName}?api-version=2025-02-01

If I want to update the softDeleteState it does not actually change anything, even though I get a Response Code: 200

I can also see in the body of the response nothing has changed.

Expected behavior

Security Settings actually change

Actual behavior

Nothing, and no error

Reproduction Steps

use curl or https://learn.microsoft.com/en-us/rest/api/recoveryservices/vaults/update?view=rest-recoveryservices-2025-02-01&tabs=HTTP&tryIt=true#code-try-0

Post to a vault that does not have soft delete enabled:

{
    "properties": {
        "securitySettings": {
            "softDeleteSettings": {
                "softDeleteState": "Enabled"
            }
        }
    }
}

I've noticed this is a bigger bug during testing, actually more affected than just the setting I want to change:

{
    "properties": {
        "ERRORsecuritySettings": {
            "softDeleteSettings": {
                "softDeleteState": "Enabled"
            }
        }
    }
}

will error as it should but with no helpful message though

{
    "properties": {
        "securitySettings": {
            "THIS_SETTING_DOES_NOT_EXIST": "test",
            "softDeleteSettings": {
                "softDeleteState": "Enabled"
            }
        }
    }
}

Will happily report 200 back, but won't notice that the setting does not actually exist, so my guess is everything below securitySettings is broken.

Environment

current rhel8 curl and edge

[Klaas-]

It also does not work on create, same for MultiUserAuthorization

[Klaas-]

Create also has an undocumented required field: properties.publicNetworkAccess -- I am guessing you guys forgot to set a secure default?