
Announcements
You're encountering a nuanced issue with ARRAffinity cookies in Power Pages when using Azure Front Door (AFD) with a custom domain. Here's a breakdown of what's happening and what you can do:
The ARRAffinity cookie is set by Azure App Service (which underpins Power Pages) to maintain session stickiness. It is hardcoded to the App Service domain (e.g., *.azurewebsites.net or *.powerappsportals.com) and does not respect the custom domain set via Azure Front Door. This is a known limitation .
Even if you configure a custom domain in AFD and Power Pages, the ARRAffinity cookie will still be scoped to the original backend domain, which causes it to be blocked by browsers due to domain mismatch.
You're absolutely right to ask about the ASLBSA cookies. These are:
So yes, ASLBSA cookies are effectively the replacement for ARRAffinity in this architecture.
Ignore ARRAffinity in this setup.
Rely on ASLBSA cookies for session stickiness.
Optional: Disable ARRAffinity at App Service level
Ensure Origin Host Header is set to the custom domain in AFD.