Simplified IDE connection parameters

Renamed two parameters for clarity and added the missing ILAP Data Exchange (IDE) UI base URL. Update your .bicepparam file as follows.

Renamed parameters (keep the same values, just change the names):

New parameter — add ideUiBaseUrl under the existing publicConfigurations param. It is used to build links to IEAs from the report schedule grid.

param publicConfigurations = {
  // Existing items .....
  ideUiBaseUrl: 'ILAP Data Exchange UI base URL' // e.g. 'https://ilaptest.collabor8.no' (test) or 'https://ilap.collabor8.no' (production)
}

Release 2.8.0.0

Use latest NODE version for web application

Updated NODE version for web application.

Go to the IlapAnalyticsUi.bicep file. In the resource ilapAnalyticsUi, set linuxFxVersion to NODE|24-lts.

Release 2.7.0.0

Operation completion notification for large schedule import

#7176

Send event hub message in chunk so that notification job doesn't fail for large data. Added BatchSize parameter under existing operationCompletionNotificationConfig object parameter. Use appropriate batch size based on your event hub tier.

param operationCompletionNotificationConfig = 
{
// Existing parameters .....
  BatchSize: 2000 
}

Release 2.6.0.0

Warn user if IA version is not compatible with IDE

Removed parameter enableApiVersionValidation. So remove that parameter from your .bicepparam file. Also remove the usages from the following files.

1. main.bicep
2. IlapAnalyticsApi.bicep

Release 2.4.0.0

Improvement of health check for Ilap Analytics

Card #6712

Change details

Added new item backgroundJobAppUrl under the existing publicConfigurations param.

  backgroundJobAppUrl: 'your-analytics-backgroundjobs-app-base-url'

// Example: 'https://app-ilapanalytics-backgroundjobs-dev.azurewebsites.net'. You can find the URL by clicking browse from azure app service.

Release 2.3.0.0

Sending Completion event log to event hub after completion of import/revert

Card: #5679

Change Details

Added new parameters in the bicep parameter files. More details can be found on the document Configuring Event Hub message sending.

// Operation completion notifications
// Controls whether applications publish a notification to event hub when a report schedule import/revert is completed.
// Notes:
// - If you plan to enable this, configure the "eventhubConfig" block below.
// - If you plan to notify via HTTP callback, set "CallbackHostUrl" to your API host base URL.
param operationCompletionNotificationConfig = {
  // Enable or disable operation completion notifications (true|false)
  IsEnabled: false
  // Notification type: 
  //      1 = Report Schedule Id Only, 
  //      2 = Report Schedule Id With Activity Ids, 
  //      3 = Report Schedule Ids With Activity Fqdns
  NotificationType: 2
  // Optional: Base URL for callback endpoints (used when notification type 3 is selected)
  CallbackHostUrl: publicConfigurations.analyticsApiUrl
}

// Event Hub configuration (optional, mandatory if operation completion notifications are enabled above)
// Provide only if you plan to publish operation completion notifications to an Azure Event Hub.
// - NamespaceUrl: The fully qualified namespace host (e.g., "your-namespace.servicebus.windows.net").
// - EventhubName: The Event Hub name to which events will be emitted.
// Note: Ensure that the application has the necessary permissions to send events to the specified Event Hub.
param eventhubConfig = {
  NamespaceUrl: 'your-namespace.servicebus.windows.net'
  EventhubName: 'name-of-your-eventhub'
}

Significance

If you want to configure event hub notification for each import revert/completion fill up the parameter file values. If you don't want to enable messaging, ignore them.

Resource Impact

New Resource creation: NO Resource config change: Yes Impacted resource: Background job, Analytics API