Forum Discussion
Microsoft Teams News: Wiki Page Retiring in January 2024 & There Are Things You Must Do
Before saying "Peace Out" to Wiki Page in January 2024, you must do some things.
This in-depth video discusses what to expect, Microsoft's timelines, and a guide to completing the transition.
Now, you can work your magic - efficiently!
- Video Date January 20: Peace Out https://youtu.be/y7BtR9NlMyE
- Updated Video February 27: Revised Timelines https://youtu.be/seXrZ5awhGs
- Date: 3/21/2023: Download Wiki from SharePoint https://youtu.be/9BKk2zh1y84
If you want a backup of your Wiki Pages, this video shows you how to download Teams Wiki Pages from SharePoint to your local drive. Once the files are downloaded, then open the Wiki files in Microsoft Word. Note: This process should NOT replace Microsoft's requirement to export Wiki Page to OneNote.
Date: 4/30/2023: https://youtu.be/4ugFh6sLcP8
Tips and insights on Exporting Teams Wiki to OneNote
5/14/2023 "Perfect Wiki for Teams" App: A Microsoft Teams Wiki Alternative
Video: https://youtu.be/jSk6SQRN4sk
In this thread, several users were searching for an alternative wiki app. I conducted a review on the "Perfect Wiki for Teams" app. It is a great app! Check out the video.
/Teresa
#traccreations4e
REVISED: Regarding the Wiki Libraries in SharePoint, the wiki pages will remain on SharePoint. However, the Wiki Page and App are not available in January 2024.
I created a video on exporting the Wiki libraries content to a zip file and opening the pages into a Word file as a BACKUP. It will be available later this week. I will update this post with the link when it is available.
Stay tuned.
/Teresa
#traccreations4e
Thanks for starting this informative blog Teresa_Cyrus!
I may be stating the obvious but wanted to maybe give a couple of discovery pointers to anyone that may need them. I am an admin and did not want to rely on users to complete the discovery work. I had a total of 112 sites with teams and was able to get through these discovery steps over the course of 3 days while still completing other duties.
Start with producing a SharePoint list of Sites with Teams in the SharePoint admin center.
Download it and use it to document what you find/do.
For each Team:
- In the Teams admin center add yourself to the team and to any private channels
- Check the tabs for Wiki content. Don't just check the tab labeled Wiki as the tab may have been renamed.
- If the tab is a Wiki and it's empty, remove it.
- Check every Channel's tabs. Make sure you expand any hidden channels too.
- Optional steps: Open the site in SharePoint. Private channels create their own Sites so make sure you open them too.
- Navigate to and open Site Contents.
- Open library 'Teams Wiki Data'.
- Check under each folder for content.
- Delete empty folders or if there is only 1 or 2 'untitled' .mht files.
- If nothing is found of value, delete the Library 'Teams Wiki Data'.
- It's important to note that I did find folders in the Library that didn't have a folder by the same name as channels for the team with content. I suspect these were from channels that were removed. You may want to keep this content.
- In your SharePoint spreadsheet, make a note for what you did and if there are any Wiki's present to migrate.
- Remove yourself from the Team.
Does anyone know how to exclude the Wiki App from being used in Teams? I would love to not allow anyone to add a Wiki now that I completed my research to find all the Wikis!
I did a little test too for new sites getting created.
When you create a New Teams SharePoint site and add a Team or create a new Team in Teams, the Wiki tab was not included and the library 'Teams Wiki Data' was not created. That was a relief! I hope that experience is the same for everyone.
Hope this helps folks to prepare for the next steps!
Good content. On average, how many channels per Team Site did you have?
I also did a little digging and found nothing on how to disable the Wiki App. It has been a hot topic in the past.
Most had 1 channel but I would have to say 2 channels per team if you are looking at an average. We also utilize private channels and that does create a separate SharePoint site.
I took some time yesterday and wrote the following simple PowerShell script to identify the team, channel, and tab name where the wiki app is being used. It matches my manual results so I am confident it reports correctly. This script doesn't alter anything and it does not have a bunch of bells and whistles. I hope it helps those that can use PowerShell:
#Set Connection Variables $Tenant = 'your tenant' $ClientId = 'your client id GUID' $TenantId = 'your tenant id GUID' $Thumbprint = 'your certificate thumbprint' #Import and Connect to Necessary Modules Import-Module -Name Microsoft.Online.SharePoint.PowerShell Connect-SPOService -Url "https://$($Tenant)-admin.sharepoint.com/" Import-Module -Name Microsoft.Graph.Teams Connect-MgGraph -ClientID $($ClientId) -TenantId $($TenantId) -CertificateThumbprint $($Thumbprint) #Setup the object and container Items $properties = @{Team=''; Archived=''; Channel=''; ChannelType=''; Tab=''; App=''} $objectTemplate = New-Object -TypeName PSObject -Property $properties $Items = @() #Get all SharePoint Sites with a Team Connected and Sort on Title $Teams = @(Get-SPOSite -IncludePersonalSite:$False |Where IsTeamsConnected -eq $True |Sort Title) #Process Each Team ForEach ($T in $Teams) { $Team = Get-MgTeam -TeamId $($T.GroupId) $Channels = @(Get-MgTeamChannel -TeamId $($T.GroupId) |Sort DisplayName) #Process Each Channel in the Team ForEach ($C in $Channels) { $Tabs = @(Get-MgTeamChannelTab -TeamId $($T.GroupId) -ChannelId $($C.Id) -ExpandProperty TeamsApp |Sort DisplayName) #Process Each Tab in Each Channel in the Team ForEach ($TA in $Tabs) { #Only output an item where the App for the Tab is 'Wiki' If ($($TA.TeamsApp.DisplayName) -eq 'Wiki') { $objectCurrent = $objectTemplate.PSObject.Copy() $objectCurrent.Team = $($Team.DisplayName) $objectCurrent.Archived = $($Team.IsArchived) $objectCurrent.Channel = $($C.DisplayName) $objectCurrent.ChannelType = $($C.MembershipType) $objectCurrent.Tab = $($TA.DisplayName) $objectCurrent.App = $($TA.TeamsApp.DisplayName) $Items += $ObjectCurrent } } } } #Print the Results to the screen $Items |Select Team, Archived, Channel, ChannelType, Tab, App |Format-Table #Export Results to a CSV File $Items |Select Team, Archived, Channel, ChannelType, Tab, App |Export-Csv -Path $Home\TeamsWithWikiApp.csv #Disconnect from SPOService and MgGraph Disconnect-SPOService Disconnect-MgGraph
Today the message 'Wiki tabs in channels will go away starting in June 2023. You can export your content to a new Notes tab that will be created for this channel.' with a 'get details' button. After clicking that button you have the option to 'Export to Notes'. Here is some information I will pass along as it's NOT how I wanted my Wiki converted to Notes. For those that maybe didn't realize this and it's important to understand because they are opposite each other....
WIKIs have multiple pages with multiple sections in the page
OneNote has multiple sections with multiple pages in the sectionHere's what the exported result was for me:
A site OneNote is created or if already existed it is updated
Each channel Wiki becomes a OneNote Section by the channel name, 'General' for example
Each Wiki page becomes a OneNote page in the OneNote Section
All of the Wiki Sections are inserted 1 after the other in the OneNote page
This may be the desired result, it was not for me. I wanted each channel's content only available in that channel.
My expectation was that a OneNote would be created for each Channel.
Each Wiki page would become a OneNote Section.
Each Wiki section in the page would become a OneNote page in the OneNote Section.
Probably not the best illustration but hopefully it helps to understand what happens.
If my Team and Wikis are like the following before exporting:
They end up like this after exporting:
My links to exported wiki pages/sections were lost. You will need to add those back.
Other links seem to be fine.
Pictures transferred.
It's time consuming but I am splitting out my information into separate OneNotes (1 per channel) recreating the original structure of the Wiki. Reply if you want information on how to do the splitting and I will do my best to describe it.
I also noticed that any conversations that were on the right side of the Wiki page for the entries don't get exported. After the export the Wiki page becomes read only. So you also don't have access to the conversations anymore. Any links or documents in those conversations are then gone. Is there anyway to access this again?
Don't like the structure it becomes in OneNote. Everything is just on one page. The numbering for the content headlines is lost. There is no space or page breaks between the sections. So a lot of edit effort needed to get it back into a readable format.
I think your best bet to get the links back or at least get an idea of where they pointed to would be to download and open in word like @teresa_cyrus describes in this video: https://youtu.be/9BKk2zh1y84.
Keep in mind though once you convert the wiki ALL links to it change because it's not the same or retained.
- Thank you for sharing this valuable information.
- Hi Teresa
Thx for a great post!
Many of my users are having trouble with exporting their Wikis to OneNote. They get this error:
Export didn't complete.
Looks like something went wrong, and you'll need to restart the export. If the problem persists, contact your IT admin for help.
*************************
We have tested Teams version, Teams for Web, Started an app for OneNote, Cleared cache, checked the permissions and settings in the Teams - without results.
Have you, or anyone else in this thread heard of a solution for this? My suspicion is that's an error on some old Teams. We started up with Teams back in 2017'ish.
Thanks in advance for your answer.
Br. Linda Gärtner Nielsen
- Thank you for the information.
With Regards,
Satish U - Hey, how about wiki pages libraries in SharePoint, are they also being retired?
Cheers
JoergREVISED: Regarding the Wiki Libraries in SharePoint, the wiki pages will remain on SharePoint. However, the Wiki Page and App are not available in January 2024.
I created a video on exporting the Wiki libraries content to a zip file and opening the pages into a Word file as a BACKUP. It will be available later this week. I will update this post with the link when it is available.
Stay tuned.
/Teresa
#traccreations4e
Thank you so much for this! Here is the one thing I can't figure out...any help would be greatly appreciated.
- My problem is that the yellow banner to export to OneNote only appears when I am using Public Preview (EA). We don't allow public preview for most of our users so they cannot perform the export operation
- Also, I recall hearing that as it stands right now, users shouldn't be able to create NEW wiki tabs. However, even if I'm on public preview, I can STILL create new wiki tabs.
- Yes, I get the warning but I can still create new wiki tabs in the standard version of Teams
- I am version 1.6.00.8767
_J-K_ SharePoint Wiki Libraries are not covered by this announcement, and there have not been any other announcements about them.
Hi Teresa,
Would you mind to share the original document that talks about this? Thanks.
Regards,
DracoDracoLLSS / StevenC365 / _J-K_
Guys, the data will remain on SharePoint but the Wiki Page and App are not available effective Jan 2024. MS also mentioned, users can download files from SharePoint. FYI: I had tested it. I was able to bulk export per channel the Wiki Libraries' content to a zip file and open the wiki page files in Word Doc. One concerned area; it is not intuitive where the images were placed on the pages. (I hope this helps. By the way, if you need help with converting wiki pages, inbox me.)
Here is the MS Post date Feb 21.
Updated February 17, 2023: Based on customer feedback we have updated the content with FAQs. Thank you for your feedback.
We are announcing that Wiki's will be retired from Teams. We are offering note taking capabilities through Teams Channels powered by OneNote.
When this will happen:
The following change will be rolled out starting early March.
How this affects your organization:
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.
Upcoming plans
Soon Notes tabs powered by OneNote will be added by default when users create new channels. For now, users can create OneNote tabs manually using the add tab experience (via +).
We will share out the details of Wiki retirement in advance to help our customers prepare for this change.
What you can do to prepare:
We urge users to export their channel wikis to OneNote once it is available.
If your organization has not enabled OneNote you can review this documentation:
FAQs:
Why is Teams retiring wiki?
- Our users’ needs for note taking are evolving every day and the current capabilities & infrastructure of Wiki will not be able to cater to those needs in future. We understand that moving away from wiki is a difficult change and we want to help our users throughout the changes.
How can I take notes in channels after this change?
- New channels will now come with a OneNote notebook (M365 brand for note taking). OneNote brings goodness of richer formatting, better organization, search within OneNote app and keeps the experience consistent across M365.
When & how are we retiring Wiki?
- Stage 1 – (Timeline – early March 2023) Users won't be able to create new wikis, but they can continue to access (read/write) their existing wiki. Users also have the option to export their content to OneNote. Once users export their content to OneNote, the Wiki is available as read only.
- After exporting, each wiki in a channel appears as separate section in OneNote and each Wiki page will be a separate page in OneNote.
- Stage 2 – (Timeline – Mid CY23) Wiki tab in channel will not be supported; users will be easily able access (read/write) content in Wiki app. Users can also export their content to OneNote.
- Stage 3 – (Timeline – Jan 2024) Wikis tab and wiki App wouldn't be able to accessible in Teams and users wouldn't be able to export. Users can download their wiki files from SharePoint.
What happens to my existing data?
- Your data is accessible from SharePoint as per retention policy even after Wiki is deprecated. You can download wiki content from SharePoint.
Does end user need to export wiki one by one or in bulk?
- End users will have to export wikis one by one per Wiki tab. If there are more than wiki tabs in a channel, then users will have to export them separately. Users can export their wiki by visiting Wiki tab.
Who can export Wiki to Notes?
- Any team member who has access to add/remove tab in a channel can export their Wiki.
Is there a bulk export option available at tenant level?
- No, users can export their wikis as per their convenience.
Known limitation:
- OneNote notes only work in Default (Light) and High contrast mode.
- Thanks. Teresa
Hello,
I'm working on this subject for my company, I understand what is the "wiki tab" in the Teams client, but what is the "wiki app" ?Because when I read the different stages of the retirement , for "stage 2" i understand the main difference is that wiki tab will be unavailable, while wiki app will not .
Or maybe I understood wrongly, as english is not my primary language (i'm french)
Thank for any additionnal information
ogouret
Same Q here:
Is that (in english version) the "tab" (german: "Registerkarte")?...und this the "app"?
While in Teams, the Wiki App will not be listed when you select + then choose from a list of Apps.
Hi Teresa_Cyrus
Do you know if the links from 1 wiki section to another convert properly or do these need to be corrected too?
I still don't see the option to migrate to Teams Wiki to OneNote. Getting a little nervous that it's not there yet!
Hi KathyROI
A lot of folks are anxious to get started with converting to OneNote. I checked the message center, MS has not posted any updates since Mar 17th. I wonder if we will see the banner by the second week of April.
Obviously, I have not tested with the actual exporting tool. However, I suspect the links will carry over with a problem. As soon as the exporting tool is available - trust and believe - I will complete a thorough test again. 😁
Thank you for your inquiry about the links. It prompted me to test the other attributes on the Wiki Page. Here are my learnings with exporting Wiki Pages from SharePoint to a zip file and then opening with MS Word.
On Teams Wiki Page, I created:- internal links within & outside of a channel
- MS Word retained the links
- external links
- MS Word retained the links
- Used the following attributes: strikethrough, yellow highlighter, red and bold font, quote and inserted a table.
- MS Word did not keep the yellow highlighter or the color font; everything else was fine.
I encourage you to watch the Download from SharePoint video. I share my concerns about the images. The link is in the original post above.
MS Word Results
If find this information helpful, please like it which will assist others with the same question.
/Teresa
#traccreations4e
Teresa_Cyrus - for the record, and I'm hoping this has been said... I do not use Wiki for "notes," and Teams' OneNote functionality is clunky and cumbersome. I use the Wiki for FAQs. Is there a comparable product that is as easy to use with Teams? Thank you!
- internal links within & outside of a channel
- As a heavy markdown user in both Teams messages, and in channel Wikis, I'm concerned that we may be losing this feature when Wikis go away. I do see all the usual options available in OneNote, so perhaps there is a way to use just the keyboard to do the common tasks, such as mark a word as code, or a sentence as a quote.
- The messages are absolutly proper. The first just warns or suggest to start over elsewhere. For Not-PP Users.
For PP-Users the wizard can be used, more or less for test reasons.
Just tell your clients to wait for June, when the wizards comes up regularly. Dont let them into the PP, cos they would unnecessarily turn on Teams2.0 😞
Thans kevin. Cos we now know from your screeni (the german one is different) that the feature for the 99% of users just starting even in Phase 1 not in March, not in April, not in May (oh boy). In June 🙂- Ah Teresa: If June is right, MS should clarify whats "summer" (Phase 2) means. July would be a panic maker, August would be ok. Agree?
Hi Teresa_Cyrus ,
I'm in Australia and haven't seen any banners or received notification that Wikis are going to be retired! All of my business' manuals are kept in Teams Wiki 😬. Wondering why some are receiving banners advising of retirement, and others aren't? Am I missing something?!
Thanks you!
Please check with your IT Administrator. The retirement announcement was posted in the Admin Center Message Center.
Also, I have had several GCC users sharing that they have not received the message or banner notices. I am not sure which region they were in. So, thank you for sharing your region.
MS "usually" roll out features and updates in a regional phase, but I am not absolutely sure why you have not received the notification. Please keep me and others in this thread informed.
If you find this information helpful, please like this post. Thank you in advance.
/Teresa
#traccreations4e
Teresa_Cyrus
I finally have the message, but its translation in french is quite different from what I understood from the roadmap , it says "Wiki tabs in channels will disappear starting june 2023. You can export your content to a new OneNote tab that will be created in this channel."
According to the roadmap I understood they would disappear only in january 2024 !
Are we sure that our users must migrate all their wiki tabs at the end of june , in 2 months ?I have also noticed an issue : the message doesn't appear in the "Wiki App", is it normal ?
I checked the Message Center in the Admin Center today and Microsoft's last update was March 17th. In my post early in this thread on March 14th, the only change was the rolling out date from early March to late March.
In response to your question, my Wiki Page banner also states:
"Wiki tabs in channels will go away starting June 2023. You can export your content to a new Notes tab that will be created for this channel."It appears to me (as a non-MS employee) that MS forgot to change the date to January 2024. Also, MS mentioned that the Wiki Page will be unsupported starting June 2023.
I will also add that a Microsoft Team Member has marked one of my posts as the best answer where I had referenced the January 2024 retirement date.
I agree that the communications are confusing. If you find this information helpful, please like this post. Thank you in advance.
/Teresa#traccreations4e
- I also saw that MS mentioned that the Wiki Page will be unsupported starting June 2023, the important thing to know is what "unsupported" exactly means ...
