az eventhubs georecovery-alias create command remove the UserAssigned identity from primary namespace

[v-dbhimani]

Describe the bug

I am trying to create a georecovery alias using the az cli for eventhubs. for this I have created a Primary namespace and secondary namespace, for that I have added the UserAssigned identity to the both namespace and that's working fine.

After that I am using the az eventhubs georecovery-alias create command to create georecovery alias and that ultimately trigger the change to my primary namespace and it removes the UserAssigned identity from my namespace.

Also tried the same thing using the terraform and facing the same issue.

Related command

az eventhubs georecovery-alias create --alias <alias-name> --namespace-name <primary-namespace-name> --partner-namespace <secondary-namespace-id> --resource-group <resource-group-name>

Errors

Command is not failing with any error but it's behaviour is not expected.

Issue script & Debug output

az eventhubs georecovery-alias create --alias <alias-name> --namespace-name <primary-namespace-name> --partner-namespace <secondary-namespace-id> --resource-group <resource-group-name>

Expected behavior

When we run this command it should just create georecovery-alias using the primary namespace and secondary namespace. it should not trigger any of the change in any namespace.

Environment Summary

azure-cli 2.56.0

core 2.56.0
telemetry 1.1.0

Dependencies:
msal 1.24.0b2
azure-mgmt-resource 23.1.0b2

Python location '/usr/bin/python3.9'
Extensions directory '/root/.azure/cliextensions'

Python (Linux) 3.9.14 (main, Oct 12 2023, 19:48:32)
[GCC 11.2.0]

Legal docs and information: aka.ms/AzureCliLegal

Your CLI is up-to-date.

Additional context

No response

[yonzhan]

Thank you for opening this issue, we will look into it.

[microsoft-github-policy-service]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @Saglodha.

[schaudhari6254888]

Hey @v-dbhimani, I have tried the exact same thing. but none of my namespace affected.
can you please, give us more information on this.

[microsoft-github-policy-service]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @Saglodha.