Referencing inside of HTTP to a parametrized User Assigned Managed Identity does not work

Kaloszer commented 10 months ago

Describe the Bug

Given an action within logic app like:


                "Revoke-UserSessions": {
                  "type": "Http",
                  "inputs": {
                    "authentication": {
                      "audience": "https://graph.microsoft.com",
                      "identity": "@parameters('uami02id')",
                      "type": "ManagedServiceIdentity"
                    },
                    "headers": {
                      "Content-Type": "application/json"
                    },
                    "method": "POST",
                    "uri": "https://graph.microsoft.com/v1.0/users/@{items('someOtherAction')?['AadUserId']}/revokeSignInSessions"
                  }
                },

And parameter within the template:

        "parameters": {
          "uami02id": {
            "value": "/subscription/..../someuaminame"
          }

Resolves to an invalid value like:

Plan Type

Consumption

Steps to Reproduce the Bug or Issue

Create logic app that attempts to reference an UAMI ID from parameters inside of a logic app HTTP request
Issue noted above happens

Workflow JSON

No response

Screenshots or Videos

No response

Additional context

Workaround to this issue to have a preflight step that replaces said reference in parameters to a hardcoded value. However if that were a secret, that would be an issue if this issue occurs therein.

If referenced directly by the ID string (/subscription/...../uaminame) - it works fine. Which is the underlying parameter

PS: The issue also seems to occur when trying to do a similar thing to api 'azuremonitoringlogs' - so when trying to assign 'identity' property with a parameter reference - it fails to find it. However when referenced directly by ID it finds it. (whereas that's the ID under the parameter value still, so the same string)

AB#25580185