Hi Jeroen,

Are you talking about the Azure database export or the CMS package export?

The CMS export/import functionality to export/import content from the CMS. We use it to transform content from an TEST to an ACC or Production environment without the need to create all content again. And it saves us from DB copies as we use shared environments with multiple websites on a single instance.

Hi Jeroen,

As I understand it, the export process consists of three parts. In the first part, clicking the export button starts the export process in the background. There's then a series of XHR requests made to check the status of the export then, once the status call reports that the export is complete, there's a final call to prompt the download of the file. This export process occurs on a single server so, for the process to work end-to-end, the requests all need to be handled by the same server.

If the session affinity thing is a deal-breaker and your license allows, one option might be to set up a separate web app for editing linked to the same database, service bus and blob storage as the public-facing site.

@Paul: I had the same thougth about this, but the thing is that I can't find any official statement or documentation that this setting needs to be enabled in order to let this work properly. My conclusion is so far that on Azure Web Apps ARR Affinity needs to be enabled to let CMS Export/Import functionality work properly. So I was more looking for a confirmation if this really is the case or that this is a bug that it also should work without ARR Affinity enabled.