User-Assigned Managed Identity are not displayed properly in HTTP actions when referenced through Parameters

WenovateAA commented 1 year ago

Describe the Bug with repro steps

Link existing user-assigned managed identity (UAMI) to Logic Apps (Standard or Consumption).
Add resource id of the UAMI to parameters (UAMI-Id)
Create HTTP action. Add Authentication property for the HTTP action. Choose Managed identity from the drop-down menu
Click on Switch to code view mode button and paste the code:

{

"audience": "https://management.azure.com",

"identity": "@{parameters('UAMI-Id')}",

"type": "ManagedServiceIdentity"

}

This HTTP action will work as intended, however Designer displays The entered identity is not associated with this Logic App error

What type of Logic App Is this happening in?

Consumption (Portal)

Are you using Preview Designer or GA Designer

Preview

Did you refer to the TSG before filing this issue? https://aka.ms/lauxtsg

Yes

Workflow JSON

{
  "type": "Http",
  "inputs": {
    "uri": "https://management.azure.com/...",
    "method": "PUT",
    "body": {},
    "authentication": {
      "audience": "https://management.azure.com",
      "identity": "@{parameters('UAMI-Id')}",
      "type": "ManagedServiceIdentity"
    }
  }
}

Screenshots or Videos

Preview Designer

GA Designer

Browser

MS Edge (Chrome)

Additional context

This issue is observed in both versions of Designer and for both Logic Apps tiers.

Why it is important to store UAMI resource id in parameters and not in the code? There is a need to have the same code in all environments (tenants), for which UAMI is different. Its resource id therefore should not be part of workflow's code but instead stored in parameters (Consumption) or Application settings and referenced in parameters (for LA Standard)

AB#24439960

mohit-jagtiani commented 1 year ago

I have same issue. And also it is not possible to add parameter via designer but via code edit. Lastly why should system assigned identity must be enabled for this logic app. My company decided to only use user assigned for more control and since that works, either of 2 should be enabled and not System assigned.