A first-time poster... be kind :) I’ve searched the posts and haven’t found a similar complaint, so here it goes…
In Teams (web or app), a OneNote file stored in a Teams channel can be opened successfully using the “Edit in Teams” or “Open in browser” feature of Teams. However, when attempting to open the same OneNote file with the "Open in app" feature of Teams, the default OneNote app (modern or desktop) pops warning/error messages and fails to open the notebook.
- OneNote 2009 (aka OneNote desktop) first shows a Security Notice message indicating the “location may be unsafe”. Clicking Yes to continue then shows an error stating “We can’t open that location”.
- OneNote for Windows 10 (aka OneNote modern) shows an error stating “Sorry, we can’t open the notes that you were looking for”.
We’ve reproduced the issue…
- across Windows 10 PC's
- across M365 Tenants
- with both versions of OneNote (modern and desktop)
- with various M365 users (licensed, unlicensed, and guests)
- and across Teams clients (web and app)
I’m pretty sure this has worked fine in the past, but I can’t provide a specific date when I think it last worked correctly.
Works from SharePoint
When using "Open in app" from SharePoint, the same OneNote file opens successfully with either OneNote app as the default in Windows. OneNote desktop still warns “the location may be unsafe” but clicking Yes to continue opens the notebook successfully. OneNote modern opens the notebook successfully, showing no error or warning.
Works with other Office files
Word, Excel, and PowerPoint files all open successfully in their respective apps using the “Open in app” feature of Teams (web and app).
A “Tail” of Two URLs
If OneNote desktop is the default app in Windows for the "onenote:" URL, the Security Notice warning message provides the actual URL passed to OneNote.
The Security Notice shows that the onenote: URLs used by the "Open in app" feature in SharePoint versus Teams are identical except that Teams adds additional "junk" to the end of the URL. This “junk” seems to cause the failure.
The example above shows an attempt to “Open in app” the “test beta notebook” OneNote file from the General channel of the Beta Team. The extra “junk” is shown below in red at the end of the Teams URL (second bullet).
- SharePoint = onenote:https://<tenant>.sharepoint.com/sites/BetaTeam/Shared Documents/General/test beta notebook
- Teams = onenote:https://<tenant>.sharepoint.com/sites/BetaTeam/Shared Documents/General/test beta notebook|f|tdd7c600f-a1ed-4df3-bb90-eb4ae1258079
Post-Failure, OneNote lists the notebook
Interestingly, after failing, the OneNote file is listed in both versions of OneNote as an additional notebook to open – and will open successfully if you try to open it directly from OneNote’s list of additional notebooks.
@majani hello!
I think I managed to get a workaround by opening the notebook from the OneNote Windows 10 app.
I don't remember for sure though, sorry!
ps. MS support for OneNote isn't the best, unfortunately. They essentially ditched OneNote 2016 and moved to OneNote Windows 10, I have heard they are ditching this version again and making a completely new app! 