Lab profiles now have an option on the advanced tab to allow lab users to disconnect from the lab and keep the lab running. The disconnected lab will still count towards the user’s active lab instances.
It is now possible to use an ADO repository to sync instructions to a lab profile. Syncing instructions with an ADO repository allows lab authors to utilize version control in ADO, multi-author support, as well as centralized management of lab instructions in ADO.
IDL legacy is no longer available to use in new labs. The option to use IDL (legacy) for lab instructions has been removed from LOD. IDL legacy labs that have not yet been converted to IDLx will be automatically upgraded on October 1.
The next page button in lab instructions now displays the first header on the next page for all header sizes (H1-H6), instead of only using H1 headers on the next page button.
- Fixed an issue that prevented custom CSS from displaying correctly on some event pages.
- Fixed a bug that prevented exam settings from being inherited in child lab profiles.
- When editing cloud templates, validation logic has been updated to ensure that changes won’t break any labs that use the template. Safe changes are allowed, changes that would break labs are blocked, and changes that might impact labs require confirmation.
- VMware VMs can now be built using hardware version 14.
- Fixed a […]
- Fixed a bug that caused an error to occur during lab launch, when the option in the subscription to override subscription pool authentication settings is disabled and the lab uses the subscription pool authentication settings instead.
Fixed a bug that could cause manually evaluated activities to be scored more than once. This issue did not impact automated ABA/PBT.
Fixed a bug that caused an application error when editing lab instructions of an AWS lab profile that does not have an AWS region configured.
- Add any number of external registry accounts to […]
House your lab instructions in Azure Dev Ops instead of Lab on Demand. Take advantage of your organization’s ADO access policies, change control, and project management while authoring lab content.
Containers can now persist changes, similar to how differencing disks work for VMs. Changes can be persisted to a new container image, new lab and container image or the current container images in the lab can be updated. This allows lab authors to configure the container image and save it, so that the configuration will be present on future lab launches that use that container image.