Skip to content

Promote security knowledge from community to Microsoft layer#49

Open
JesperSchulz wants to merge 1 commit into
mainfrom
jesperschulz-promote-security-to-microsoft-layer
Open

Promote security knowledge from community to Microsoft layer#49
JesperSchulz wants to merge 1 commit into
mainfrom
jesperschulz-promote-security-to-microsoft-layer

Conversation

@JesperSchulz

Copy link
Copy Markdown
Contributor

Summary

Pure git mv relocation of the SECURITY knowledge domain from the community layer to the Microsoft layer. No content changes — every file moved byte-for-byte (100% rename similarity). The layer is determined purely by path; the domain: security frontmatter is unchanged. Domain experts review content in this PR.

Articles moved (6)

  • classify-every-field-with-dataclassification (.md + .good.al + .bad.al)
  • compose-permission-sets-with-included-sets (.md + .good.al + .bad.al)
  • do-not-grant-rights-beyond-a-users-entitlement (.md only — intentionally no .al samples)
  • guard-bulk-operations-with-istemporary (.md + .good.al + .bad.al)
  • prefer-oauth2-over-api-keys-for-external-http-calls (.md + .good.al + .bad.al)
  • protect-sensitive-data-in-temporary-tables (.md + .good.al + .bad.al)

16 files total. community/knowledge/security/ is now empty.

Review

Requires domain-expert review. CODEOWNERS auto-requests @darjoo, @WaelAbuSeada, @Aleyenda, @pchriste-microsoft-com.

Validation

  • python .github/scripts/validate_frontmatter.py --root .0 errors / 0 warnings
  • pwsh .github/scripts/Test-KnowledgeIndex.ps1 -Root .PASSED, article count unchanged at 191
  • No filename collisions with existing microsoft/knowledge/security/ slugs.

Do not merge yet — this will sit BLOCKED on the 2-approval ruleset, which is expected.

Pure git-mv relocation of the SECURITY domain from the community layer to the Microsoft layer. No content changes.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants