Skip to content

Add cross-links to common validation failure article - #14512

Open
v-spakirla wants to merge 3 commits into
mainfrom
v-spakirla-toc-move-common-validation-failure
Open

Add cross-links to common validation failure article#14512
v-spakirla wants to merge 3 commits into
mainfrom
v-spakirla-toc-move-common-validation-failure

Conversation

@v-spakirla

@v-spakirla v-spakirla commented Jul 27, 2026

Copy link
Copy Markdown

Summary

This PR adds cross-links between related articles so developers can discover common validation failures while preparing their submission.

Changes

  • submission-checklist.md: Added link to "Common reasons for app validation failure" in See also
  • teams-store-validation-guidelines.md: Added link to "Common reasons for app validation failure" in See also
  • common-reasons-for-app-validation-failure.md: Added link to "Prepare your Teams Store submission" in See also

Fixes #14114

Relocate 'Common reasons for app validation failure' from post-publish
section to before 'Submit your app' so developers can review common
failures while preparing their submission.

Fixes #14114

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
@learn-build-service-prod

Copy link
Copy Markdown
Contributor

PoliCheck Scan Report

The following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans.

✅ No issues found

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.

@learn-build-service-prod

Copy link
Copy Markdown
Contributor

Learn Build status updates of commit 5158a1d:

✅ Validation status: passed

File Status Preview URL Details
msteams-platform/TOC.yml ✅Succeeded View

For more details, please refer to the build report.

v-spakirla and others added 2 commits July 27, 2026 13:01
Instead of moving the TOC entry, add cross-links between related
articles so developers discover common validation failures while
preparing their submission:

- submission-checklist.md: added link to common-reasons article
- teams-store-validation-guidelines.md: added link to common-reasons article
- common-reasons-for-app-validation-failure.md: added link to submission checklist

Fixes #14114

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
@v-spakirla v-spakirla changed the title Move "Common reasons for app validation failure" before "Submit your app" in TOC Add cross-links to common validation failure article Jul 27, 2026
@learn-build-service-prod

Copy link
Copy Markdown
Contributor

PoliCheck Scan Report

The following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans.

✅ No issues found

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.

@learn-build-service-prod

Copy link
Copy Markdown
Contributor

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.

TOC placement of common reason for failure article

1 participant