You have probably already been in a situation where you needed to get something done and were blocked: How does this work? How am I supposed to configured this? Where do I find the right information? Technologies such as FIM are no "learning by doing" technologies. Without at least some basic knowledge about the system, an attempt to get something meaningful deployed will very likely fail. To address this issue, you can use the FIM Documentation Technical Library on TechNet. What should I do? While we have already developed a lot technical content for many FIM related areas, there is always a chance that: A specific document is missing An existing document is incomplete or contains errors The good think is, YOU can have a significant impact on getting these issues resolved by providing feedback on this forum. How? By opening a Suggestion Box post to track your feedback. Tracking your feedback in a separate post is a great first start. This gives other community members an opportunity add additional comments. How should I do it? The next step is to put actionable information into your post. I have seen comments such as "is light", "not enough", etc. While adjectives such as light, thin or skinny might very well express your current feelings, this is not really helpful when trying to address your feedback. Basically, the more details you provide, the better. At a minimum, your feedback should include the following items: The name of the document and a link to it - if your feedback is about an existing document. In case of an existing document, you should include the name into the title of your post The type of the document (e.g.: conceptual, technical reference, step-by-step) and a suggestion for a name You can use the current content of the FIM Technical Library as reference The scenario you are working on A scenario is not "I need to configure the object deletion rule" - a scenario is more something like "I need to synchronize HR user objects to Active Directory Domain Service and need to handle deletions". In other words, the scenario description should not include specific features - unless, this is not avoidable. While the article was not written to provide instructions for providing documentation related feedback, I highly recommend Peter Geelen's article on How to get the maximum return on your forum question. What applies to forum questions does also apply to documentation feedback. What else can I do? Instead of waiting for documentation to be developed by us, why not developing it? There are lots of options for you to participate in the development process. Please see How to become a FIMster for more details. Markus Vilcinskas, Knowledge Engineer, Microsoft Corporation