Updates to Windows 365 Flex, formerly Windows 365 Frontline
AI summary
Windows 365 Frontline rebranded to Flex: API terms and naming updated
Windows 365 Frontline → Flex: API-Werte und Bezeichnungen geändert
Rollout dates
- Standard release (GA):
Extracted from the announcement text; the Microsoft text is authoritative.
Impact
ChangeCockpit assessment (admin, user and compliance impact).
Microsoft announcement
[What and why:]
Earlier this year, Microsoft announced that Windows 365 Frontline is becoming Windows 365 Flex. As previously communicated in MC1401294, the first phase of this rebranding was completed on July 6, 2026, when customer-visible labels in the Microsoft Intune admin center and Windows 365 client experiences were updated from Windows 365 Frontline to Windows 365 Flex.
The next phase in early October 2026 will update Windows 365 SKU display names, in-product terminology, and Microsoft Graph API values from Frontline to Flex.
The Graph API value change may affect scripts, automation, reports, dashboards, and integrations that reference Frontline naming. Organizations should review and update dependent solutions as appropriate. This change does not affect Windows 365 functionality, Cloud PC capabilities, provisioning behavior, license assignments, or entitlements.
A later phase of the rebranding will update Device Model references and additional terminology. Details and timing for those changes will be communicated separately before rollout.
[Rollout schedule:]
- Windows 365 SKU display names, in-product terminology, and Microsoft Graph API values will roll out in early October 2026.
- Device Model references and additional terminology updates are planned for December 2026.
[Impact on your organization:]
Who is affected
- Windows 365 Flex administrators and users
What will happen
Breaking changes affecting automation and configurations (action required):
- API request and response values, display names, and other values related to Service Plan names that currently reference Frontline will be updated to reference Flex instead.
- This change may affect customers who have built custom automation, scripts, reports, dashboards, third-party integrations, alerts, or other configurations that depend on Windows 365 Frontline naming values. Existing logic that looks for, filters on, or processes the value Frontline may no longer behave as expected after the change.
- Branding changes only (no customer impact)
- Most of the changes in this update are terminology updates that align Windows 365 experiences with the new Windows 365 Flex branding. Existing licenses, Cloud PCs, provisioning policies, assignments, and entitlements continue to work as they do today.
- Administrators and users will begin seeing Flex instead of Frontline across Windows 365 experiences, including:
- Cloud PC pages and filters
- Provisioning policies
- License type display names
- Cloud PC size names
- Windows 365 web, Windows, Android, and iOS client experiences
- Report names, columns, and filters
- Alert names, email subjects, and email content
Examples of terminology changes include:
| Current terminology | Updated terminology |
|---|---|
| Windows 365 Frontline | Windows 365 Flex |
| Cloud PC Frontline | Cloud PC Flex |
| Frontline type | Flex mode |
| Frontline Shared | Flex shared |
| Frontline Dedicated | Flex dedicated |
| Frontline devices | Flex devices |
[Action required / Recommendations:]
Action required
Complete the following actions before the rollout reaches your environment:
Review Microsoft Graph API dependencies.
- Identify scripts, automation, reports, dashboards, and integrations that filter on or read Frontline.
- Update request filters and response-handling logic to support both Frontline and Flex during the gradual rollout.
- Test queries and automation against both values.
Update operational materials.
- Update internal documentation, runbooks, training, screenshots, and user guidance.
- Inform your help desk about the new Windows 365 Flex terminology.
- Watch for a separate communication about device model terminology updates.
[Compliance considerations:]
No compliance considerations are identified. Review as appropriate for your organization.
Additional information
Change history
- 2026-09-02 · Created · All