DXP Commerce/CMS11 deployment warning: The Azure Health Check fea

DXP Commerce/CMS11 deployment warning: The Azure Health Check feature is not working as expected

Johan Kronberg

Vote:

I'm looking at a CMS11 & Commerce Connect environment DXP deployment that has these warnings logged:

DXCS009, The source is missing assemblies needed for compatibility in DXP. Details: missing the Episerver.CloudPlatform.Cms.dll file, https://docs.developers.optimizely.com/digital-experience-platform/v1.3.0-DXP-for-CMS11-COM13/docs/requirements
DXCS007, The source is missing assemblies needed for compatibility in DXP. Details: missing the Episerver.CloudPlatform.Commerce.dll file, https://world.optimizely.com/documentation/developer-guides/digital-experience-platform/requirements/

Failed to validate default hostname ***prod-slot.dxcloud.episerver.net for the slot slot on site ***, falling back to ***prod-slot.azurewebsites.net
The Azure Health Check feature is not working as expected.

I'd prefer not to install the first two packages/DLLs mentioned since I've heard they can really mess things up...

But how can solve the last warning? Is that something that normally is handled inside the CloudPlatform-binaries?

#339542

Jun 26, 2025 13:31

Stefan Holm Olsen

Vote:

Hi Johan

Apparently those assemblies are optional. However, I like having them so all the integrations are set up automatically in DXP. When "self-hosting" in Azure, it is a whole other story.

The DXP documentation warns that you will get a warning. Probably the one you get.

If you really don't want to install those assemblies, you might have to emulate the health check endpoints (see EPiServer.CloudPlatform.Cms.Internal.CloudPlatformHealthCheckEndpointRoutingExtension and Microsoft.Extensions.DependencyInjection.WarmupHealthChecksBuilderExtensions) so DXP sees what it wants.

#339547

Jun 27, 2025 13:32