Hello All,
We are working on both D365 for Retail and D365FinOps projects.
It appears that the recommendations/best practices I've heard about using the included Tier 1 environment as a build machine don't hold for Retail due to the additional requirements to make the Retail SDK work. There is a developer topology package you need to install for example, and you cannot install that on an environment defined as Build using deployable packages.
Recommendations from: docs.microsoft.com/.../new-environments-visual-studio-teams-branch-retail-projects
"Use the LCS portal to deploy a new build environment. We recommend that you use a cloud-hosted environment, because you will have more options and capabilities if you have administrative rights."
From the same article earlier on:
"One environment is included in the subscription. We recommend that you use this environment as a build environment."
which seems to be a contradiction, I guess they must have lifted the FinOps recommendations and altered for Retail but missed that.
The suggestion to use Cloud hosted seems a workaround to the enforced 'no-admin' on subscription environments, I do not like having different hosting methods/setup for Retail vs FinOps when the workaround of using cloud hosted is purely to address something Microsoft enforce but haven't considered every eventuality. Interested to hear general thoughts and other approaches to Build environments, and whether anyone has formally raised this with Microsoft?
My intention was to almost always use Tier 1 subscription environment as a Build environment in D365 Retail or FinOps projects as this was the strong lead I got from Technical Summit and others, but if we're stuck with these limitations I will likely change to all Build environments are Cloud-hosted for consistency between projects.