Path to image isn't correct when using .less & CDN

I'm not sure I understand, as those settings are producing what seems to be the expected result - you've configured Azure for your filestorage, and it's looking there for the file. What is the actual valid url for the file?

That's right.. Azure is used for filestorage, so the 'cfs-file' part of the URL doesn't match any 'container' in the storage account.. the container is called 'e14core' (the name of our custom CFS).

The correct URL would be;

https://mysite-storage.mydomain.com/e14core/images/icons/small-gray-padlock.png

So this goes to the correct container, and un-encodes the _2D00_ back to a dash like the file has on disk, and also has the correct sub-path (images/icons).

After further investigation, what I initially suggested is not possible. I've removed that reply. 

Community does not support CDNs in any released version. The current implementation of Azure CDN support does not work with stylesheets. The workaround is to disable CDN for file stores that contain stylesheets.

Our upcoming version 12.1 adds CDN support, and what you are attempting would be possible there. I've also logged a bug to investigate possible resolutions of the issue in the current implementation of Azure CDN.

Thanks for coming back to this, even if it doesn't solve it. We'll work around the problem for now.

I'm looping back again with another option to work around this issue.

Rather than storing the file in another filestore, you could embed the file within the widget (Upload Attachment) and then use the -evo-widgetfile-url LESS function to reference the file.

.e14-ranked-locked-icon {
    width: 8px;
    height: 11px;
    float: right;
    margin-right: 8px;
    margin-top: -30px;
    background: url(-evo-widgetfile-url("small_2D00_gray_2D00_padlock.png")) no-repeat 0 0;
}

Thanks for the suggestion, but we'd prefer to put assets like this in the filestore, since they'll be used across more than 1 widget. I can see this approach working fine for some folks, so it's good to highlight it here

Thanks for the suggestion, but we'd prefer to put assets like this in the filestore, since they'll be used across more than 1 widget. I can see this approach working fine for some folks, so it's good to highlight it here

To clarify this, the use of this function is the required approach, not a work around.   Referencing of physical files using the function and embedding the file in the widget is how the system should work as the widget is a portable container.

Could you confirm that in 12.1 (which adds CDN support), I'd be able to reference an image in the CFS as per my original post (see code examples).