Forum Discussion
Jan_Steberl
Microsoft
MicrosoftNow in public preview: Future of wiki and Notes in Teams
Description
We are announcing that Wiki's will be retired from Teams starting January 2024. We are offering note taking capabilities within Teams channels using the included OneNote notebook provided for each team.
With this release, users have an option to export their wiki content to OneNote notebooks in Teams standard channel. After exporting users can go to the Notes tab to collaborate using OneNote in channels while Wiki is read only after export.
Why are we moving to a new note taking experience?
- This new functionality provides an improved note taking experience over Wiki. Some of the improvements are:
- Easy collaboration across the team
- View all channel notes in a team in one place organized within single notebook
- Rich editing with typing, ink annotations, highlighting, file attachments, etc.
- Easy recall & search for channel notes within OneNote
Plan to enable OneNote Notes in Teams channel and retire Wiki
- Users now have the option to export their Wiki content to OneNote Notebooks or they can continue to read/write their existing Wiki. Post export users can continue to collaborate in Notes tab in channels and have a copy of older Wiki content available for reference. When Wikis are exported each page in Wiki will appear as a page in OneNote Notebook section. Users can’t create new Wikis in new channel experience; for note taking we suggest using OneNote.
- For new channels Notes will be available as default tab soon. For now, user can create Notes tab manually using add a tab option.
We request you to try out the new Wiki export experience and share your feedback.
How to try out the experience
- In Teams, go to whatever channel has the wiki you want to export.
- In the Wiki tab, select Get details > Export to Notes > Finish.
- Go to the Notes tab to access your content.
Read more about the change here - Export a wiki to a OneNote notebook - Microsoft Support
Flighting status
Available in public preview
How to enable
This config change is available to everyone.
Supported clients and platforms
|
Windows |
macOS |
iOS |
Android |
Linux |
Chrome |
Firefox |
Safari |
Edge |
|
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
How does this feature impact the existing experience?
Users can continue to access their Wiki as is, no change in existing content until general availability when Wiki content will retire.
Known issues
None
Known limitations
- Post export users may see some formatting change and dark mode is not supported
- Export is only supported from standard channels, from Private channels user need to manually copy & move content.
Enable your Teams client for the public preview
- First, IT admins need to set an update policy that turns on Show preview features. Learn how at Public preview in Microsoft Teams - Microsoft Teams | Microsoft Docs.
- Users then choose to join the public preview individually. See Get early access to new Teams features - Office Support (microsoft.com) for instructions.
Send us your feedback
Got feedback on features in the public preview or other areas of Teams? Let us know straight from Teams via Help > Give feedback. This is on the bottom left of the your client.
Thank you,
Preview Team
Quality & Customer Obsession, Microsoft Teams
Jan_Steberl please reconsider this change. One Note doesn't load quickly, isn't searchable, and has constant problems syncing. It is not made for a reference guide, which many of us use wiki for. I know this change will not work for us, because our reference guide was in One Note before we moved it to the Wiki, which was a much better experience for our front end team that needs quick answers. Surely, it cannot take vast resources to maintain the wiki. Or at least develop a REAL replacement product.
I guess I'll format a Word document- at least it's searchable and navigable with headings/subheadings, but yikes. What a mess.
- Thanks for your answer, I fully agree, but I often have problems with word, because it takes much longer to load. So, keep wiki, that would be the best!
- !!! PLEASE KEEP THE WIKI !!!
I have tried for months to find alternatives but there is nothing that's as seamlessly integrated, efficient, to-the-point, and robust (and free) as Wiki.
Migrating to OneNote is evidently not an option we're able to even consider. We migrated one Team to OneNote and it's been a complete disaster and disruption to team communications.
!!!! PLEEEEEASE !!! I BEG YOU TO KEEP THE WIKI. FFFFFFFFFFFF - Wiki was simple, worked well as an overview for my teaching. All the other stuff is much more complicate. Simplicity is the new smart! Or am I too complicated?
- Searching OneNote books from Sharepoint Online is basically broken. Search is one of the main entry points into a wiki, so this implementation is currently unusable from within Sharepoint Online. The only workaround is to open the book from the Windows client.
Wiki was great - fast, intuitive, and easy to access and share, I tried using Notes today and it was awful.
For my organization, WIKI was one of the main drivers to use Microsoft Teams, please reconsider it
- Just exported our knowledge base from WIKI to NOTES. What a cluster! Lost all the bookmarks that take me to each support topic in my WIKI page. This will be unusable going forward in NOTES. Time to see what SLACK offers. Heck, DISCORD may be an option at this point. Fail.
- Does anyone have an alternative for Wiki? Notes is wholly unusable as an alternative and our workflow and collaboration is suffering due to this irreversible "preview".
Anthony-123 I moved our wiki to a SharePoint site, it was the only thing that worked fast enough, the OneNote was a massive fail and wouldn't update in teams correctly.
Jan_Steberl Whereas, we used to have a great tabbed list of over 50 entries now we have to scroll around in Notes to find what we are looking for. Terrible.
Hi Jan,
This is a hurtful change for my teams. We use wiki to display formatted static information, we use them like user manuals. We don't update these process documents often.
We use notes as a flexible tool to capture meeting information and information. Now that we have to use notes for both, we have a system revision on our hands to keep things organized.I wish MS Teams Channels still supported wiki.
Losing features like this makes fully embracing Microsoft Teams difficult, as we must revise established business processes at the whims of a general software provider.
How do you consider this negative impact to the user experience when deciding to reduce feature support?
- I really hope you guys listen to your users and please DO NOT GET RID OR THE WIKI!
This is a terrible idea!
