Every organization I work with has at least one system that will never get an API, such as an old ERP client or a file share full of contracts. Until now, agent automation stopped there. At Ignite 2026, Microsoft announced that agents running on Windows 365 for Agents Cloud PCs can now access on-premises applications by using agent identities. The capability is in preview.
In this post I explain how the feature works, what to prepare and the gotchas in the fine print. Where Microsoft has not documented something, I say so.
Quick context: where Windows 365 for Agents stands after Ignite
First, a short recap. Windows 365 for Agents gives AI agents managed Cloud PCs. An agent checks out a Cloud PC from a pool and does its task. Then it checks the Cloud PC back in, and the service resets it. According to the What’s new page, it became generally available in the week of June 1, 2026.
The Ignite announcements add several pieces:
- Copilot Credits billing for new customers through Agent 365.
- On-premises app access (preview), the topic of this post.
- Persistent Cloud PCs for agents in Frontier private preview.
- Copilot Studio computer use in the standard harness today, with a Microsoft Copilot harness preview from December.
- Microsoft Foundry MCP server setup in preview early next year.
Copilot Credits changes the budgeting conversation
With Copilot Credits, billing runs through a spending policy in the Microsoft 365 admin center. If no policy covers the agent user at checkout, the checkout fails, so a missing policy looks like a broken agent. Scope the policy to a security group of agent users. The design rules from my post on Copilot Credits spending policies apply here too.
Two more things to know. An All users policy with Auto-apply new services turned on already includes the service, so check what you are funding. And switching an existing pool from a billing plan to Copilot Credits can’t be undone.
How on-premises access for Windows 365 for Agents works
The Learn article sums it up: an agent needs both a network path to the resource and permission to use it.
The network path: Global Secure Access, not a VPN or ANC
The network path is Microsoft Entra Private Access. The Global Secure Access client on the Cloud PC routes traffic for your private applications through a Private Network connector in your datacenter.
Notice what is missing. The Learn page title says “with MHN and GSA”, which I read as Microsoft Hosted Network. The body does not spell it out. However, the documented provisioning policy for agents has no Azure network connection option and no hybrid join. Copilot Studio pools also run Entra joined on the Microsoft Hosted Network. So the documented path needs no vNet. The Entra guide does say any supported network connection works, but Private Access is the only one Microsoft documents for agents.
Identity: agent users and Microsoft Entra Kerberos
Authentication is the clever part. The agent signs in as an agent user. That is a user-type object in Microsoft Entra Agent ID, linked one to one with a parent agent identity. It has no password and no AD DS account.
Without an AD account, classic Kerberos does not work. Instead, the session gets a Primary Refresh Token and a Cloud TGT, and Windows uses the Cloud TGT to request a service ticket. Microsoft Entra Kerberos issues the ticket, including the on-premises group SIDs in the PAC. Your server decrypts it with its own key and evaluates its existing ACLs as usual.
As a result, the application does not change. It still trusts an AD group SID, which now has a cloud-only member.

What you need before you start
The prerequisites span three products, so collect them up front:
- Windows 365 for Agents: an Intune license, an Agent 365 license in the tenant and Copilot Credits billing (or a legacy billing plan).
- Global Secure Access: Microsoft Entra Private Access or Microsoft Entra Suite licensing, plus Entra ID P1 for connector groups.
- On-premises: an AD DS domain with working DNS, an AD-joined resource server, a unique SPN and a Microsoft Entra Cloud Sync provisioning agent.
- Tenant access to the Entra Kerberos preview for cloud-only identities.
- Conditional Access for agents requires Agent 365 together with at least Entra ID P1 or Microsoft 365 E3, or Microsoft 365 E7.
Setting up on-premises access, step by step
Like Microsoft’s guide, I use an SMB share: \\fs01.contoso.com\contracts.
Step 1: Build the agent pool and install the client
Create the provisioning policy under Intune admin center > Devices > Provision Cloud PCs. Open the Provisioning policies (Agents) tab and select Create policy (Agents). If the service is not enabled in your tenant, the button is greyed out and the tab shows Setup not complete.
In the Configuration section, link an Autopilot device preparation policy that installs the Global Secure Access client. Then keep Prevent connection to Cloud PC upon installation failure or time-out selected. That way, agents only get Cloud PCs where the client installed. Device grouping and preparation is itself in public preview.

Step 2: Configure Private Access
Next, in the Entra admin center, set up the network side:
- Create a connector group and install a Private Network connector on a server that can reach
fs01.contoso.com. - Under Global Secure Access > Applications > Quick access, add an application segment for the FQDN and TCP 445.
- Assign the agent users or their group to the Quick Access app.
- Enable the Private Access profile under Global Secure Access > Connect > Traffic forwarding.

