![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(38.4, 95%, 13%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAD%3C/text%3E%3C/svg%3E)
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(275.2, 16%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EV%3C/text%3E%3C/svg%3E)
Hi Athul Dev | JH/Technology Solutions,
you are experiencing a widespread server outage. Quick Assist relies on Microsoft's remote relay servers and authentication infrastructure to generate secure session codes. The application is explicitly informing you that those backend servers are currently failing to process requests.
Because you have successfully isolated this as a global Microsoft server drop, you should completely halt any local troubleshooting. Reinstalling the application, wiping local cache files, or altering Windows firewall rules will not resolve a cloud infrastructure outage. Your only course of action is to wait for Microsoft engineers to apply a server-side fix, which your tenant administrator can monitor via the Service Health dashboard in the Microsoft 365 Admin Center. If you require immediate remote access capabilities today, I highly recommend using the screen sharing and remote control features natively built into Microsoft Teams until the Quick Assist servers are restored.
Hope this answer has brought you some useful information. If it did, please hit “accept answer”. Should you have any questions, feel free to leave a comment.
VPHAN