Skip to main content

Notifications

Rotate Secrets (SSL certificate) using LCS for the Dynamics 365 for Finance & SC Cloud hosted environments

When you deploy a Dynamics 365 for Finance & SC cloud-hosted one-box environment, the SSL certificate will be valid for a year. After that, you will need to rotate certificates. Credential rotation is an essential component of enterprise-grade cybersecurity, and you can do it using the LCS portal.

IIS

When the SSL certificate is no longer valid, you will receive an error stating “Your connection isn’t private” when you try to use Dynamics 365 for Finance & SC:

When the SSL certificate is no longer valid, you will receive an error stating “Your connection isn’t private”

You can resolve the error by rotating the SSL certificate. To rotate the SSL certificate, follow the next steps:

  1. Log in to https://lcs.dynamics.com and navigate to Cloud Hosted Environments page in your project.
  2. Select an environment and click Full Details.
  3. On the Environment details page, click Maintain > Rotate secrets.
    3. On the Environment details page, click Maintain > Rotate secrets.
  4. Select Rotate the SSL certificates and confirm that you want to perform this action.
    Select Rotate the SSL certificates and confirm that you want to perform this action.
  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.
    After the certificate rotation is complete, the environment history will be updated.

Note: Project owners or Environment managers can rotate the certificate from LCS.

If you want to know how to rotate certificates on a D365 on-premises environment, please read this article from my colleague Eugene Dmytriienko:

https://community.dynamics.com/ax/b/axinthefield/posts/on-premises-certificate-rotation

 

Thanks for reading,

Said

Acknowledgments: I want to thank my colleague Amy Flowers (Customer Engineer) for her contributions and peer review.

Comments

*This post is locked for comments