Rotate the expired or nearly expired SSL certificate on your subscription’s one-box environments

On April 23 2018 17:00:00 UTC, the SSL certificate on one-box environments that are under your subscription and not managed by Microsoft, will expire. Project owners or Environment managers can rotate the certificate from LCS.

If you do not rotate the certificate, when you try to use Dynamics 365 for Finance and Operations or Dynamics 365 for Retail, you will receive an error that your certificate is not valid.

To rotate the certificate, complete the following steps on each Environment page in LCS.

Note: Complete these steps only on environments that are under your subscription.

  1. Log in to and navigate to Cloud Hosted Environments page in your project.
  2. Select an environment, and in the right pane click Full Details
  3. On the Environment details page, click Maintain > Rotate secrets. Please note that this option will only show for environments in the Deployed state. If your environment is in the Stopped state, you will need to Start it first to see this option.

  4. Select Rotate the SSL certificates and confirm that you want to perform this action. Note that rotating the SSL certificate can't be reversed.

  5. After the certificate rotation is complete, the environment history will be updated. You can view the history by clicking History > Environment changes on the Environment details page.


Comments (2)

  1. If you receive a message when opening the Environment Details page that says “An error has occurred. Please try again later” there is a temporary workaround until we can fix the issue that you can do. Go to the Tools icon in the upper right of LCS and choose Language Preference. Then change your language preference temporarily to English US and then refresh your browser. When you go to the Cloud Hosted Environments page again, verify that the dates are showing in mm/dd/yy format and then try the Full Details link again.

  2. SteeveG says:

    It took 4 hours to appear as completed in the environment history but I still get the same certificate error. Anything I should look at?

Skip to main content