How to add a Cloud PC to an existing vNet to map a VM drive?

Darren Persaud 40 Reputation points

Hello, I apologize if this is a very simple question, but I don't see any write-ups on if this is possible.

I would like to provision Cloud PCs so that when they are created, they are already within the vNet (and subnet). My end goal is for the Cloud PCs to be able to connect to the Virtual Machine that is in the same vNet/subnet. This way that VM will act as a sort of fileserver for those Cloud PCs to access.

I have created a VM in my Azure Portal, configured it and can successfully RDP into the VM.

I've tried creating an ANC, thinking that maybe if I add the ANC to the provisioning policy, it will do this on its own. Unfortunately, it fails the "First Party App Permissions" due to reader permissions on Azure Subscriptions saying "application' Windows 365' doesn't have sufficient permissions." The other checks pass w/o issue (Azure Tenant readiness, Azure virtual network readiness, Intune enrollment restrictions allow..)

Am I going about this the wrong way and overcomplicating things? Any insight or help on this would be greatly appreciated. Thank you!

Windows 365 Enterprise
0 comments No comments
{count} votes

Accepted answer
  1. Lu Dai-MSFT 28,366 Reputation points

    @Darren Persaud Thanks for posting in our Q&A.

    Please check if it meets the requirements.

    If this issue still exists, with Q&A limitation resource, it is suggested to create an online support ticket to get more help. Here is the support link:

    If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

0 additional answers

Sort by: Most helpful