Live Assist for Dynamics 365 Provisioning Issue
Update - We would like to inform that the workaround for installing the Live Assist is failing to authorize now via the API. Our Development Team is closely working with Microsoft to resolve the issue. Should there be another workaround available before the issue has been totally resolved, we will share it also.

For further clarification, you can reach our technical support by emailing support@liveassistfor365.com.
Dec 16, 2024 - 15:27 UTC
Update - As the recode to work with our third-party's new API is still ongoing, we would like to share here an article for the workaround we mentioned to successfully install/provision the Live Assist for Microsoft Dynamics 365 (LAD365).

If you need further assistance, please raise a request by emailing our technical support at support@liveassistfor365.com.
Dec 12, 2024 - 08:48 UTC
Update - As the recode to work with our third-party's new API is still ongoing, we would like to share here an article for the workaround we mentioned to successfully install/provision the Live Assist for Microsoft Dynamics 365 (LAD365).

If you need further assistance, please raise a request by emailing our technical support at support@liveassistfor365.com.
Dec 03, 2024 - 04:14 UTC
Identified - We have identified the cause of the issue where some partner's APIs have changed and so our provisioning broke. We have a temporary workaround in place while we recode to work with their new APIs.

If you are having an issue with installing Live Assist in your Dynamics, please raise a request by emailing our technical support at support@liveassistfor365.com.
Nov 19, 2024 - 13:32 UTC
Update - We continuously investigate this issue with our partner's engineering team to find the root cause. We appreciate your understanding. If it's urgent or you really need to install Live Assist in your Dynamics, please raise a request by emailing our technical support at support@liveassistfor365.com.
Oct 29, 2024 - 01:16 UTC
Update - We are continuing to investigate this issue with our partner where the installation of the Live Assist from the Microsoft AppSource may fail. Alternatively, you can install the Live Assist application from the Power Platform admin center > Resources (on the left pane) > Dynamics 365 apps > Live Assist for Dynamics 365 powered by LivePerson (with "Configured" status) > click "Manage". For more assistance, please contact Live Assist Technical Support at support@liveassistfor365.com.
Sep 13, 2024 - 06:52 UTC
Update - We are investigating this issue further and with our partner.
Sep 06, 2024 - 05:52 UTC
Update - We are continuing to investigate this issue.
Aug 30, 2024 - 00:03 UTC
Investigating - We have identified a potential issue with LAD365 service onboarding. We are currently investigating a provisioning issue for intermittent issues with the onboarding of Live Assist . Our engineers are actively investigating this issue. We'll post updates as soon as we have more information.
Aug 29, 2024 - 16:58 UTC

About This Site

Welcome to the Live Assist for Microsoft Dynamics 365 Service Status Dashboard.

To get help please visit our knowledge base at https://support.liveassistfor365.com

Uptime over the past 90 days. View historical uptime.
Co-browse Service Operational
Chat Service Operational
Chatbot Service Operational
Voice and Video Escalation Service Operational
Administration Portal Operational
Campaign Management Portal Operational
Billing Portal Operational
Onboarding Service Partial Outage
Supervisor Portal Operational
Messaging Service Operational
90 days ago
99.79 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Apr 1, 2026

No incidents reported today.

