How we did for AWS, on Azure I think should be pretty the same: Create test1 page that will display server name(CD1, CD2, etc.) and put information to session: trigger some goal and save some information directly to session. For example something like: //Register goal var goalTrigger = Sitecore.Analytics.Tracker.MarketingDefinitions.Goals[{SomeGuid}]; ...


You dont need to disable session to not store a page in Mongo/xDB. Just disable it in the content editor. Analyze > Attributes > Disable Analytics for this page


From the error it seems that your database server is not configured with Contained Authentication. Please execute below script on your server sp_configure 'contained database authentication', 1; GO RECONFIGURE; GO


I've seen this happen with the Forms Authentication cookie before. Multiple instances of the same cookie get added and the most specific domain wins. I ended up creating a method to remove all but the first instance of the cookie from the HttpContext.Current.Response.Cookies collection. I found the first cookie in the collection to be the correct one in my ...

Only top voted, non community-wiki answers of a minimum length are eligible