Add/update Copilot instructions in .github

Author: RoseHJM

.github/copilot-instructions.md

@@ -0,0 +1,36 @@
+# Pull Request Review Instructions
+
+1. **Check Formatting**
+  - Ensure markdown headings are structured logically (H1 → H2 → H3).
+  - Verify lists, tables, and code blocks render correctly.
+  - Confirm links are valid and use relative paths when appropriate.
+
+2. **Validate Content**
+  - Confirm technical accuracy (APIs, parameters, commands, screenshots).
+  - Ensure examples are correct, build/run, and follow best practices.
+  - Remove outdated references or deprecated features.
+
+3. **Style and Clarity**
+  - Follow Microsoft Writing Style Guide (clarity, simplicity, consistency).
+  - Use inclusive, neutral language.
+  - Fix spelling, grammar, and punctuation issues.
+
+4. **Metadata and Structure**
+  - Verify front matter (title, description, author, ms.service, ms.topic).
+  - Ensure TOC placement and navigation are correct.
+  - Confirm file naming and folder structure follow repo conventions.
+
+5. **Compliance and Security**
+  - Remove secrets, keys, usernames, or confidential data.
+  - Avoid third‑party copyrighted content without proper permission.
+  - Check that code and text samples respect licensing requirements.
+
+6. **Testing and Validation**
+  - Run any documented commands in a safe/test environment when possible.
+  - Validate code snippets compile or run as described.
+  - For UI steps, confirm that labels and flows match the current portal/CLI.
+
+7. **Review Outcome**
+  - **Approve** when the change is technically correct, clear, and compliant.
+  - **Request changes** with specific, actionable comments.
+  - **Comment only** for non‑blocking suggestions or questions.