L67vle error in New Outlook (Desktop)

Question

Hi Team,

Hope you’re well.

I’m reaching out for assistance with an issue I recently started experiencing in Outlook (New).

Previously, when composing a reply, I would highlight my text and use Copilot to rewrite it.

However, since yesterday, I’ve been receiving the following nonsense output when attempting to do so:

Could you please advise on how I can resolve this?

I have already tried restarting my machine and left it for a day in case it was an isolated issue. I also checked for any outstanding updates, and there are none. I’m not experiencing any issues in other M365 applications, and the functionality works as expected in the classic version of Outlook.

Additionally, another user in my organisation who uses Copilot in the New Outlook is experiencing the same issue, so it appears not to be limited to my device.

Thank you in advance,

Rositsa

Answer 1

The issue should be backfixed now. It should not happen again if you restart the Outlook app.

Answer 2

Dear everyone, 

Welcome to the Microsoft Q&A forum.

I understand that the Rewrite function in Copilot is currently unresponsive across multiple platforms, including the web and the built-in Outlook app, despite working correctly in Classic Outlook.

Based on the details provided and recent reports within our forum, this behavior indicates a service-side regression specifically affecting the Copilot deployment in the New Outlook and web interfaces. Since the feature remains functional in Classic Outlook, I can confirm the root cause originates from the Copilot backend service rather than your local device configuration or tenant-level policies.

To expedite a resolution from the engineering team, I recommend submitting a formal bug report directly through the application. High volumes of feedback on specific features help the product team prioritize backend fixes.

1. Open the Outlook app and navigate to Help > Feedback.
2. Choose the Copilot category.
3. Select Report a Problem.
4. Provide a detailed description of the symptoms, noting that the issue persists across web and mobile but functions in Classic Outlook.
   

You can also share your feedback through the official feedback portal, where you can submit your concerns, issues, or errors so they can be reviewed. Additionally, you can upvote existing reports if you find an issue similar to yours.

To maintain productivity and avoid workflow interruptions, I suggest using Classic Outlook as your primary mail client while the backend deployment is being addressed.

If you find this information helpful, please consider marking it as the answer. This helps other users in the forum quickly notice that this is a widely reported issue and encourages them to submit feedback to the engineering team.

I appreciate your patience as Microsoft works toward a permanent fix.

---

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.