House rules for comments on the Azure Information Protection documentation

Applies to: Azure Information Protection, Office 365

If you have feedback about the documentation you've just read for Azure Information Protection, we would love to hear from you. For example, if you have a clarifying question about the information documented, want to report an inaccuracy in the documentation, or can’t find the information that you need.

Before you post your comment, make sure that it's relevant to the page where you are posting. These posts are public and visible to everybody. If your post is not relevant or it is outside the scope of our house rules (see below), expect it to be deleted.

Livefyre comments and sidenotes should not be used for the following:

  • Technical support. For example, a feature isn’t working after checking any requirements and following the documentation instructions, or you have a question about licensing. Instead, use your standard support channels or contact Microsoft Support.

  • Roadmap information. For example, when a new release will be available or additional functionality is planned. For this information, visit the Enterprise Mobility and Security Blog or if it is critical to your deployment, email askipteam.

  • Product feedback. For example, suggestions for product improvements or a new feature. Instead, visit the Yammer site for Information Protection to engage with the engineering team.

  • Documentation design feedback. For example, you want to report a problem or request a few feature for all documentation pages on the docs.microsoft.com site. Instead, visit our feedback site to post your suggestion or vote on other suggestions. You might also find it useful to read Introducing docs.microsoft.com to learn more about the site design and new features.

You’ll find additional resources in Information and support for Azure Information Protection.

Note: If you are a Microsoft employee, please use internal communication channels.