Finance | Project Operations, Human Resources, ...

Deploy package to production environment without a Sandbox environment

(0) Share

Report

Posted on by Roberto Vzz

Hi all,

Currently I have a Cloud-hosted Build environment where I create a deploy package,
I want to release this package to a production environment, the problem is that it is necessary to first pass it through a sandbox environment,
unfortunately I do not have one and Microsoft no longer allows me to create environments Sandbox for its new policies,
any idea how to deploy my package to production?

Thanks!

I have the same question (0)

All responses (8)

Answers (0)

Suggested answer

Gunjan Bhattachayya 35,423 on at

Like (0)

Report

Hi Roberto Vazquez,

Microsoft does not allow deployment of Tier-1 sandbox environments . You can still deploy Tier-2 sandbox environments. Please check logging into LCS. You should have an option to deploy the the sandbox environment.

As for your question, it is mandatory to deploy a package into a Tier-2 environment so that it is marked as a release candidate. Only then the package will be available for deployment onto Prod.

Was this reply helpful? Yes No
Roberto Vzz 15 on at

Like (0)

Report

Hi Gunjan, thank you for you reply,

In my lcs I'm only able to deploy a Cloud-hosted environment, the option in the main menu no longer appears.

For Cloud-hosted environment these are the options.

for DEVTEST

These two options are created as Cloud-hosted environments.

If any of these options are Tier-2?

Was this reply helpful? Yes No
Gunjan Bhattachayya 35,423 on at

Like (0)

Report

Hi Roberto,

It shouldn't be a cloud hosted environment. Do you see an option below "Production" environment for "Sandbox: Standard

Acceptance Test"?

Was this reply helpful? Yes No
Roberto Vzz 15 on at

Like (0)

Report

I have a sandbox environment but it already contains changes from another project, I don't know if I delete it Microsoft let me create a new one, previously I had a Sandbox Dev environment, I deleted it and I could no longer create a new one.

Was this reply helpful? Yes No
Suggested answer

Gunjan Bhattachayya 35,423 on at

Like (0)

Report

It will let you re-configure this sandbox environment. I believe the environment you would have deleted would have been "Sandbox : Develop and Test". After Nov2, 2020, you cannot deploy Sandbox Develop and Test (Tier-1) environments

This environment is a Tier-2 environment and deploying your deployment package onto this environment will enable you to mark the package as a release candidate.

In case you have any dounts/questions, you may reach out to MS support to confirm regarding deletion and re-deployment of this environment

Was this reply helpful? Yes No
Suggested answer

Ahmad_Sufyan on at

Like (0)

Report

Indeed you have to apply package to UAT first and mark it as released candidate to proceed with applying into prod.

doc for non self service: https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/deployment/apply-deployable-package-system#apply-a-package-to-a-production-environment-by-using-lcs

for self service: https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/deployment/updateenvironment-newinfrastructure#production-environment

Note: UAT is mock test for package before going live so it is mandatory.

Regarding: Environment deletion.

Ans: I see what you are using is default license 1 prod+ 1 sandbox. If you delete configure will be available again.

(Make sure VSTS is configured).

The slot dis appears when you have add-on license for UAT and license count doesn't match against that.

Was this reply helpful? Yes No
Suggested answer

nmaenpaa 101,160 Moderator on at

Like (0)

Report

As others have already said, you must always deploy every deployable package succesfully to your UAT system (Sandbox Tier 2) before you can deploy to Prod.

Same applies to all Microsoft updates.

New Sandbox Tier 1 systems can't be deployed anymore, but those could not be used for deployable package validation in the past, either. You always needed to use Tier 2 system which has similar architecture than the prod system. Tier 1 is used for development or build purposes, and for those purposes you must now use cloud hosted environmnents or locally hosted VMs. (And for build you don't need a server anymore, you can use hosted build agent in Azure DevOps if you want to).

If your Sandbox Tier 2 system contains customizations from another project (how did you end up in such situation?) you must delete the system and deploy it again.

Was this reply helpful? Yes No
André Arnaud de Cal... 300,911 Super User 2025 Season 2 on at

Like (0)

Report

Hi Roberto,

Are the customizations from another project also part of the total solution for this customer environment? If so, note that you would need all-in-one deployable packages containing all extension models to be deployed to the production environment. This package would be validated in your standard acceptance test environment before you can deploy it to the production environment. If the other project should not yet be deployed to the production environment, then it shouldn't be in this acceptance environment.

Was this reply helpful? Yes No