First published on CloudBlogs on Mar 25, 2016
For well over a decade the enterprise client documentation team has tried to stay connected with you, our customers, through the SMSDocs feedback email address. The feedback we’ve received has made a tremendous impact and greatly helped the documentation teams tell the technical documentation story for SMS, System Center Configuration Manager, and now Microsoft Intune. The products we support, and the documentation that describes how to use them to solve your business problems, has changed over the years and now the way we request doc feedback is also changing.
The time has come to retire the smsdocs feedback email alias.
Of course, as you know, your comments and feedback about our product documentation are very important to us so we aren’t simply shutting down smsdocs, we’re also letting you know about the quickest way to provide that feedback about the docs via User Voice. You can post feedback about the documentation in the applicable User Voice category area:
Just like sending feedback to the old smsdocs alias, the writing team will not be able to answer technical questions at the User Voice link. However, if you leave comments about the documentation, a member of our team will review and respond to your message as soon as possible. As a reminder, for the most current documentation, see the following locations:
Another big change we’re working on is consolidating our social media efforts to make it easier for you to engage with us that way too. Rather than following ConfigMgr iX Twitter feed or liking our Facebook page, you will now be able to get documentation updates straight from our regular product Twitter feeds and blogs. The Configuration Manager team uses the
System Center Configuration Manager Team blog
to provide you with technical information and other news about Configuration Manager and related technologies. For similar information about Microsoft Intune, see the
Microsoft Intune blog
for supplemental information to the product documentation and support information.
Thanks again for your feedback and please continue to let your voice be heard! Please send us doc feedback via User Voice and stay connected on Twitter with
--The Enterprise Client Documentation Team