Windows 365 for Login Enterprise

Overview

Login Enterprise can automate connections to Windows 365 Cloud PCs using the Windows App. This enables you to run Login Enterprise tests directly inside your Cloud PC sessions and measure performance, availability, and login health. The connector provided on this page handles signing in, entering TOTP codes when required, selecting the correct Cloud PC, and launching the session so your test scenario can begin.

Download the Windows 365 Connector and all required files at the bottom of this page.

The connector is script-based and works with the Login Enterprise Custom Connector feature. It uses a PowerShell entry script, a C# workload script for driving the Windows App UI, a JSON steps file, and a helper script that handles password and MFA entry. This lets you run Login Enterprise tests against Windows 365 in a completely automated way.

Demonstration

Windows 365 Connector for Login Enterprise in action. In this demo, the Login Enterprise Launcher uses the Windows 365 Connector to open the Windows App, sign in to a Windows 365 Cloud PC, handle MFA automatically, and start a Login Enterprise test inside the Cloud PC session. You will see the test run to completion. The connector cleanly signs out and immediately begins the next connection cycle, proving that logins, MFA, and session launches can be checked on repeat without manual effort.

https://youtu.be/JOMzD7sd_OU?si=2HEbA5yJ9C2VnQOe

Learn how to set up and run automated continuous testing on Windows 365 Cloud PCs using Login Enterprise. This walkthrough covers launcher configuration, connector deployment, test creation, and production monitoring, from initial setup to viewing real-time results and reports.

https://youtu.be/SV-_pBJUK_I?si=AsnyXiZoFHzvLwZL

For a quick overview of the process, check out our interactive Storylane walkthrough that covers the Connector setup and the Continuous Testing scenario:

For the Storylane walkthrough that covers the Application Testing scenario, please review:

What the connector does

• Starts the Windows App on the Launcher.

• Cleans up any stale login windows from previous attempts.

• Detects whether the user is already signed in or needs to sign in.

• Types the Windows 365 username when prompted.

• Submits the password and, if you provide it, a TOTP authentication code.

• Waits for the Windows App to reach the Devices view.

• Selects the correct Cloud PC based on its display name.

• Connects to the Cloud PC so Login Enterprise can run its test scenario.

• Signs out at the end so the next test run starts cleanly.

This connector removes the need to build your own automation, and it works with any Login Enterprise test type that uses a Custom Connector.

Prerequisites

Before you can run a test against Windows 365, make sure the following components are set up.

Login Enterprise environment

• Login Enterprise must be installed and running.

• At least one Windows Launcher must be installed and attached to your environment.

• A test account must exist in the Login Enterprise Accounts page and belong to an Account Group. This account must have access to a Windows 365 Cloud PC.

Software on the Launcher host

• The Windows App must be installed. This is the Microsoft application used to access Cloud PCs.

• The Login Enterprise Standalone Engine must be installed.
  After installing Universal Web Connector, the engine will be here:

  CODE

  C:\Program Files\Login VSI\Universal Web Connector\engine\LoginEnterprise.Engine.Standalone.exe

• Place the four connector files from this page together in one folder on the Launcher:

  • Windows365Connector.ps1

  • Windows365Connector.cs

  • Windows365Connector_AuthenticationWindow.ps1

  • Windows365Connector.json

Login Enterprise test scenario setup

Create or edit a test scenario and configure:

• Select the Launcher that has the connector files on it.

• Use the Account or Account Group that contains the Windows 365 test user.

• Choose the Custom Connector option for the connector type.

• Enter the connector command line. Examples are shown later on this page.

• Use Login Enterprise command line tokens so you do not hardcode credentials. Examples include {username}, {password}, {domain}, {host}, and {securecustom1}. For the full list of supported tokens and usage patterns, see the connection command line.

• Store your Windows 365 TOTP secret (if required) in a secure custom field such as securecustom1 (requires Login Enterprise 6.3).

• Requiring Login Enterprise 6.3 or later, enable the process and window tracking feature for the Custom Connector settings in the Login Enterprise test scenario. Set the Process tracking > Process name field to be msrdc. This enables tracking of the Windows 365 Cloud PC window logging out and closing at the end of a test loop, allowing the test scenario to be available and start running its next loop iteration as soon as possible.

Once these items are configured, run the test scenario. The Launcher will open the Windows App, authenticate, connect to the Cloud PC, and begin your Login Enterprise workload. For help creating or editing test scenarios, see the configuration docs for Continuous Testing, Application Testing, and Load Testing. 

