Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Answered

Development on cloud hosted environment

(0) ShareShare
ReportReport
Posted on by 66

Hi,

I have some questions regarding development on a cloud-hosted environment...

The cloud-hosted development VM created with version :

Application release  = Microsoft Dynamics 365 for Finance and Operations (10.0.25)
Platform release = Update49 (7.0.6316.36)

The cloud hosted environments are requested by someone in the customer organisation, so technically they are the Administrator of the environment.
Question 1
Microsoft originally started this D365 Finance and Operations implementation project.
Then my company joined the project, and now I have been asked development a change request for this project.
I'm supposed to take over the cloud hosted VM that was originally used by one of the Microsoft developers.

However I was warned that this could be a problem, and that it may be best if the VM was deleted and recreated in LCS.
I didn't quite understand WHY the problems could occur however...

I suppose it has to do with any existing workspaces and risk of polluting MS code checked into DevOps ?
Can anyone explain the risks involved when taking over a DevBox from another developer ? 
SHOULD the VM be deleted and recreated in LCS ?


Question 2
When a cloud hosted environment is created in LCS, there are 2 users you can use to connect via RDP:
5001.pastedimage1660128486870v1.png
Should you use the "Admin" account to connect via RDP for development ?
Or can you use the "User" account for development without the Admin rights ?

Microsoft documentation states that, as a developer, you should use the "User" account..
However they also go on saying that a developer should have Admin rights on the machine, so I'm confused...
I have only worked on local VM's up untill now, so I'm not sure how to proceed to use and configure the environment properly (connect/sync to DevOps, restore DB backup with customer test data, etc..)

Thanks in advance for any information !
  • gverstrepen Profile Picture
    66 on at
    RE: Development on cloud hosted environment

    Hi André,

    Thanks for your input...

    No, we had just a quick (and brief) "hand-over" call 2 days before that person went on vacation, so a lot of the details went missing

    (or I didn't think to ask because I assumed they would be similar to working on local VM, which doesn't seem to be the case)

    All customizations should be in DevOps already, so I don't think there's an issue of losing source code.

  • Suggested answer
    gverstrepen Profile Picture
    66 on at
    RE: Development on cloud hosted environment

    Thanks for your quick reply, Komi

    In my case I believe the the DevOps project is created using the customer credentials, as they seem to be managing all access rights to LCS/DevOps/AD themselves. I'll have to check once my access rights come through

  • Verified answer
    André Arnaud de Calavon Profile Picture
    294,261 Super User 2025 Season 1 on at
    RE: Development on cloud hosted environment

    Hi gverstrepen,

    In addition to the reply from Komi some thoughts:

    Did the person who warned you also informed you about the details of the problem? The only topic I can think of would be separating the users/workspaces for check-in the code in DevOps like you mentioned yourself. At least, don't delete the old VM until you are sure that the Microsoft code was checked-in in DevOps. You would need to have a backup of the source code.

    A user doesn't need admin rights on the VM, but Visual Studio need to be opened with the option 'Rus as administrator'. Usually, I use the Admin user myself without any particular reason.

  • Suggested answer
    Komi Siabi Profile Picture
    12,837 Most Valuable Professional on at
    RE: Development on cloud hosted environment

    Question 1

    To link D365FO DEV to VSTS, you need to have a project created on dev.azure.com. There are two options:

    a. An organization and a project is created using the client credentials: This allow the client to have full control over source control. In this case, even if a new partner comes in. They are just granted access to Source control.

    b. An organization and a project is created using the partner credentials: For this, the next client might not have access to source control if the previous partner left under bad conditions. Hence, they would have to create a new deveOps project and link to Visual studio.

    For me, redeploying the VM should not be the primary concern, but having access to the customization done by Microsoft so far.

    Question 2

    You obviously have two accounts provisioned. I do make use of the admin account by default to connect to the RDP.

    Open Visual studio as admin is required while carrying out some development action.

    I hope this helps. 

    Komi, 

    Regards.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

🌸 Community Spring Festival 2025 Challenge 🌸

WIN Power Platform Community Conference 2025 tickets!

Jonas ”Jones” Melgaard – Community Spotlight

We are honored to recognize Jonas "Jones" Melgaard as our April 2025…

Kudos to the March Top 10 Community Stars!

Thanks for all your good work in the Community!

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 294,261 Super User 2025 Season 1

#2
Martin Dráb Profile Picture

Martin Dráb 233,013 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,158 Moderator

Leaderboard

Product updates

Dynamics 365 release plans