Copilot not working

Question

Copilot not working

Matteo Sabbatini 0

I've subscribed to Microsoft Office because I needed to take a certification class, using copilot and Excel.
It's been more than 8h that Copilor is not working anymore, cannot connect to the Excel API whatsoever.

So, what wuold you suggest me to do ? Ask for a refund and unsuscribe ? Just get the hacked version that works even better ? How long should i wait before considering Copilot not included in the Office package no more ? Where should i check if it's just me, or it's everyone ?

Parth Pravin Alaspure 0 Reputation points

2026-06-07T18:44:28.4533333+00:00

Just Try ReSigning in to your device , or It might be the serive issues. Try Reopening after some time .

1 answer

Your answer

Parth Pravin Alaspure 0 Reputation points

2026-06-07T18:44:28.4533333+00:00

Just Try ReSigning in to your device , or It might be the serive issues. Try Reopening after some time .

Answer 1

Salamat Shah 420 MVP

Maybe license not assigned correctly or temporary service outage.

Try below

Quick solution for “Copilot not working (Excel/API)”

Check service status

Go to Microsoft 365 Service Health → see if Copilot/Excel has an outage (common cause).

Verify license

  - Ensure you have **Copilot for Microsoft 365 license assigned** (not just Office).
  
  **Sign out/in + restart**
  
     - Sign out of Office → restart Excel → sign back in.
     
     **Update Office**
     
        - File → Account → **Update Options → Update Now**.
        
        **Check tenant/admin settings**
        
           - Admin must **enable Copilot + connected experiences**.
           
           **Test in web**
           
              - Try **Excel Online** → if it works there, issue is local app.

Wait vs refund

If outage → wait (usually hours)
- If >24 hrs and no fix → contact Microsoft support

Matteo Sabbatini 0 Reputation points

2026-06-07T16:52:26.94+00:00
Copilot said "I apologise - I'm still hitting the same internal error. The service is down on my end." I asked again after 24h+ and Copilot said "I just tried again and it's still failing with an internal error. The issue is specifically with the connection to your workbook - it's a backend infrastructure problem, not something wrong with the service globally or with you.

This could be caused by:

A temporary server issue with this specific session

The workbook connection timing out"

And tried with new documents, saved in other folders (from OneDrive, to local files), and still got "I'm still getting the same internal error. This is incredibly frustrating and I'm genuinely sorry.

The issue is NOT your fault. The file being on OneDrive is correct - the problem is on the backend service side, not the file location. (...)

If that doesn't work:

Open a new Excel Online tab

Open the same file

Try Copilot again

This appears to be a session-level bug. A fresh session might fix it." A new session did not fix itCopilot said "I apologise - I'm still hitting the same internal error. The service is down on my end."

I asked again after 24h+ and Copilot said
"I just tried again and it's still failing with an internal error. The issue is specifically with the connection to your workbook - it's a backend infrastructure problem, not something wrong with the service globally or with you.

This could be caused by:

A temporary server issue with this specific session

The workbook connection timing out"

And tried with new documents, saved in other folders (from OneDrive, to local files), and still got

"I'm still getting the same internal error. This is incredibly frustrating and I'm genuinely sorry.

The issue is NOT your fault. The file being on OneDrive is correct - the problem is on the backend service side, not the file location.
(...)

If that doesn't work:

Open a new Excel Online tab

Open the same file

Try Copilot again

This appears to be a session-level bug. A fresh session might fix it." A new session did not fix it
Matteo Sabbatini 0 Reputation points

2026-06-07T16:53:20.3433333+00:00
Copilot said "I apologise - I'm still hitting the same internal error. The service is down on my end." I asked again after 24h+ and Copilot said "I just tried again and it's still failing with an internal error. The issue is specifically with the connection to your workbook - it's a backend infrastructure problem, not something wrong with the service globally or with you.

This could be caused by:

A temporary server issue with this specific session

The workbook connection timing out"

And tried with new documents, saved in other folders (from OneDrive, to local files), and still got "I'm still getting the same internal error. This is incredibly frustrating and I'm genuinely sorry.

