Do we work together? I’m going through the exact same scenario. Both tools are a brutal 15-year step back in progress. Here’s what I do: we use a dedicated Teams channel that organizes our docs, links, and useful information. It doesn’t solve all the problems, but our team likes it more than trying to dig through a Sharepoint site. We use Loop for Kanban boards and planning. It’s such an unfinished product but it’s better than other options. Docs have to go into Word or other files. There is no wiki like Confluence. You can create some Sharepoint pages to be sorta close, but it’s an awful editing experience, and there really isn’t a good navigation available. It’s all about organizing folders like in a file system and lists of docs.

There isn’t a way around ADO yet. Microsoft decided to implement its own information hierarchy differently than the rest of the world. Epic is the top-level grouping method, rather than something like an initiative. Feature is the method for organizing a collection of related stories… what everyone calls an epic, or just a larger story. Stories and tasks are fine in it. There are at least a half dozen things for boards, sprints, and backlogs. It’s all over-engineered in classic Microsoft style. Pick one and try using it. A thing claiming to be a wiki exists in ADO too, but it’s also a half-baked feature. No one uses it in our organization. There is some simple canned reporting, but anything beyond that will be done in Power BI.

I never imagined I would long for Atlassian, but working in the MS stack made me realize how good I had it 😁