Step-by-Step Guide: Configuring Concurrency Assignment in Windows 365 Frontline Dedicated Mode

In my last August blog post I have discussed about the Concurrency Assignment in Windows 365 Frontline Dedicated Mode, in this article I am showing you the step by step guide to configure the same.

1. Understand Licensing and Concurrency Rules

• Each Windows 365 Frontline license in dedicated mode allows the assignment of up to three Cloud PCs, but only one concurrent (active) connection per license.
• For example, 10 licenses let you provision up to 30 Cloud PCs, but only 10 can be active simultaneously.
• When a user signs out, the corresponding Cloud PC session is released, allowing another user to connect.

2. Prepare Prerequisites

• Ensure the organization has Windows 365 Frontline licenses and each user that requires a dedicated Cloud PC is licensed appropriately.
• Microsoft Intune licensing is also required for managing Cloud PC provisioning^[2].

3. Create and Assign a Provisioning Policy

• Log in to the Microsoft Intune Admin Center.
• Navigate to the Windows 365 section and select Provisioning Policies.
• Click Create policy and choose the Frontline license type.
• Within the Frontline option, select Dedicated mode.
• Choose network and image configuration appropriate for your organization.
• Assign this policy to the target group of users (e.g., shift workers, regional teams).

4. Monitor and Manage Concurrency Limits

• The Windows 365 service automatically enforces concurrency rules.
• When the maximum number of concurrent users is reached, new users cannot sign in until an active user logs out.
• A concurrency buffer allows temporary exceptions—up to four times per day and for up to one hour per instance—to prevent disruption during shift changes. Monitor usage to avoid exceeding limits too frequently, which may lead to a temporary or permanent buffer block.
• Use Frontline connection hourly reports and configure concurrency alerts in Intune to track usage and receive notifications if the concurrency buffer is activated.

5. Inform and Train Users

• Explain to employees that signing out of their Cloud PC is necessary to release sessions for colleagues.
• Cloud PCs automatically power off after a user signs out and can be powered back on when needed. The PC remains powered on for two hours after sign-out to enable rapid reconnection if required.

6. Ongoing Maintenance and Optimization

• Regularly review concurrency reports and alerts.
• Adjust policy assignments as shifts change or team sizes are updated.
• Use monitoring data to optimize license purchases and maximize ROI by aligning license count with actual concurrency needs.

By following these steps, administrators can ensure efficient Cloud PC usage, keeping resources scalable and costs predictable while supporting the flexible work requirements of modern organizations. That’s all about today, in my next post I will talk more about licensing.