Finance | Project Operations, Human Resources, ...

Creating build server and updating existing pipe line configuration in D365FO

(3) Share

Report

Posted on by krishna.rao@dax

3,008

Requirement:

1) Create new build server (cloud hosted environment) for pipe line deployment purpose.

2) Client has specific requirement, they want to use server based pipe lines for deployment. They don't want server less pipe line approach

3) After creating build servers. We need to create build agents. these build agents need to be updated/pointed in existing pipe line configurations in the Azure devops .

Can someone please guide here.. documentation, blogs for this activity

Many thanks in advance,

Categories:

Dynamics 365 Finance

I have the same question (0)

All responses (6)

Answers (0)

Suggested answer

udaY-ch 5,173 on at

Like (1)

Report
Copy link

Link copied!

Hi

Please check out these blogs,

https://denistrunin.com/d365fo-buildrelease/

https://blog.ateliware.com/step-by-step-to-deploy-d365fo-with-azure-devops/

https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/dev-tools/hosted-build-automation

Thanks

Uday

If you found this answer helpful, kindly mark it as verified so it can assist others facing similar issues.

Was this reply helpful? Yes No
Suggested answer

Navneeth Nagrajan 2,538 Super User 2026 Season 1 on at

Like (2)

Report
Copy link

Link copied!

Hi,

1. Build servers are pre-configured or needs to be spinned up, based on your Dynamics Lifecycle Services (LCS) subscription. It is pre-configured and ready to start a build. Any configurations at any time can be altered through the Visual Studio IE or Azure DevOps interface. Ensure that source code is synchronize with the build machine for easy build setup.

There is a default agent pool that is attached to a build pipeline. Ensure that you have the required permissions to set this up in Azure DevOps.

2. Server based pipelines for deployment is an older approach and a cumbersome approach. You will need to ensure that the build server is turned on and has the latest source code synchronized. There is also an overhead of managing the default agent pool.
https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/perf-test/continuous-build-test-automation

3. In this case, you will need to use the default agent pools instead of the Cloud hosted agents. Refer to the link below for build agents.

https://learn.microsoft.com/en-us/azure/devops/pipelines/agents/agents

A few questions:

1. Are you planning to use Team Foundation Services (TFS) or Git for version control?

Hope this helps. Happy to answer questions, if any.

Was this reply helpful? Yes No
krishna.rao@dax 3,008 on at

Like (0)

Report
Copy link

Link copied!

Modified my response:;

Thanks for your responses so far.

I've created new environment. after 3-4 hours of servicing, it ended with status failed.

Any idea, what is the issue here and how to fix this?

Find below screenshot for reference.

Thanks,

Was this reply helpful? Yes No
udaY-ch 5,173 on at

Like (0)

Report
Copy link

Link copied!

Hi

Expand the Manage environment tab and scroll down to see the error / reason.

Thanks

Uday

Was this reply helpful? Yes No
Suggested answer

Anthony Blake 3,092 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi @krishna.rao@dax

If you can't find any failure information, try deploying your environment again, very often it just works second time around.

Build servers are just Cloud Hosted Dev environments with an agent running locally which is connected to Azure DevOps. If Azure DevOps is connected to in LCS, when you deploy your build server you will see your new available agent, and can set it's pool on your build pipeline to start using it.

If the agent doesn't deploy automatically, you can deploy it manually.

Anthony

Was this reply helpful? Yes No
krishna.rao@dax 3,008 on at

Like (1)

Report
Copy link

Link copied!

Using TFS.

Already raised Microsoft ticket on this.

Find the error details below. also attached screenshot for reference

Error code

0

Error message

Failed to fetch deployment error from outputXml.

Best regards,

Krishna.

Was this reply helpful? Yes No