One article per released version of ILAP Analytics, newest first. It is written for whoever plans and performs upgrades.
What a release note contains
- The component versions in that release. The Analytics API, Background Jobs and Web UI are versioned separately and do not always move together, so the release number alone does not tell you which build of each you are running.
- The work completed in the release, by work item.
- Any change the release requires to your deployment — new or changed Bicep parameters, configuration, or infrastructure.
Before you upgrade
Read every note between your current version and the target, not only the newest one, and check the Bicep Changes section in each. A release that needs a new parameter says so there, and skipping an intermediate note is how a required parameter gets missed.
Ilap Analytics Bicep Change History, under New Customer, collects those parameter changes across releases in one place, which is the quicker check when you are several versions behind.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article