v0.6.100: Managed runs start again after an Azure change
Update now. Since 4 November Azure refuses to start managed runs on earlier versions, and the run console shows "Container Apps job start failed with HTTP 400". This release gives your instance the permission Azure now asks for.
Update now
Since 4 November 2026, scheduled runs and Run now may have failed to start, and each run’s console shows Container Apps job start failed with HTTP 400. Azure Container Apps changed the permission it requires to start a job with per-run settings, and every Maester Cloud run starts that way. Instances on earlier versions don’t have the new permission, so Azure refuses every start.
Your results, history and tenant connections are untouched. The runs never started. Once you update, your next scheduled run starts as normal.
Fixes
- Managed runs start again. An update gives your instance’s app identity the Container Apps Jobs Contributor role, which includes the write permission Azure now requires. The role is scoped to your instance’s own runner job and nothing else in your subscription.- A refused start is retried once. Azure’s new permission check sometimes refuses a start it should allow. When that happens, Maester Cloud waits a few seconds and tries again.
- The run console says why a start was refused. A failed start now shows Azure’s error code, for example
HTTP 400 (JobStartOverrideAuthorizationFailed), and for this error the console tells you how to fix it. Azure’s full error message names your subscription and resource group, so it stays out of the console and out of telemetry. - The Managed Maester runs card works when other services are connected. On a tenant with Exchange Online, Teams or SharePoint Online connected, Save and Run now on the card could be refused with “Runs and schedules use the Microsoft Graph connection.” The card now always uses the Microsoft Graph connection. This fix shipped in v0.6.99 and is included here.
How to update
- Open setup.maester.cloud and sign in with the account you used for setup.
- Choose your instance and select Update to v0.6.100. The update applies in place, and your stored results and history are untouched.
- Open your portal and select Run now on a tenant to check that a run starts.
If you run setup from PowerShell, update the module first with Update-Module MaesterCloud, then run Start-MaesterCloudSetup.
If a run still won’t start after the update, email [email protected] with the first line of the run’s console.