Skip to content
LambogeniusDocs

Compose using XSLT for Azure Logic Apps

Licensing

Developer, trial and production licenses, the LAMBOGENIUS_LICENSE setting, and where no license is needed.

Service provider/serviceProviders/lamboXsltComposeOperation ComposeXslt, shown in the designer as Compose using XSLT.

Free for development, licensed for production

Compose using XSLT checks a Lambogenius license token offline, against public keys built into the connector: nothing is sent to Lambogenius. Get a token on Licensing at lambogenius.com.

LicenseForTerm
Developer (free)Development and testing, Azure included. The Logic App logs a reminder that it isn't a production license.90 days, renewable
Trial (free)Production use while you evaluate.30 days, once per organization
ProductionProduction. Contact sales.Annual

Where a token is needed

  • No token: Azure Functions Core Tools (func start) on a developer machine runs the action unlicensed and logs a reminder. The samples need no license.
  • Everywhere else (Azure Logic Apps, containers, Kubernetes, dotnet run) the action fails with LicenseRequired (HTTP 403) until the token is set.
  • After expiry the license keeps working for its grace period (14 days for trial and production, 7 for developer licenses), with warnings in the Logic App logs. Renew it and generate a new token.

Install the token

In the licensing workspace, open the license and select Generate connector license token. Put the token in the app setting LAMBOGENIUS_LICENSE, ideally as a Key Vault reference, or in a file named by LAMBOGENIUS_LICENSE_FILE. A changed setting takes effect within 5 minutes.

az logicapp config appsettings set -n <logic-app> -g <rg> \
  --settings "LAMBOGENIUS_LICENSE=@Microsoft.KeyVault(VaultName=<vault>;SecretName=LambogeniusLicense)"
One token per product family

A Compose using XSLT token unlocks only Compose using XSLT. HL7 connector, Edge Gateway, Liquid and CLI licenses are separate, and a token for another product fails with LicenseRequired, even under func start.