Skip to main content
SolutionsTeams
  • Home
  • Guides
  • Topics
  • Articles
  • About
  • Contact

Feedback

Corrections & Feedback

Something wrong, missing, or outdated? Here is how to tell us — and what happens after you do.

Last updated: November 2, 2026

What we want to hear about

  • Inaccurate instructions — a step that doesn’t match how the platform actually behaves, or a claim about roles, settings, or defaults that is wrong.
  • Outdated content — a guide that no longer matches the current version of a platform it references.
  • Broken links — internal links that lead nowhere, or external links that no longer resolve.
  • Missing context — a guide that answers your question only halfway, or skips a prerequisite it should have mentioned.
  • Clarity problems — sections that are confusing, jargon that goes unexplained, or steps that can be read two ways.
  • Suggestions — topics we should cover, or ways the site could be more useful.

How to report

Call us at +1 509-607-7777. To make the report as useful as possible:

  1. Have the article title or web address ready — the exact page you’re reading.
  2. Say what you expected and what happened — or what the guide claims versus what your platform does.
  3. Mention your platform and edition where relevant, since behavior often differs between products and plans.

Written reports can be sent by postal mail to 312 3rd Ave SE, Soap Lake, WA 98851, United States — the same details apply, and we process them the same way, though they take longer to reach us.

What happens next

  1. We verify the report against the platform’s official documentation — the same standard our guides are written to, described on the Editorial Standards page.
  2. If confirmed, we correct the article and update its visible “Updated” date. Material corrections change the substance of what the page says; small fixes may land without fanfare, but everything is dated.
  3. If the report is version-specific — true in your environment, not universal — we add the necessary qualification instead of a blanket correction, so the guide stays honest for both cases.
  4. If we disagree, the bar is the documentation, not opinion: we’ll tell you what we found and why we left the text as is.

Why reports matter to us

Collaboration platforms change constantly, and no publication — ours included — catches every shift on its own. Readers who report discrepancies are doing the most valuable work on this site: keeping the library trustworthy for the next person who reads it. We’d rather hear about a problem ten times than zero times, and a correction call is always welcome.

SolutionsTeams

Independent educational guides for workplace collaboration technology — written for the people who keep digital workspaces organized.

Explore

  • Home
  • Guides
  • Topics
  • Articles

About

  • About SolutionsTeams
  • Editorial Standards
  • Corrections
  • Contact

Legal

  • Privacy Policy
  • Terms and Conditions
  • Disclaimer

Contact

+1 509-607-7777
312 3rd Ave SE
Soap Lake, WA 98851
United States

SolutionsTeams is an independent educational publication. It is not affiliated with, endorsed by, or officially operated by Microsoft. Third-party product names and trademarks belong to their respective owners.

© 2026 SolutionsTeams. Photography by Unsplash contributors, used under the Unsplash License.