Mobile Network - identity type mismatch

[ziyeqf]

for resources not support both SystemAssigned and UserAssigned identity, it only supports UserAssgined identity so please define it to only none or UserAssignedIdentity instead of ManagedServiceIdentity

e.g.: https://github.com/Azure/azure-rest-api-specs/blob/main/specification/mobilenetwork/resource-manager/Microsoft.MobileNetwork/stable/2022-11-01/simGroup.json#L325

[rafaeldnferreira]

@sathiyan-sivathas could you track fix for the next API? I'm assuming we are keeping our position to only support UserAssigned.

[sathiyan-sivathas]

@ziyeqf are you sure that that will work? I think there are at least a couple of problems:

• UserAssignedIdentity is a read-only object so there's no way for a user to specify a user-assigned MI using that type. At the very least we would need UserAssignedIdentities where the key in the dictionary is the user-assigned MI ID.
• Then how will will ARM treat this change? My understanding is that ARM enriches user request with additional headers based on the managed identity type set by the user. If we remove the type field, how does ARM know how to treat the request. I've found several documents that suggest that the identity property must follow a set format.

[ziyeqf]

Thanks @sathiyan-sivathas, I think I made a wrong link, sorry for that.

• just checked other service which only support UserAssigned identity, it seems they defines identity in their own Swagger. Here are some examples:

  • https://github.com/Azure/azure-rest-api-specs/blob/main/specification/cosmos-db/resource-manager/Microsoft.DocumentDB/stable/2022-05-15/managedCassandra.json#L771
  • https://github.com/Azure/azure-rest-api-specs/blob/main/specification/network/resource-manager/Microsoft.Network/stable/2022-07-01/firewallPolicy.json#L955

• I don't think it should be removed, but the current type allows users to set a SystemAssigned identity, which is not used by service. The supported types are None and UserAssigned. My request is also based on the assumption SystemAssigned type will not be used.

[sathiyan-sivathas]

@ziyeqf thanks. I agree if we made API changes similar to those ones you've linked to, then we would support user-assigned only. We will address this in our next API.