Incorrect Remote State Behavior for defaultManagementGroup in "Microsoft.Management/managementGroups/settings@2023-04-01"

[ms-henglu]

Description

Issue Summary

When using the Microsoft.Management/managementGroups/settings API (2023-04-01 version) to configure the defaultManagementGroup property, there is a discrepancy between what the API requires during resource creation and what it returns in the remote state.

Expected Behavior:

The API requires the full ID of the management group (e.g., /providers/Microsoft.Management/managementGroups/) to set the defaultManagementGroup property.
The API should return the same full ID in the remote state to maintain consistency.

Actual Behavior:

After applying the configuration, the API returns only the name of the management group (e.g., ), not the full ID. This causes tools like Terraform to detect changes during subsequent plan and apply actions, as the returned value doesn't match the expected input.

Steps to Reproduce

Use the following payload to configure the default management group settings:

{  
    "properties": {  
        "defaultManagementGroup": "/providers/Microsoft.Management/managementGroups/mg-sandbox",  
        "requireAuthorizationForGroupCreation": true  
    }  
}  

2. The API accepts the request and successfully creates the resource.

3. Fetch the remote state of the resource (e.g., via GET request or tools like Terraform). The defaultManagementGroup property in the response shows only the name of the management group (mg-sandbox), instead of the full ID.

4. This discrepancy causes tools like Terraform to repeatedly detect changes, leading to unnecessary updates.

Expected Behavior

The API should return the full ID (e.g., /providers/Microsoft.Management/managementGroups/mg-sandbox) for the defaultManagementGroup property in the response, matching what it required during the creation process.

Actual Behavior

The API returns only the name (e.g., mg-sandbox) instead of the full ID in the remote state, leading to state mismatches.