Anyone an idea if something recently changed with the hosting of the images / URLs?
In our original email templates in our outbound marketing we obviously include headers and footers (and other images) which back then -upon creation of the generic templates- were selected and included with their original current URL; thus with the svc.dynamics.com domain.
Now if you select images from the current library I've noticed they are pointing to some other location and they may be hosted elsewhere; from the mkt.dynamics.com domain.
Was this actually foreseen in any of the previous releases?
And was there any plan to deprecate the old domain?
+ advice how to prevent any impact or how to deal with this deprecation
Is it correct that these %svc.% domain recently got deprecated?
Was this perhaps an older change but only recently disabled without any further communication.
I seem to notice in our old emails, but also still in our more recent emails (which are created from such older templates still using the other URL) that our images no longer render. If I try to check the html and open the image I get an error:
legacy endpoints are disabled.
An example image:
images.mktsvcp102we001.svc.dynamics.com/org-da2c2b6a47644a22ac5ed8ef73cd8d90/c59c2a7e-3a1d-ec11-b6e6-6045bd8d28b5/2KM-ImhHDJ85BAXjhSMEh2XAWqLJR3tcVRNTyqU9eUY!
So emails that are recently sent (still using such older template where those images still rendered until recently), the header and footer will no longer appear in their emails ... which is pretty annoying to notice soon after.
Looks as if this has just recently started to affect and impact us.
Did we miss something? I don't seem to find such info.
Was this expected and communicated?
I start to fear we may have missed something and the only option left to fix it for future mailings is to go over each and every template and alter all of our images?
Or was that normally included in the plan while moving the images?
Cause it wouldn't be the most pleasant job if we need to manually alter each image in each template.
Anyone some idea or some more information on this sudden legacy endpoint disablement?
Thanks
Tom