Office 365 Collaborations - Sessions Expired Error

[sendres]

Is anyone else seeing this? When attempting to create an Office 365 Collaboration, a "your session has expired" error occurs. I have filed Case 04930126 with Instructure to see if they can identify the cause.

Steps to reproduce:

1. In a Canvas course, click COLLABORATIONS in the course navigation menu.
2. Click START A NEW COLLABORATION.
3. Select OFFICE 365.
4. Log in to Office 365 when prompted.
5. Select WORD as the document type (or whatever...it doesn't matter).
6. Enter a name for the document.
7. Select one or more students to collaborate with (optional).
8. Click SAVE.

Result: Two error messages are displayed:

1. Your session has expired, please log back in.
2. An unexpected error occurred.

Expected result: The new O365 collaboration is created without errors.

[bclay1]

I had the same problem. Turns out I didn't have the Collaborations module enabled in the Canvas Navigation settings.

• Go to Settings/Navigation
• Mouse over Collaborations and click on the three dots for "Edit Course Navigation"
• Click on Enable

[rshafer]

I have the same problem described by the OP, but I've verified that collaborations are already enabled! What else can I do to fix this?

[tryggvimar]

I am experiencing the same issues here. Have you had any information on this issue?

[j_c_turner · Accepted solution]

yes we are getting this reported a lot. but seems like you can fix it by clicking on the office 365 link in the course navigation and then you can create the shared document. its like the authenitcation tocket for MS is not sticking or getting shared. it/s my theory anyway

wish there was an answer

jim

[LeannaSue]

I had Office 365 disabled in my Navigation until I read your reply, Jim. I just re-enabled it, and then the Collaborations worked. After I set up the Collaboration file, I went back to hide Office 365 from students in the Navigation. THANKS for your help, Jim!

[Choachy]

Its August 2024 and this is still an issue. Same error messages but thankfully, your workaround still works. I'm just wondering if the students are going to have this same error message when they try to collaborate on the doc? We'll see after some testing.