Many Microsoft engineering groups have a forum on the UserVoice platform to collect and respond to customer feedback. Signs that change is in the air came in a message posted by the Microsoft Information Protection (MIP) team in their Yammer community posted on March 3:

Due to recent policy updates within Microsoft across all products, [the] Microsoft Information Protection product group is discontinuing the usage of UserVoice and starting to use other methods to stay connected to customers and collect product feedback.

The team is committed to have an open channel to hear customers and stay connected, therefor we have updated the UserVoice link to route to a new form at: That in addition to a new link that will route to the same:”

True to their word, the MIP UserVoice forum is marked as not currently active (Figure 1).

User Voice for Microsoft Information Protection is silenced
Figure 1: UserVoice for Microsoft Information Protection is silenced

Corporate Edict

Since then, several Microsoft contacts have confirmed to me the move to dump UserVoice is a Microsoft corporate edict that affects all development groups. According to a Microsoft post in the MIP Yammer community, concerns about customer data protection requirements lie at the heart of the issue. I’ve also heard that the specter of GDPR has raised its head.

No doubt the axe will soon descend on Teams UserVoice, which I regard as a good example of how to have two-way customer interaction. Although they don’t always get it right, I know that the Teams development group have leveraged the feedback received through UserVoice to influence decisions about product directions. As of the time of writing, the Teams UserVoice forum remains open and active, with updates to product requests being posted this week (here’s an example about the availability of the Graph API for Presence).

Other popular Microsoft UserVoice Sites include To-Do, Word, and Planner. SharePoint has nine UserVoice sites while Outlook has six. The Office 365 and Office 365 Groups sites are marked as inactive (here’s a good list of feedback sites).

There’s no word as to when these sites will close, but I imagine that this won’t happen until the sponsoring development groups find suitable replacements. Hopefully, they’ll be able to migrate all the ideas, comments, and responses which exist in UserVoice to the replacement platforms.

March 8 Update: In a motherhood and apple pie statement, Microsoft published their position on moving from UserVoice. It’s a holding statement to acknowledge the passion about this topic expressed by many customers.

Customer Feedback is Critical

Any sensible person understands that bidirectional customer feedback is critical. Decisions made within Microsoft based on the knowledge, experience, and background of program managers are not always as well-rounded as those making the decisions think. Regretfully, listening to customers is not a skill some Microsoft engineers have acquired.

As Microsoft gets rid of UserVoice, it’s obvious that they need another platform to allow customer ideas and reactions to surface. To be fair, many development groups conduct extensive customer research and maintain sites where people can ask questions of engineers. The MIP group has its Yammer community, which is open to all. Other groups (but not many, and not consistently) use the Microsoft Technical Community. Others have Teams open to guest users from outside Microsoft. Many of the guests are MVPs, so they’re part of the Microsoft ecosystem anyway, but some are open to customers, especially those in Technology Adoption Programs.

What’s missing is a platform where anyone could bring an idea and ask the community to back the idea with their votes. UserVoice, for all its flaws, is such a platform. We can only hope that the replacement Microsoft choses is equally useful, and that the development groups continue to interact with customers and listen to their views.

Update: Read what an administrator of a 4,000 user Office 365 tenant thinks of Microsoft’s decision to shutter their UserVoice sites.

About the Author

Tony Redmond

Tony Redmond has written thousands of articles about Microsoft technology since 1996. He is the lead author for the Office 365 for IT Pros eBook, the only book covering Office 365 that is updated monthly to keep pace with change in the cloud. Apart from contributing to, Tony also writes at to support the development of the eBook. He has been a Microsoft MVP since 2004.


  1. Anna Kuzma

    I would understand if they would offer at least a basic similar functionality instead. But replacing Uservoice forums with some forms in nonsense.
    There are plenty of tools similar to Uservoice, there even self-hosted ones… I still don’t get this decision…

  2. Ali Salih

    Seems like the new platform is based on the “Dynamics 365 Customer Voice” — When you click on the MIP link, it is noted at the bottom.

  3. Pete Mitchell

    This looks more like an attempt to hide all the suggestions they’ve ignored over the years because their listening to feedback is just lip service. I’ve seen numerous good ideas that have a fair number of votes go ignored for years. Not a ‘no we can’t do that’, but just nothing.

    1. Nat

      I absolutely agree. Microsoft stands for Mediocrity.

  4. Andrew

    Well at least you still have a voice Tony 🙂

  5. Tim

    This is a major bummer. This was an easy destination to go to not just for me, but to tell users where to send feedback. I guess we’re back to only being able to express an opinion to the teams designing these projects if you’re one of the lucky few who is able to attend Ignite in person every 2 -3 years if we’re lucky.

  6. David

    So now they can ignore our feedback from a different site.

  7. Joel

    The Microsoft Stream group has a monthly Teams meeting called “Microsoft Stream customer connections office hours,” at which they make announcements, give updates, and field questions from IT professionals. It’s a fantastic way to share feedback. All of the M365 product groups should consider something like this.

Leave a Reply