Hosted Agent ZIP deployment fails because adduser is missing for fuse-zip

Your ZIP layout and dotnet_10 runtime match the documented source-code deployment model, while the logs fail during platform package configuration before the application entry point runs. That makes a managed runtime bootstrap failure more likely than a readiness-endpoint problem, but public documentation does not confirm a known West Europe regression. Download the deployed ZIP, compare its SHA-256 with the uploaded artifact, and verify the active version, runtime, dependency mode, and entry point. Invoke a new session and stream its container logs using the returned session ID. Capture the session ID, region header, response identifier, UTC time, and complete package error. There is no supported customer step for installing a missing operating-system package inside the managed source-code image. For an immediate workaround, use the container deployment path, which gives you control of the runtime image. Otherwise open Azure support with the correlation data and request confirmation of a regional platform fault.