When the test ends, you can review the results in the normal results pages for Continuous Testing results, Application Testing results, or Load Testing results.

Files included with the connector

Windows365Connector.ps1

The entry point. It accepts the command line parameters, sets environment variables, and launches the Standalone Engine with the correct arguments.

Windows365Connector.cs
The workload script that drives the Windows App. It handles the sign-in flow, TOTP generation, JSON steps, device selection, connection, and cleanup.

Windows365Connector_AuthenticationWindow.ps1
A helper script that interacts with the Windows sign-in window. It types the password and TOTP code and handles the different authentication screens Windows may show.

Windows365Connector.json
A simple steps file that defines click and wait operations inside the Windows App after authentication. You can edit this file to customize or extend the click path.

Command line usage

Below are the most common ways to call the connector from a Custom Connector configuration.

Example with fixed values

A hardcoded command line string, such as the following, is helpful to verify or troubleshoot on your Launcher a one-time connection:

powershell -NoProfile -ExecutionPolicy RemoteSigned -WindowStyle Minimized -File "C:\LoginEnterprise\Windows365Connector\Windows365Connector.ps1" -EnginePath "C:\LoginEnterprise\ScriptEditor\engine\LoginEnterprise.Engine.Standalone.exe" -Email "user@contoso.com

Recommended example using Login Enterprise tokens

A tokenized command line string, such as the following, should be used in the Login Enterprise test scenario's Custom Connector configuration:

powershell -NoProfile -ExecutionPolicy RemoteSigned -WindowStyle Minimized -File "C:\LoginEnterprise\Windows365Connector\Windows365Connector.ps1" -EnginePath "C:\LoginEnterprise\ScriptEditor\engine\LoginEnterprise.Engine.Standalone.exe" -Email "{username}@{domain}.com" -Password "{password}" -Title "{host}" -TOTPSecret "{securecustom1}"

Default TOTP behavior

If you do not specify advanced TOTP settings, the connector uses:

• Time step: 30 seconds

• Digits: 6

• Algorithm: SHA1

These defaults match most identity providers.

Advanced TOTP example

powershell -NoProfile -ExecutionPolicy RemoteSigned -WindowStyle Minimized -File "C:\LoginEnterprise\Windows365Connector\Windows365Connector.ps1" -EnginePath "C:\LoginEnterprise\ScriptEditor\engine\LoginEnterprise.Engine.Standalone.exe" -Email "{username}@{domain}.com" -Password "{password}" -Title "{host}" -TOTPSecret "{securecustom1}" -TOTPTimeStep 60 -TOTPDigits 8 -TOTPAlgorithm SHA512

Parameters

How the connector works

The process from start to finish:

1. Start connector

2. Close any old Windows App windows

3. Launch the Windows App

4. Wait for the main window to appear

5. Check sign-in state

   1. If already signed in

      1. Open Account menu

      2. Sign out

      3. Select "Use another account"

   2. If not signed in

      1. Click "Sign in"

      2. If "Use another account" appears

         1. Click it

      3. If the login window appears

         1. Type the email address

6. If an email field appears

   1. Type your email and continue

7. Run the authentication helper: locate the Windows sign-in window

   1. Find the password field and type the password

   2. Press Enter to submit the password

   3. MFA handling

      1. If no MFA is required, continue to the next step

      2. If MFA is required, detect which MFA screen is shown

         1. If a hyperlink is shown (for example: “Can’t use my Microsoft Authenticator”)

            1. Click the hyperlink

            2. Then click the “Use a verification code” option

      3. If a button is shown (for example: “Use a verification code”), click the button

      4. If a code entry field appears immediately, use it directly

   4. Once the verification code screen is active

      1. Wait for the code field to appear

      2. Type the TOTP code

      3. Submit it

8. Wait for the Devices view

9. Run the steps defined in the JSON file

   1. Open Devices

   2. Use Search

10. Type the Cloud PC name

11. Click Connect

12. After the session ends

    1. Open Account

    2. Sign out

    3. Confirm "Use another account" is visible

13. Stop connector

This sequence repeats every time the scenario runs.

Tested environment

The connector has been tested with:

• Windows App version 2.0.706.0 | Client version 1.2.6515.0

• Windows 11 Pro x64 25H2

Other versions may work, but have not been validated.

Download the connector

Download the connector files below and place them together on the Launcher host. After downloading, configure the Custom Connector in Login Enterprise and begin testing your Windows 365 Cloud PC sessions.

Windows365Connector.ps1

Windows365Connector.json

Windows365Connector.cs

Windows365Connector_AuthenticationWindow.ps1