Workspace Weekly: Feature Spotlight, Windows 365 Connector
March 5, 2026
Windows 365 Cloud PCs are becoming a core part of many EUC strategies. However, the user experience still depends on identity, policy, apps, and networking, and those are the exact places where small changes create big problems.
Login Enterprise 6.5 introduces the Windows 365 Connector, which enables automated testing of Windows 365 Cloud PCs by launching and interacting with a remote session through the Windows App.
With this, teams can turn Cloud PC access and app workflows into repeatable application, continuous, and load tests, so issues are caught before users report them.
For full setup and configuration details, see the Windows 365 Connector documentation.
Figure 1: Windows 365 Connector for Login Enterprise in action (video)
Login Enterprise Windows 365 Connector: Automated Cloud PC Testing Without Manual Clicks
When something breaks in Windows 365, the symptoms often show up first as user complaints: sign-in friction, a policy regression, a slow app launch, or a connection issue after an update.
The Windows 365 Connector makes Cloud PC access testable as part of an automated workflow. Instead of relying on manual spot checks, you can run repeatable tests that measure user experience over time and validate changes before they reach production.
This is especially valuable for teams that need to prove stability during migrations, renewals, or major change cycles, where stakeholders want evidence, not assumptions.
What the Windows 365 Connector Automates: MFA, Sign-In & Session Management
At a high level, the connector handles the parts that are usually the most painful to script and maintain:
- Launches the Windows App on a Launcher
- Signs in with the correct test account
- Handles MFA using verification codes when configured (TOTP)
- Searches for and selects the correct Cloud PC by name
- Connects to the Cloud PC session so your workload can run
- Signs out and resets the Windows App so the next run starts clean
You define the workload and the success criteria; the connector focuses on making Cloud PC access repeatable.
Use Cases: Continuous Cloud PD Testing, Image Validation & Windows 365 Migration
This feature is for teams who want to move from reactive firefighting to proactive validation:
- Continuous testing to catch issues overnight and before business hours.
- Application testing to validate image changes and security agent updates before rollout.
- Organizations where MFA and sign-in flows are non-negotiable and must be validated continuously.
- Teams scaling Windows 365 across departments, regions, or Cloud PC SKUs and need consistent, repeatable coverage.
Important Operational Note about Scaling
The Windows 365 Connector can only automate the Windows App connection to phase one session at a time on a given Launcher. If multiple Windows 365 sessions start on the same Launcher, their connection phases are queued and handled sequentially.
Once a session is fully connected, other sessions may proceed. Sessions running on different Launchers can connect in parallel.
Recommendation: Use dedicated Launchers for Windows 365 sessions.
Windows 365 connection phases can take longer than other connectors and mixing connector types on the same Launcher can cause non-Windows 365 sessions to time out while Windows 365 is holding the queue.
How to Set Up the Windows 365 Connector in Login Enterprise
Prerequisites
- A Launcher that includes Windows 365 Connector support
- The Windows App installed on the Launcher machine
- A warm Windows account on the Launcher machine (recommended)
The warm account requirement matters. First-time Windows App sign-in flows can include one-time dialogs that are not reliably repeatable. If you deploy a new Launcher machine or reinstall the Windows App, treat the account as new and warm it again by signing in once manually.
Prepare the Virtual User Account
In Login Enterprise:
- Go to Accounts
- In Account Settings, set Email to the user’s login (UPN or email). This is required for the Windows 365 Connector.
-
In Custom Field 1 (recommended), enter the Cloud PC device name
- Get this from the Windows 365 portal at windows365.microsoft.com
- Go to Cloud PCs and copy the value under Device Name
-
In Secured Custom Field 1 (recommended), enter the TOTP secret for MFA
- If you did not save the secret during authenticator setup, you will need to remove and reconfigure the authenticator method to generate a new secret.
Configure the Connector in a Test
- Go to Configuration > Manage tests
- Open an Application or Continuous test
-
In the Connector tab:
- Select Windows 365 (Preview)
- Set Cloud PC name field to the custom field containing the device name (default: Custom field 1)
- Set TOTP secret field to the secure field containing the MFA secret (default: Secure custom field 1)
-
Keep defaults unless troubleshooting:
- TOTP time step, digits, hash algorithm
- Script execution timeout
From here, run the test, and the connector will handle the Windows App sign-in, Cloud PC selection, and connection, so your workload can execute inside the Cloud PC session.
Figure 2: Windows 365 Connector configuration in Login Enterprise
Example: Validating Windows 365 Image Updates Across Departments
A platform team rolling out Windows 365 across multiple departments. You ship image updates, policy changes, and security agent releases regularly, and every change risks breaking the experience in a way users experience immediately.
With the Windows 365 Connector, you run repeatable tests that connect through the Windows App, validate access and workflows, and show performance trends over time.
By catching these issues early, you can reduce surprises and have evidence to share with stakeholders when it is time to approve changes or justify the rollout.
Upgrade to Login Enterprise 6.5: Download and Configuration
Upgrade your appliance and Launchers, then follow the documentation above to configure your accounts, set up the Cloud PC name and MFA secret fields, and run your first Application or Continuous Test against Windows 365.
To set up a new appliance or update an existing one, go to Downloads. If your Appliance already exists and is internet-connected, follow Updating Login Enterprise (there are additional update steps here). Don’t forget to take a snapshot first.
FAQ
Q1: Does the Login Enterprise Windows 365 Connector support MFA?
Yes. The connector handles MFA automatically using TOTP verification codes during sign-in, so tests can run unattended without manual authentication steps. You configure the TOTP secret in the virtual user account settings, and the connector generates the correct code at runtime.
Q2: Can Login Enterprise test multiple Windows 365 Cloud PCs at the same time?
Yes, with a dedicated Launcher per concurrent session. The connector processes one Cloud PC connection phase at a time per Launcher, but sessions running on different Launchers connect in parallel. For teams testing across departments or SKUs, deploying multiple Launchers enables full parallel coverage.
Q3: Is the Windows 365 Connector agentless?
Yes. Like all Login Enterprise connectors, the Windows 365 Connector requires no agent installed on the Cloud PC itself. It launches the Windows App on a Launcher machine, connects to the Cloud PC remotely, and runs your workload — the Cloud PC sees a normal user session, not a testing agent.
As always, thank you for your feedback! We use your insights to make Login Enterprise better for you.
Stay tuned for more Workspace Weeklies and join our Slack channel #workspace-weekly to share field stories, tips, and interesting finds.
Workspace Weekly
