Security change on December 1, 2026: TLS 1.2 will become the minimum standard for 365 business Print Agent. Details and system requirements
365 business development
PowerShell Module

PowerShell module

The businessdev.ALbuild PowerShell module is the engine of ALbuild, organised into nine use-case modules. Both the Azure DevOps extension and the VS Code extension are thin shells over it, so everything the toolchain can do is available here as plain PowerShell.

  • Version: see the PowerShell Gallery
  • Requires: PowerShell 5.1 or 7+ (dual-target)
  • Packaging: one Gallery package, one version, composed of use-case nested modules.

Installation

PowerShellCode
# install once: one package, all areas Install-Module businessdev.ALbuild -Scope CurrentUser Import-Module businessdev.ALbuild # confirm Get-Command -Module businessdev.ALbuild

No BcContainerHelper

ALbuild does not require, install or call BcContainerHelper. The entire container stack is built into the module.


Module reference

ModuleTierWhat it covers
CoreFreeConfig, logging, licensing, version math, project config, build order, version stamping, readable errors
ContainersFreeArtifacts, Docker container lifecycle, users, test toolkit, config packages, Traefik, certificates
AppsFree (except AppSource validation)Compile, publish/sync/install/unpublish, sign, test, coverage, app version, 365 apps, XLIFF
FeedsFreeDependency resolver, dependency reconciliation, feed providers, NuGet packaging, feed-view promotion
RuntimePackagesLicensedThe runtime-package factory: plan by platform version, worker pool, checkpointing
MarketplaceLicensedAppSource / Partner Center ingestion
OnPremLicensedOn-prem publish/install/sync/upgrade, PTE, Dev
EnvironmentsLicensedDemo/dev environment provisioning
PipelineFreeLocal pipeline runner

Each module page is generated from the cmdlets' own comment-based help, so it always lists the complete set as shipped.

Licensed cmdlets call Assert-ALbuildLicensed on entry. See Licensing & tiers.


How the reference pages are organised

Each module page opens with a table of its cmdlets, then documents every cmdlet in full:

  • Synopsis & description: what it does and the important behaviour.
  • Syntax: the parameter signature.
  • Parameters: a table with type, whether it is required, allowed values, defaults and a description.
  • Output: what the cmdlet returns.
  • Examples: worked invocations.

Common workflows

Last modified on