Dynamic Sessions consumption profile only accepts 1 vCPU/2 GiB despite documented 0.25–2 vCPU and 0.5–4 GiB range

Hi @SOFIA YANG

Thank you for reaching out to Microsoft Q&A.

When configuring Azure Dynamic Sessions using the Consumption workload profile, the portal and documentation indicate that a range of 0.25–2 vCPU and 0.5–4 GiB memory is supported. However, in practice, the deployment is accepted only when configured with 1 vCPU and 2 GiB memory, and any other value within the documented range is rejected. This behavior is due to a current platform-side limitation in the Dynamic Sessions runtime. The service internally provisions Dynamic Sessions on a fixed sandbox SKU, and the backend strictly enforces only 1 vCPU / 2 GiB regardless of what values are exposed in the portal UI or ARM schema. This is not related to regional capacity, subscription quota, or a misconfiguration, and there is currently no opt-in, feature flag, or support request path to enable other sizes. Microsoft has acknowledged that the documentation reflects future intended support, and is ahead of the actual implementation, which leads to this mismatch between documented behavior and real-world enforcement.

Refer below points to resolve this issue or this is the workaround

Use the only supported size (1 vCPU / 2 GiB) for Dynamic Sessions on Consumption profile

Dynamic Sessions on the Consumption workload profile currently support only a fixed size. You should explicitly configure your session pool or deployment to use 1 vCPU and 2 GiB memory, as any deviation will fail backend validation.

Do not rely on the documented range for Dynamic Sessions (Consumption)

Although documentation mentions a broader CPU and memory range, these values are not yet implemented in the service runtime. Automation via ARM, Bicep, CLI, or Terraform should avoid other values, as they will consistently be rejected.

If higher per-session resources are required, use an alternative workload profile

For workloads that need more CPU or memory per session, consider using Dedicated or other supported Azure Container Apps workload profiles, as Dynamic Sessions (Consumption) are designed for fixed-size, isolated execution rather than vertical scaling.