Our sitecore sites are hosted in Azure Web. We use ARR (Azure Request Routing) to redirect traffic between sitecore site vs. existing legacy site until we fully migrate the legacy pages on to sitecore.

While testing FXM, noticed a weird behavior with how sitecore FXM generates end point for sitecore/api/ssc/Beacon/Service. Instead of generating the public domain it seems to generate azure internal azurewebsite url.

For example, our beacon JS is hosted on https://fxm.poc.com.au/bundle/beacon

However, the response we get from this request has :

SCBeacon = new SCBeacon("//fxm.azurewebsites.net/sitecore/api/ssc/Beacon/Service");

It should be

SCBeacon = new SCBeacon("//fxm.poc.com.au/sitecore/api/ssc/Beacon/Service");

When I look at temp folder on azure, noticed that all the beacon file exept the beacon.js has incorrect URL:

enter image description here

I made sure that

FXM.Hostname is set to fxm.poc.com.au

Still isn't working.


Looking at BeaconLoadProcessor, the code seems to construct a URL from Context.Request.URL. Which is interesting and unsure how it would work in azure as we don't want to expose origin URL and are IP whitelisted: enter image description here

1 Answer 1


Sitecore has acknowledged this as bug and provided a patch for SC8.2 update 1. Ask support for support ticket 507773 patch.

Basically fix is use the FXM.Hostname if specified otherwise Current.Request.URL

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.