London Dev Meetup Rescheduled! Due to unavoidable reasons, the event has been moved to 21st May. Speakers remain the same—any changes will be communicated. Seats are limited—register here to secure your spot!

Stefan Johansson
Mar 27, 2025
  503
(0 votes)

Transitioning to Application Insights Connection Strings: Essential Insights for Optimizely CMS

Transitioning to Application Insights Connection Strings: Essential Insights for Optimizely CMS

As part of Microsoft's ongoing modernization efforts, Application Insights is transitioning from instrumentation keys to connection strings. While your current implementations using instrumentation keys will continue to operate seamlessly, we strongly recommend updating to connection strings. This ensures alignment with Microsoft's latest standards and maximizes the performance of your Optimizely solutions.

New environments will now be equipped with connection strings by default.

This blog post provides a guide to updating your Optimizely CMS projects, ensuring seamless compatibility with these changes.

Guidance for Optimizely CMS 12 Projects

Existing Projects

  • Promptly update to the latest versions of EPiServer.CloudPlatform.Cms (and EPiServer.CloudPlatform.Commerce, if applicable).
  • Following the update, your next deployment will automatically configure your application to utilize the correct Application Insights connection string.

New Projects

  • Deployments will be restricted unless you are using the updated versions of EPiServer.CloudPlatform.Cms (and EPiServer.CloudPlatform.Commerce, if applicable).
  • Ensure all project dependencies are current before initiating a deployment.

Guidance for Optimizely CMS 11 Projects

Without Custom Application Insights Configuration

  • If there is no custom Application Insights configuration, your next deployment will seamlessly update your application to use the correct connection string.

With Custom Application Insights Configuration

  • Verify that your custom implementation is compatible with connection strings.
  • Reach out to Optimizely support to confirm and deploy the correct configuration for your application.

For more detailed information from Microsoft, please refer to their documentation here.

Mar 27, 2025

Comments

Scott Reed
Scott Reed Mar 31, 2025 08:56 AM

Can you clarify on the specifics around new projects?

Does this only affect new clients or projects in the PaaS portal, e.g if we use the migration tooling that spins up a new project I assume first deployments will need to be on EPiServer.CloudPlatform.Cms. If we're in the middle of a go live process for a migration however I assume this will be unaffected?

Please login to comment.
Latest blogs
Identifying Spike Requests and Issues in Application Insights

Sometimes within the DXP we see specific Azure App Instances having request spikes causing performance degredation and we need to investigate. I fi...

Scott Reed | Apr 25, 2025

Optimizely Frontend Hosting Beta – Early Thoughts and Key Questions

Optimizely has opened the waitlist for its new Frontend Hosting capability. I’m part of the beta programme, but my invite isn’t due until May, whil...

Minesh Shah (Netcel) | Apr 23, 2025

Developer Meetup - London, 21st May 2025

The London Dev Meetup has been rescheduled for Wednesday, 21st May and will be Candyspace 's first Optimizely Developer Meetup, and the first one...

Gavin_M | Apr 22, 2025

Frontend hosting for PaaS & SaaS CMS

Just announced on the DXP, we FINALLY have a front end hosting solution coming as part of the DXP for modern decoupled solutions in both the PaaS a...

Scott Reed | Apr 22, 2025