This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(147.20000000000002, 5%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECP%3C/text%3E%3C/svg%3E)
Hello!
i've successfully created an azure site to site connection (vnet, subnets, local and virtual gateways are all good)
i've purchased a couple windows365 licenses then configured an azure network connection (join type = Azure AD Join) tied the connection to my azure resource group, vnet and subnet.
so i then fire up the cloudpc, i get a completely different ip address/subnet that is definitely not mine. im unable to ping or access my on-prem network.
i then fire up an azure vm in the same resource group. i can ping my on prem network with no prob. not sure what im missing or where the windows365 cloud pc is getting its routing or subnet information but any help would great. thanks in advance
A cloud-based identity and access management service for securing user authentication and resource access
fyi, what worked for me was using the Azure Hybrid Join method. once i configured windows365 for hybrid the "azure network connection" successfully provisioned and i was able to get visibility to our internal network using the azure site to site connection i created. thank you!
Hi @Christopher Paco , glad the above response helped in answering your query. Accept Answer and Upvote, so others visiting the forum with the same query might get help.
NOTE: To answer you as quickly as possible, please mention me in your reply.
Hi @
Thank you for asking this question on the **Microsoft Q&A Platform. **
The windows 365 Cloud pc has diverse kinds of networks.
]
Source: https://learn.microsoft.com/en-us/windows-365/enterprise/architecture
According to your explanation, you require an On-Premises network connection.
This is the documentation to create an Azure Network Connection
Azure network connections (ANC) let you provision Cloud PCs that are attached to a virtual network that you manage.
Hope this helps,
Carlos Solís Salazar
Accept Answer
and Upvote, if any of the above helped, this thread can help others in the community looking for remediation for similar issues.
NOTE: To answer you as quickly as possible, please mention me in your reply.
@Christopher Paco , you can Accept Answer and Upvote, if the above response helped answer your query, others visiting the forum with the same query might get help.
NOTE: To answer you as quickly as possible, please mention me in your reply.
