Get-AzIntegrationAccountMap only supports XSLT format and does not provide a way to work with other formats. Maps in Liquid format, for example, can be added via the portal or the REST API but are inaccessible via Azure PowerShell.
When listing maps, the list is filtered on the following line to show only XSLT:
The -MapName parameter can be used to retrieve a specific map, but retrieving a Liquid format map results in an "Unable to deserialize the response" error.
I would understand the limitation if the content of the map was included in the response and needed to be deserialized into a PowerShell object, but the response actually just includes a contentLink object with a URI inside to get the map content. The only significant difference in the API response compared to an XSLT map is the mapType property.
Script/Steps for Reproduction
First, create an integration account in the Azure Portal and add a map in Liquid format. (This is unsupported in Azure PowerShell). Optionally, add another map in XSLT format to illustrate that the list of maps is filtered to XSLT.
Run Get-AzIntegrationAccountMap without specifying -MapName. Only XSLT maps are returned.
Run Get-AzIntegrationAccountMap with a -MapName specified to specifically request the Liquid map. The cmdlet will return "Unable to deserialize the response."
Description
Get-AzIntegrationAccountMap
only supports XSLT format and does not provide a way to work with other formats. Maps in Liquid format, for example, can be added via the portal or the REST API but are inaccessible via Azure PowerShell.When listing maps, the list is filtered on the following line to show only XSLT:
https://github.com/Azure/azure-powershell/blob/b61106c491fc624776f3be3f933879c8cf7ffb36/src/ResourceManager/LogicApp/Commands.LogicApp/Utilities/IntegrationAccountMapOperations.cs#L105
The
-MapName
parameter can be used to retrieve a specific map, but retrieving a Liquid format map results in an "Unable to deserialize the response" error.I would understand the limitation if the content of the map was included in the response and needed to be deserialized into a PowerShell object, but the response actually just includes a
contentLink
object with a URI inside to get the map content. The only significant difference in the API response compared to an XSLT map is themapType
property.Script/Steps for Reproduction
First, create an integration account in the Azure Portal and add a map in Liquid format. (This is unsupported in Azure PowerShell). Optionally, add another map in XSLT format to illustrate that the list of maps is filtered to XSLT.
Run
Get-AzIntegrationAccountMap
without specifying-MapName
. Only XSLT maps are returned.Run
Get-AzIntegrationAccountMap
with a-MapName
specified to specifically request the Liquid map. The cmdlet will return "Unable to deserialize the response."Module Version
Environment Data
Debug Output