Update format

Author: Gijsreyn

docs/troubleshooting/troubleshooting.md

@@ -0,0 +1,88 @@
+---
+title: 'Known issues: Microsoft Desired State Configuration'
+description: "[Article description]."
+author: [your GitHub alias]
+ms.author: [your Microsoft alias or a team alias]
+ms.service: [the approved service name]
+ms.topic: troubleshooting-known-issue #Don't change.
+ms.date: [mm/dd/yyyy]
+
+#customer intent: As a <role>, I want <what> so that <why>.
+
+---
+
+<!-- --------------------------------------
+
+- Use this template with pattern instructions for:
+
+Known Issues
+
+- Before you sign off or merge:
+
+Remove all comments except the customer intent.
+
+-->
+
+# Known issues: Microsoft Desired State Configuration
+
+<!-- Required: Article headline - H1
+
+Identify the product or service the article
+applies to.
+
+-->
+
+[Introduce and explain the purpose of the article.]
+
+<!-- Required: Introductory paragraphs (no heading)
+
+Write a brief introduction that can help the user
+determine whether the article is relevant for them 
+and to describe the specific issue that the article
+covers.
+
+-->
+
+## [Issue]
+
+<!-- Required: Issue - H2
+
+Each known issue should be in its own section. 
+Provide a title for the section so that users can 
+easily identify the issue that they are experiencing.
+
+-->
+
+[Describe the issue.]
+
+<!-- Required: Issue description (no heading)
+
+Describe the issue.
+
+-->
+
+### Prerequisites
+
+<!--Optional: Prerequisites - H3
+
+Use clear and unambiguous language, and use
+an unordered list format. 
+
+-->
+
+### Troubleshooting steps
+
+<!-- Optional: Troubleshooting steps - H3
+
+Not all known issues can be corrected, but if a solution 
+is known, describe the steps to take to correct the issue.
+
+-->
+
+### Possible causes
+
+<!-- Optional: Possible causes - H3
+
+In an H3 section, describe potential causes.
+
+-->