Important
Azure Lab Services will be retired on June 28, 2027. Click here for more information. We will not be taking any future requests or fixes. Note that this does NOT affect Azure DevTest Labs.
This is a public, community-contributed repository that contains:
-
Artifacts for Azure DevTest Labs: These artifacts can be deployed onto virtual machines in Azure DevTest Labs via the Azure Portal or through scripts.
-
Environments for Azure DevTest Labs: An environment is a collection of resources defined as ARM templates, which represent the Public Environment repository in Azure DevTest Labs and can be accessed via the Azure Portal or through scripts.
-
Samples for both Azure DevTest Labs and Classroom Labs: These samples vary from QuickStart Templates, to SDK samples and scripts that can be used to facilitate outside-the-box scenarios. They are used to demonstrate how Azure Lab Services can be integrated in automation scenarios.
-
Azure Pipelines Tasks for Azure DevTest Labs: This is the source code used to author Azure Pipelines tasks specifically geared to demonstrate use of Azure DevTest Labs in builds/releases. Refer to Azure DevTest Labs Tasks for more information and to install.
Az.DevTestLabs is a PowerShell module to simplify the management of Azure DevTest Labs. It provides composable functions to create, query, update and delete labs, VMs, Custom Images and Environments. The source can be located under /samples/DevTestLabs/Modules/Library/.
Az.LabServices is a PowerShell module to simplify the management of Azure Lab Services. It provides composable functions to create, query, update and delete lab accounts, labs, VMs and Images. The source can be located under /samples/ClassroomLabs/Modules/Library/.
If you are using the update (with lab plans) the Lab Services module is available in the PowerShell gallery. There is a dedicated Lab Services repository with samples for the updated modules and the improved service.
Contributions are encouraged and welcome. Please refer to the respective sections (e.g. Artifacts, Environments, Tasks) for more details on the respective process to follow.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.