Basundhra

Debugging Sitecore Analytics on Azure: Lessons From a Real Deployment When deploying a Sitecore solution on Azure PaaS, most teams expect Sitecore Analytics to work out-of-the-box—especially when the deployment follows the standard ARM templates or the Sitecore Azure Toolkit. But during one of our recent deployments, we noticed that Sitecore Analytics was not working at all , even though the application was healthy, CD/CM were synced, and the xConnect endpoints were reachable. After investigation, we found the root cause: allowInvalidClientCertificates was not enabled in our ARM template. And enabling this single configuration value instantly fixed Analytics. This blog walks you through the issue, symptoms, root cause, and how re-deploying the ARM template with the correct setting resolved everything. The Problem: Analytics Events Not Being Recorded Even though: xConnect services were up XP roles were able to communicate CM/CD could reach the xConnect endpoint No major...

Enabling Custom Domain URLs for Media Files in a Sitecore Headless (JSS + Next.js) Project Recently, while working on a Sitecore XP 10 solution integrated with Next.js (JSS) , I came across a requirement to serve media assets via a custom domain instead of the default Sitecore CM/CD URLs. This is a common scenario when optimizing for performance, SEO, and CDN configurations — especially when you want to serve images from a brand-specific or region-specific domain like https://Customdomain.com instead of the default https://sitecore-cd.azurewebsites.net . Step 1: Define Media Base URL in Next.js In your Next.js environment configuration , add a new variable to define the media domain: NEXT_PUBLIC_MEDIA_BASE_URL= https://Customdomain.com   This allows your front-end components to dynamically resolve Sitecore media URLs from the correct domain at runtime. Step 2: Configure Site Definition in Sitecore Next, you need to update the Sitecore site definition to use the same domai...