Windows 365 Connector Management in Login Enterprise 6.7 | Workspace Weekly

July 15, 2026

Windows 365 connector management is central to keeping Windows 365 validation reliable, because that validation depends on the Windows App connection flow. When that flow changes, the connector automation behind the connection may need to change too.

This week’s Workspace Weekly looks at Windows 365 connector management in Login Enterprise 6.7, including how connector scripts can now be reviewed and managed from the Login Enterprise UI, and how teams can use the Public API when they want to automate the same workflow.

For the complete list of features, changes, improvements, and fixes in Login Enterprise 6.7, check out the release notes.

Why Windows 365 Connector Management Matters for Continuous Validation

Login Enterprise connects to Windows 365 Cloud PCs through the Windows App. This follows the same general connection path a user would take, rather than depending on an agent inside the Cloud PC.

That connection path matters, but it also means the Windows App matters. If the sign-in flow, launch behavior, or connection experience changes, the connector automation may need to change with it.

Imagine you are validating Windows 365 Cloud PCs before a monthly image update, security policy change, or application rollout. Your tests are working, but then the Windows App changes or your environment needs a slightly different connection sequence.

You need a clear way to understand which connector script is being used, review it, and update it when needed.

That is the value of centralized connector management. The script can be managed from one place instead of being treated like hidden plumbing.

Manage Windows 365 Connector Scripts in the Login Enterprise UI

In Login Enterprise 6.7, Windows 365 connector scripts can be managed from the Windows 365 connector settings page.

Administrators can:

• Review the available scripts
• Upload a custom script
• Download scripts
• Delete a custom script and return to the built-in behavior

This gives teams a direct way to manage connector behavior without starting in the Public API.

The default script is provided by Login Enterprise. If no custom script is configured, Login Enterprise uses the built-in default behavior.

If a custom script is uploaded, that custom script becomes the appliance-wide script used for Windows 365 connector tests. If the custom script is deleted, Login Enterprise returns to the built-in default behavior.

This supports a straightforward workflow:

• Use the default script when the built-in behavior fits the environment.
• Upload a custom script when the environment needs different behavior.
• Download a script when it needs to be reviewed, backed up, or compared.
• Remove the custom script when the appliance should return to default behavior.

For more information, refer to: Windows 365 Connector Script Management

Click to View Details

Figure 1: Managing Windows 365 connector scripts from Connector settings

See Windows 365 Connector Management in Action

The walkthrough below shows how to review the built-in connector scripts, upload and replace a custom script, download a copy for backup, and remove the custom script to return to the built-in behavior.

The UI provides a direct way to manage connector behavior. Teams that need the same workflow in automation can use the Public API to list, retrieve, and back up connector scripts.

When to Use the UI vs. the Public API for Connector Management

The UI gives administrators a direct way to review and manage Windows 365 connector scripts. It is the simplest path for day-to-day administration, troubleshooting, and one-off changes.

Login Enterprise 6.7 also expands the Public API with connector script retrieval operations. Teams can list the built-in scripts available for Windows App versions, download a specific built-in script, and retrieve or back up the currently configured custom script.

For example, a team may want to:

• Download the current script before replacing it
• Store the script with a change record
• Compare the current script with a newer version
• Upload a custom script as part of a release process
• Confirm which script versions are available across environments

Not every team needs API automation. The UI is enough for most manual script-management tasks. The API is useful when teams already manage Login Enterprise through automation or want script changes to follow the same process as other controlled updates.

For more information, refer to: Windows 365 | Using the Public API

Retrieve Windows 365 Connector Scripts with the Login Enterprise Public API

Login Enterprise 6.7 also adds Public API operations for retrieving Windows 365 connector scripts.

Teams can use these endpoints to list the built-in scripts available for different Windows App versions, download a specific built-in script, and retrieve the currently configured custom script for review or backup.

The example below uses Windows PowerShell 5.1 to list the built-in connector scripts and download the latest one as a .cs file.

$appliance = "https://your-login-enterprise-appliance"
$token     = "<system-access-token>"
$api       = "$appliance/publicApi/v8-preview"

$headers = @{
    Authorization = "Bearer $token"
}

# List built-in Windows App connector scripts
$scripts = Invoke-RestMethod `
    -Method Get `
    -Uri "$api/connector-scripts/default?target=windowsApp" `
    -Headers $headers

$scripts |
    Select-Object version, targetVersion |
    Format-Table -AutoSize

# Download the latest built-in script
$latest = $scripts |
    Sort-Object targetVersion -Descending |
    Select-Object -First 1

$version = [Uri]::EscapeDataString($latest.targetVersion)

$content = Invoke-RestMethod `
    -Method Get `
    -Uri "$api/connector-scripts/default/content?target=windowsApp&targetVersion=$version" `
    -Headers $headers

$content | Set-Content `
    ".\Windows365ConnectorScript-$($latest.targetVersion).cs" `
    -Encoding UTF8

Example: Listing and downloading built-in Windows 365 connector scripts with PowerShell

This example shows the basic retrieval workflow without replacing the product documentation. The downloaded script can be reviewed, compared, or used as the starting point for a custom connector script.

For a fuller PowerShell 5.1 example, including error handling, custom-script backup, and optional certificate-bypass logic for lab or troubleshooting use, see the Windows 365 Connector Compatibility repository and the Get-Windows365ConnectorScripts.ps1 example.

For more information about using the Login Enterprise Public API, including creating and using system access tokens, see: Using the Public API | System Access Tokens

Keep Windows 365 Validation Maintainable Over Time

Windows 365 testing is not a one-time setup task. Cloud PCs, policies, applications, identity flows, and the Windows App can all change over time.

Connector management in Login Enterprise 6.7 gives teams one place to understand and manage the automation used for that connection flow.

Administrators can use the built-in script behavior, introduce a custom script when their environment requires it, review or back up scripts before changes, and return to the default behavior when the custom script is no longer needed.

For customers using Windows 365 as part of a broader EUC strategy, the goal is not only to launch a Cloud PC once. The goal is to keep validating the experience users depend on as the environment changes.

For more information, refer to: Windows 365 Connector Script Management

Get Started with Windows 365 Connector Management in Login Enterprise 6.7

Upgrade your appliance and launchers, then use the documentation above to start applying these improvements to your Windows 365 validation workflows.

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. Don’t forget to take a snapshot first.

If you are not yet a Login Enterprise customer and are interested in becoming one, request a custom walkthrough with our team of EUC experts.

As always, we appreciate your feedback and 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.

To see all Workspace Weekly posts, visit the Workspace Weekly hub.