Each month, the contributions are scored by a panel of judges (5 per category, 2-3 in each are MS experts), and the winners of each category are showered with love and attention from all corners of TechNet.

See the links at the bottom, to find out more about the competition and how to enter.

We have picked the top three highest scored contributions for each category to bestow our awards upon.

The awards are in gold, silver and bronze, the gold obviously being the top winner of the category.

The last column is just a few of the comments judges made during the judging process.

In some cases, we have not obtained permission to use the judges names, so they have been reduced to initials.

My fellow wiki ninjas will be digging deeper into some of these articles in this blog series, so watch out for those.

Any of our judges can exercise their right to veto an article, if they do not feel it meets minimum requirements for a medal.

When this is the case, we will at least give an indication of the reason, so you understand why.

A big thank you also to the other authors who did not make the top three of each category.

Some articles only just missed out, so we may be returning to discuss those too, in future blogs.

Ronen Ariely (aka pituach): "Nice article. It can be very useful. The topic is interesting but I get a feeling like it is a bit short. I noticed that it's missing a closer. Any Technical article must have an opening -> body -> and a closer like conclusions or summery for example. But as I said the topic can be useful for daily work and it might be good idea to save the article in the favorite. Well done!"

Ronen Ariely (aka pituach): "Great article which bring nice solution for real life scenario. Pretty sure it can be useful for many readers. The article is well written and well formatted, but there is a really tiny tiny issue with the Table Of Content. The TOC includes titles like "Step 1", "Step 2", "Step 3".... which give no value to the reader, since there is no information about what we have in each step."Rajat Jaiswal: "Thanks!"

Rajat Jaiswal: "very well explained."Ronen Ariely (aka pituach): "The article was written by a new author which succeed to present High quality article which is well formatted and well presented. Well Done! There is still work to be done. In SQL 2019 there is new option Always Encrypted with secure enclaves, which must be mentioned in article which is publish now. unfortunately, there is article about this topic in the TN Wiki, and this is duplicate article."

Eric Berg: "good writeup. Thank you"Adam Fowler: "Great clear screenshots, great for anyone to follow this guide."Joseph Moody: "Excellent article and very useful!!"Kia Zhi Tang: "Thank you for a good screenshot walkthrough."MA: "The post is well structured and organized, the steps and screenshots are neat."

Rajat Jaiswal: "crisp and clear.Nice job."J.J: "Thanks Av, very useful."Ronen Ariely (aka pituach): "Nice article, but it is missing a closer section and the 'See Also' section is empty despite the fact that there are many articles in the system related to the topic. With a bit more work on the article format and adding a bit more text this can become a great article. Thanks Av for sharing. This can helpful post"

Rajat Jaiswal: "It can be more expressive."J.J: "Very nice!"Ronen Ariely (aka pituach): "Thanks for sharing. The post include code which represent a solution for a problem. There should be a lot more text which explain the scenario and the solution. What is the scenario? what do you present in the content? Introduction and closer sections are highly important."

Rajat Jaiswal: "It would be great if you add a few more example like format file etc."J.J: "Thanks!"Ronen Ariely (aka pituach): "Thanks for sharing. I am not sure if this post can be classified as an article. It brings images and code without any explanation. An article can be about a code or a solution but the code is not the article. In addition there is no closer or "see also" sections. This might better fit for the TechNet gallery which is best place for posting code samples. As article a lot of text is missing."