Moveworks Incident History

1. identifiedSep 4 · 13:09 UTC

   Workaround Available We have identified that, for some affected customers, the Available to setting for the Moveworks bot in the Microsoft Teams admin centre is set to No one. Restoring the appropriate availability has resolved the issue for some customers. Teams administrators can update this setting by following these steps: 1. Sign in to the Microsoft Teams admin centre. 2. Go to Teams apps → Manage apps and select the Moveworks bot. 3. Open the Users and groups tab. Alternatively, select No one (org-wide default) if it appears as a link. 4. Under Availability, select Edit availability. 5. Change Available to from No one to one of the following: Everyone — Select this if all users in the tenant should have access to the bot. This is the most common setting for Moveworks deployments. Specific users or groups — Select this to restrict access to particular security groups, Microsoft 365 groups, dynamic membership groups, or distribution lists. Search for and add the required users or groups. 6. Select Apply to save the change. Microsoft advises that availability changes can take up to 24 hours to apply to all users and, in rare cases, up to six days to appear in the Teams client. However, the change may take effect sooner. We are continuing to investigate the underlying cause and will provide further updates as more information becomes available.

Reported by Moveworks on their status page.

1. monitoringSep 1 · 17:16 UTC

   Microsoft's mitigation continues to roll out and we are monitoring propagation. Most users should see the correct custom logo restored. If any users are still seeing the default Moveworks logo, please capture a HAR file while reproducing the issue and share it with Moveworks Support. We will share additional updates as progress continues.

Reported by Moveworks on their status page.

1. resolvedAug 21 · 17:20 UTC

   The intermittent unresponsiveness of the AI Assistant in Microsoft Teams has been resolved. Responses have returned to normal, and we have confirmed stability through continued monitoring. No further action is required from customers.

Reported by Moveworks on their status page.

1. resolvedAug 12 · 14:38 UTC

   This incident has been resolved.

Reported by Moveworks on their status page.

1. resolvedAug 12 · 14:38 UTC

   This incident has been resolved.

Reported by Moveworks on their status page.

1. resolvedAug 10 · 17:33 UTC

   This incident has been resolved.

Reported by Moveworks on their status page.

1. identifiedAug 10 · 13:41 UTC

   We have identified authentication failures affecting SharePoint Online integrations that use Microsoft App Store authentication, following Microsoft’s deprecation of the legacy ACS authentication method. As a result, legacy SharePoint knowledge ingestion will fail for affected customers. As an immediate workaround, please follow the SharePoint Online Azure App Registration guide. https://docs.moveworks.com/service-management/access-requirements/knowledge-base-systems/sharepoint-online-access-requirements-new-1#1-configure-azure-app-registration Engineering is working on a JWT-based update for Microsoft App Store authentication. We will share additional updates as they become available.

Reported by Moveworks on their status page.