Occasional Contributor


We're using Microsoft teams with a small IT team and started using the Wiki tab intensely.
But after a while people stopped using it because the experience wasn't that.

I'm not talking about markup, etc... it's great the latest update brought tables to wiki's but we're talking about restoring data (when somebody accidentally deleted a part), searching for stuff, easy sharing, printing and more...

I thought it was really nice have a wiki within each team it makes searching so much easier.



13 Replies
Just to add to this, wiki on mobile is a missing capability

On this note, I'd love to hear the reasoning behind providing a second wiki in Office 365. SharePoint wiki is okay, but not anywhere near the quality I get with MediaWiki. Why build a completely new wiki platform (that still lives quietly in SharePoint) instead of improving on the SharePoint one to a level many wiki fanatics expect, then simply embed it into Teams like you do with Files/SharePoint?


More curious on the business case and justification to provide a competitive product rather than improving an existing one that could use some love.

Hey Jelle, thanks for trying out our Wiki experience, we're working in conjunction with SharePoint to improve this experience. Hope to win you back soon!
Completely agree with this. Why create a new option that actually adds confusion?

Another way to say this is: give us one GOOD option and integrate across the board.
I was trying on my diplomatic hat for size. XD

I say acquire/license MediaWiki! It's the wiki everyone knows and expects!
@Matt Wade we currently don't want to add another thing to maintain and back-up (MediaWiki). I wasn't aware that sharepoint wiki and teams wiki were not the same product since the data is stored in sharepoint I tought it was the same. Choose one, make it awesome and integrate that one in teams as a tab/connector!

Yeah, they're completely different products. The Teams wiki does live in SharePoint, but it's basically invisible and it's just data. The interface is only in Teams.

SharePoint's 'Enterprise Wiki' is all but dead, it was always too poor in functionality. The SharePoint roadmap from Ignite talks about adding more 'wiki like' features to the page authoring experience in the second half of 2018, lets hope it's something that people like, here we have Atlassian Confluence and I would very much like to displace it.

Okay, but the problem is SharePoint wiki >> Teams wiki in both functionality and UI. They can stop improving SharePoint's wiki and it will still take a good amount of time for Teams' wiki to catch up. Plus, you can always add a wiki from your Team's SP Group site as a web page in a Teams tab if you need a wiki. Point is: why two wikis when one is reasonably good?
Really surprised to hear you like the SharePoint Enterprise Wiki, my users absolutely loathed it. Anyway, I think the roadmap is clear enough, the new SharePoint modern pages will add more wifi features later next year, and that will the strategic future wiki.
Teams wiki is a stopgap in the meantime for people who want something in the context of their team.

Easy killer, I never said I liked it. I said "it's okay" and "it's better than the Teams wiki". That's not high praise when I'm a regular user of MediaWiki wikis elsewhere. :D

My point is: why do we need a stopgap? You can add a wiki from SharePoint (even MediaWiki if you want to!) in a web page tab in Teams. There's no big void there, and even if there was, wikis aren't that popular that it absolutely needs a stopgap created.


In fact, the Group's default OneNote notebook that used to be included as a tab automatically was specifically replaced with the wiki. OneNote >>>>> Teams wiki (and by the transitive property of many >'s, OneNote >>> SP wiki too), but it was removed and users have to know enough to re-add it.


There are plenty of bigger voids in Teams that could have used a stopgap. Hell, those resources could have been spent on private channels or external access, two major features that likely anybody could have predicted when Teams was under construction.

That's why I asked originally: what was the driving force for adding this wiki? And why replace OneNote's tab? I'm genuinely curious.

I am completely mystified by "Teams Wiki". It's missing even the most basic, defining features of Wiki's - there's no markup to make a link to a new page. Why are they calling it a Wiki at all? And why on earth are they creating a "new" Wiki, when there's already a Wiki module in Sharepoint - it's not great, but it's better than this new one. And why not use MediaWiki - it's worlds better, and free!

i've all but given up on Knowledge Managment within O365.


I am starting to explore non-Microsoft tools like Notion.


Sad state of affairs.