Live Assist for Dynamics 365 chat and cobrowse features are supported across subdomains and domains in the following ways:
It's worth noting that if you stay within the same domain or subdomain, then chat and cobrowse persist when navigating to different pages, so long as the Live Assist for Dynamics 365 tags are in the pages.
Chat Experience
| Starting Domain | Next Domain | Behavior |
| example1.com | subdomain.example1.com | Chat Persists |
| example1.com | example2.com | Chat Does Not Persist |
| example1.com | subdomain1.example2.com | Chat Does Not Persist |
| subdomain1.example1.com | example1.com | Chat Persists |
| subdomain1.example1.com | subdomain2.example1.com | Chat Persists |
| subdomain1.example1.com | example2.com | Chat Does Not Persists |
| subdomain1.example1.com | subdomain1.example2.com | Chat Does Not Persists |
Cobrowse Experience
| Starting Domain | Next Domain | Behavior |
| example1.com | subdomain1.example1.com | Cobrowse Does Not Persist (But Can Be Restarted) |
| example1.com | example2.com | Cobrowse Does Not Persist |
| example1.com | subdomain1.example2.com | Cobrowse Does Not Persist |
| subdomain1.example1.com | example1.com | Cobrowse Does Not Persist (But Can Be Restarted) |
| subdomain1.example1.com | subdomain2.example1.com | Cobrowse Does Not Persist (But Can Be Restarted) |
| subdomain1.example1.com | example2.com | Cobrowse Does Not Persist |
| subdomain1.example1.com | subdomain1.example2.com | Cobrowse Does Not Persist |
NB. It's also worth noting that in scenarios where cobrowse does not persist but the chat does, then the Agent may end the cobrowse and re-request the consumer joins.
Cross-Origin Resource Sharing (CORS)
Live Assist for Microsoft Dyanmics 365 complies with the same-origin-policy mandated by browsers. When a user browses to a domain, the underlying page may reference images or resources which are accessed via a different domain. Such resources are subject to a Cross-Origin policy enforced by the browser. When cobrowse is initiated the Live Assist for Microsoft Dynamics 365 code will attempt to load resources from the other domain. These resources will need to specify an appropriate CORS-header in the HTTP response from their web-host. Without the CORS-header, the resources will not be visible to the agent during cobrowse.