The issue is NOT your fault. The file being on OneDrive is correct - the problem is on the backend service side, not the file location. (...)

If that doesn't work:

Open a new Excel Online tab

Open the same file

Try Copilot again

This appears to be a session-level bug. A fresh session might fix it." A new session did not fix itCopilot said "I apologise - I'm still hitting the same internal error. The service is down on my end."

I asked again after 24h+ and Copilot said "I just tried again and it's still failing with an internal error. The issue is specifically with the connection to your workbook - it's a backend infrastructure problem, not something wrong with the service globally or with you.

This could be caused by:

A temporary server issue with this specific session

The workbook connection timing out"

And tried with new documents, saved in other folders (from OneDrive, to local files), and still got "I'm still getting the same internal error. This is incredibly frustrating and I'm genuinely sorry.

The issue is NOT your fault. The file being on OneDrive is correct - the problem is on the backend service side, not the file location. (...)

If that doesn't work:

Open a new Excel Online tab

Open the same file

Try Copilot again

This appears to be a session-level bug. A fresh session might fix it." A new session did not fix itCopilot said "I apologise - I'm still hitting the same internal error. The service is down on my end." I asked again after 24h+ and Copilot said "I just tried again and it's still failing with an internal error. The issue is specifically with the connection to your workbook - it's a backend infrastructure problem, not something wrong with the service globally or with you.

This could be caused by:

A temporary server issue with this specific session

The workbook connection timing out"

And tried with new documents, saved in other folders (from OneDrive, to local files), and still got "I'm still getting the same internal error. This is incredibly frustrating and I'm genuinely sorry.

The issue is NOT your fault. The file being on OneDrive is correct - the problem is on the backend service side, not the file location. (...)

If that doesn't work:

Open a new Excel Online tab

Open the same file

Try Copilot again

This appears to be a session-level bug. A fresh session might fix it." A new session did not fix itCopilot said "I apologise - I'm still hitting the same internal error. The service is down on my end."

I asked again after 24h+ and Copilot said
"I just tried again and it's still failing with an internal error. The issue is specifically with the connection to your workbook - it's a backend infrastructure problem, not something wrong with the service globally or with you.

This could be caused by:

A temporary server issue with this specific session

The workbook connection timing out"

And tried with new documents, saved in other folders (from OneDrive, to local files), and still got

"I'm still getting the same internal error. This is incredibly frustrating and I'm genuinely sorry.

The issue is NOT your fault. The file being on OneDrive is correct - the problem is on the backend service side, not the file location.
(...)

If that doesn't work:

Open a new Excel Online tab

Open the same file

Try Copilot again

This appears to be a session-level bug. A fresh session might fix it." A new session did not fix it
Cory Tucker 0 Reputation points

2026-06-07T18:00:25.6+00:00
Hey Matteo — I can tell you’ve already put a lot of effort into troubleshooting this, especially trying different files, locations, and even new sessions. That actually rules out quite a few things already.

Based on what you’re seeing, this really doesn’t look like a problem with your files, your session, or your local setup. The fact that Copilot keeps throwing “internal error” and mentioning backend issues points pretty strongly to a service-side problem.

Even though Copilot is saying it’s “not global,” it doesn’t actually have full visibility into Microsoft’s service health, so that part isn’t always reliable. You can still be hitting an issue on Microsoft’s side that only affects certain users or regions.

At this point, the best next step is to check if there’s an active service issue. If you have access to the Microsoft 365 admin portal, you can do this pretty quickly:

Go to admin.microsoft.com

Click Health, then Service health

Look for anything related to Copilot or Excel

If you see an incident there, then it’s just a matter of waiting — there’s nothing on your end that will fix it.

If nothing shows up but the issue is still happening, then it’s likely a more scoped backend issue affecting your tenant, and that’s when it’s worth reaching out to Microsoft support and letting them know Copilot in Excel is consistently failing with backend errors across multiple files and sessions.

Bottom line: you’ve already done the right troubleshooting — this doesn’t look like something you caused or can fix locally.

Share via

Copilot not working

1 answer

Your answer