Note that the portal recommends at least two active connectors per connector group.
Step 3: Prepare the group and the Kerberos trust
This is the on-premises work. First, configure the Microsoft Entra Kerberos trust for the domain. It is the same trust object I used in Setting up Windows Hello Cloud Kerberos Trust. Next, take the AD security group that grants access to the share and sync it with Cloud Sync. After that, transfer the group’s source of authority to Entra ID. The group keeps its on-premises SID, but you can now add agent users as members in the cloud.
Step 4: Register the resource and sync its key
Create an app registration that represents the resource. Its application ID URI must include the SPN, for example api://{client-id}/cifs/fs01.contoso.com. Add a KerberosSync:cifs/fs01.contoso.com tag and configure the hybrid_group_onpremises_sids group claim. Also set requestedAccessTokenVersion to 2 in the manifest, and assign the authorization group to the resource’s enterprise application when you use the ApplicationGroup scope.
Finally, create the Kerberos key synchronization job through Microsoft Graph beta. Cloud Sync then copies the service key of the account that owns the SPN to Entra ID, so Entra can issue tickets your server can decrypt. In my view, you should treat that as a trust decision: whoever controls the resource app and the sync job can influence access to that server. Microsoft’s own guidance is to restrict the sync permissions and protect the provisioning agent.
Step 5: Configure the Windows client and verify
On the Cloud PCs, enable CloudKerberosTicketRetrievalEnabled through Intune. Map the resource host to the KERBEROS.MICROSOFTONLINE.COM realm, and apply the KDC proxy configuration. Then verify with klist that the session gets an AES-256 ticket for cifs/fs01.contoso.com.
Gotchas I found in the documentation
Kerberos only for sign-in. The Entra guide is explicit: these steps don’t enable applications that require a password or a separate AD DS user account. Private Access can still carry the traffic to such an app, but the docs describe no way for the agent user to sign in to it.
Agent user sessions are their own flow. A human password sign-in is not a supported substitute for the agent user session. A cloud-only human account can help you validate the Kerberos plumbing, but it does not prove the agent path. Verify from a real agent user session before you call it done.
Conditional Access targeting is different. Policies scoped through the Users assignment don’t apply to agent user accounts. Instead, set What does this policy apply to? to Agents. Without Agent 365 licensing that option is greyed out, as in my lab tenant. Furthermore, scoping a policy by an agent user’s group membership is not supported today.

Nested groups don’t work for Quick Access. Users must be assigned directly or through a group assigned to the app.
One KerberosSync tag per service principal. If you add a second tag, key updates can silently stop. Therefore, use separate app registrations for CIFS and MSSQLSvc.
Not every account can sync its key. Accounts with RestrictedKrbHost SPNs may be out of scope, and critical system objects are excluded. Check before you pick the target server.
The spending policy is a dependency. If an agent user is not covered, checkout fails. In addition, if nobody in an always-available pool is covered when the monthly charge runs, the whole pool fails.
What is not documented yet
The docs publish no preview limits. The Ignite post doesn’t say whether persistent Cloud PCs get the same on-premises access. The docs also don’t say whether pools created in Copilot Studio can use this, since those pools are not configured in Intune. Finally, the overview page calls the Cloud PCs “domain-joined”, while every other page says Microsoft Entra joined. I treat the latter as correct.
Governance: treat agents like a new class of worker
A Private Access app only creates a network path; the resource still enforces its own permissions. Microsoft recommends four controls, and I agree:
- Limit network access to exact servers and ports, with a dedicated Private Access app for sensitive systems.
- Grant only the permissions needed, and review group memberships as tasks change.
- Apply Conditional Access where supported. Microsoft scopes this to apps configured for per-app access, so plan to move from Quick Access to a dedicated Private Access app. Device compliance for agent users is a separate, documented control.
- Review activity across systems: Entra sign-ins, Private Access logs and the app’s own audit log.
The last point matters most to me. An old app might only log “access granted to group X”, and then you lose the link to the specific agent.

Watch the agents’ user accounts card, because agent users are what sign in to the Cloud PCs.
My take
This is the first time Windows 365 for Agents touches the systems where most manual work actually happens. The design is sound: Private Access for the network and Entra Kerberos for identity, so your existing ACLs stay in charge. Nobody gets a service account with a password in a config file.
However, it is a preview with a long dependency chain. You need Agent 365, Copilot Credits, Global Secure Access, Cloud Sync, group source of authority and a Graph beta key sync. For that reason, my recommendation is to start with one read-only file share and one agent user. Then prove the full path, including logging, before you let an agent write anything into an ERP system. If your target app does not use Kerberos, wait for Microsoft to document more options.
References
- Windows 365 at Ignite 2026 (Windows IT Pro Blog)
- Onpremise access for agents with MHN and GSA
- Configure on-premises resource access for cloud-only identities with Microsoft Entra Kerberos (Preview)
- Create a provisioning policy for Windows 365 for Agents
- Set up billing for Windows 365 for Agents
- Learn about the agent’s user account in Microsoft Entra Agent ID
- Conditional Access for Agents in Microsoft Entra
- How to configure Quick Access for Global Secure Access
- Use Cloud PC pool for computer use runs (preview)