Mar 31, 2026
Technical issues with messaging service
Resolved - The issue has been resolved following the completion of all mitigation actions, and our monitoring has returned to expected operational levels. Bots will need to be restarted in order for the issue to be fully resolved. If you continue to observe issues with CB Bots, please restart the bot connectors.
Mar 31, 19:05 UTC
Update - The service is now in a recovery state and is demonstrating full stability. Our teams will continue to closely monitor the environment for a final period to ensure sustained operational health.
Mar 31, 18:42 UTC
Update - We are now in the recovery phase and are observing continuous improvements in service stability. We continue to closely monitor the environment for complete and sustained recovery.
Mar 31, 18:14 UTC
Update - Mitigation actions are complete. While service monitoring is ongoing, our partner teams are also proactively restarting any further impacted bots. It is recommended to restart any bots that continue to show issues.
Mar 31, 17:47 UTC
Monitoring - Initial mitigation efforts are complete. We are continuing to manually restart bot connectors for impacted brands to provide relief while the broader system recovery finalizes. We are closely monitoring connectivity across all accounts post-recovery to verify stability and determine if any further actions are required.
Mar 31, 17:30 UTC
Update - Initial mitigation efforts are complete. We are continuing to manually restart bot connectors for impacted brands to provide relief while the broader system recovery finalizes. We are closely monitoring connectivity across all accounts post-recovery to verify stability and determine if any further actions are required.
Mar 31, 17:18 UTC
Identified - The targeted mitigation efforts are nearing completion. An unexpected result of the mitigation efforts is that some customers are experiencing a bot connector issue; we recommend to restart the bot connectors. We are continuing to actively work on the remaining mitigation changes and will maintain close monitoring of the service to ensure full stability and performance.
Mar 31, 17:04 UTC
Update - We are observing a new, broad impact to messaging functionality in the region. Immediate action is being taken, with an expected mitigation time of up to 10 minutes. In parallel, work continues on the previously reported agent and bot messaging issue, which is expected to be fully mitigated within approximately 30 minutes.
Mar 31, 16:10 UTC
Update - Our 3rd party service provider is experiencing technical issues with the Conversational Cloud platform that are impacting Service Connectivity, User and Bot Login, as well as Bot conversation handling. Users could experience difficulty logging in the Conversation Cloud, disconnects and latency when navigating the platform. Bots could have issues connecting and handling conversations, as well as conversations getting stuck with them.
Engineering teams are working to resolve the detected behavior.
Mar 31, 15:03 UTC
Investigating - Our 3rd party service provider is experiencing technical issues where users may observe a reconnection message inside of our Conversational Cloud platform. Agent messages may be duplicated or agents may not be able to accept and close conversations.
Engineering teams are working to resolve the detected behavior.
Mar 31, 14:46 UTC
Mar 30, 2026

No incidents reported.

Mar 29, 2026

No incidents reported.

Mar 28, 2026

No incidents reported.

Mar 27, 2026

No incidents reported.

Mar 26, 2026

No incidents reported.

Mar 25, 2026

No incidents reported.

Mar 24, 2026
Issues with our messaging service EU region
Resolved - Engineering teams have resolved the issue affecting our messaging service.
Subsequent checks have confirmed the service’s health and stability.
Mar 24, 12:53 UTC
Identified - Internal teams have found and addressed the reported issue, and we are seeing improvements in service performance. Additional validation steps are ongoing to ensure the platform's stability moving forward.
Mar 24, 11:52 UTC
Investigating - Our 3rd party service provider is currently experiencing issues with our messaging service. Agents may be unable to switch their status or send messages in conversations. Engineering teams are working to resolve the detected behavior.
Mar 24, 10:35 UTC
Mar 23, 2026

No incidents reported.

Mar 22, 2026

No incidents reported.

Mar 21, 2026

No incidents reported.

Mar 20, 2026
Live Assist 3rd Party Incident - NA Region
Resolved - Our provider's engineering teams have mitigated the reported issue. Subsequent checks have confirmed the service's health and stability. If you have any issues related to this incident, please contact our technical team at support@liveassistfor365.com.
Mar 20, 05:54 UTC
Monitoring - Our provider's technical teams are continuously monitoring the system's performance and implementing mitigation actions.
Mar 20, 05:19 UTC
Identified - Our provider's technical teams have identified a potential cause and are taking action to mitigate the reported behavior.
Mar 20, 04:33 UTC
Update - The issue is still being investigated, and our provider is making steady progress toward resolving it.
Mar 20, 03:40 UTC
Investigating - Our third-party service provider is experiencing technical issues with the messaging service. Conversations may not be routing properly, and message delivery capabilities may be impacted. Their engineers are actively engaged in identifying and addressing the behavior. An update will be provided as soon as we receive additional information from our provider.
Mar 20, 02:58 UTC
Mar 19, 2026

No incidents reported.

Mar 18, 2026
Issues with Conversation Cloud
Resolved - Technical teams have concluded their investigation and confirmed that the service has returned to normal operation. We will continue to monitor the situation to ensure continued stability. If you are still experiencing issues, please contact our Customer Care team.
Mar 18, 15:24 UTC
Identified - Our 3rd party service provider has successfully restored the primary service responsible for the recent disruption. Focus has now shifted to restarting all dependent services. We are monitoring the recovery closely to ensure stability and will provide further updates as systems return to full capacity.
Mar 18, 14:32 UTC
Investigating - Our 3rd party service is experiencing issues with Conversation Cloud. Agents and customers may not be able to send messages, or message delivery latency may be observed. Users may be unable to log in or may get kicked out of the platform. Copilot Rewrite may also be temporarily unavailable. Technical teams are currently working to resolve the reported behavior.
Mar 18, 13:29 UTC
← Incident History Powered by Atlassian Statuspage