[Doc Improvement][Update the common reasons for validation with the screenshots

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/deploy-and-publish/appsource/common-reasons-for-app-validation-failure.md
92
13
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/deploy-and-publish/appsource/common-reasons-for-app-validation-failure.md
92
13
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Learn Build status updates of commit b510f22:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/concepts/deploy-and-publish/appsource/common-reasons-for-app-validation-failure.md
:warning:Warning
View
Details

msteams-platform/concepts/deploy-and-publish/appsource/common-reasons-for-app-validation-failure.md

Line 83, Column 4: [Warning: file-not-found - See documentation] Invalid file link: '../../../assets/images/submission/validation-common-reasons-unexpected-error-scenarios.png'.
Line 85, Column 4: [Warning: file-not-found - See documentation] Invalid file link: '../../../assets/images/submission/validation-common-reasons-unexpected-error-app-usage.png'.
Line 97, Column 4: [Warning: file-not-found - See documentation] Invalid file link: '../../../assets/images/submission/validation-common-reasons-region-specific-app.png'.
Line 109, Column 4: [Warning: file-not-found - See documentation] Invalid file link: '../../../assets/images/submission/validation-common-reasons-failed-reference-app-funtionality.png'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Learn Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/deploy-and-publish/appsource/common-reasons-for-app-validation-failure.md
92
13
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Learn Build status updates of commit f2f488d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/submission/validation-common-reasons-failed-reference-app-funtionality.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reasons-region-specific-app.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reasons-unexpected-error-app-usage.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reasons-unexpected-error-scenarios.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason--unexpected-error-scenarios.png
:white_check_mark:Succeeded
View

msteams-platform/concepts/deploy-and-publish/appsource/common-reasons-for-app-validation-failure.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/deploy-and-publish/appsource/common-reasons-for-app-validation-failure.md
93
13
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Learn Build status updates of commit e37e1cf:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/submission/validation-common-reason-fail-app-description-truncation.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-app-crashes.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-test-collaboration-scenarios.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-no-test-instructions.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-provided-test-instructions.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-pass-provided-test-instructions.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reasons-failed-reference-app-funtionality.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reasons-fail-inadequate-app-description.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reasons-functional-bugs-fail-block-app-usage.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reasons-pass-inadequate-app-description.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reasons-pass-reference-app-funtionality.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reasons-region-specific-app.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reasons-region-specific-pass-app.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reasons-unexpected-error-app-usage.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reasons-unexpected-error-scenarios.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason--unexpected-error-scenarios.png
:white_check_mark:Succeeded
View

msteams-platform/concepts/deploy-and-publish/appsource/common-reasons-for-app-validation-failure.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/deploy-and-publish/appsource/common-reasons-for-app-validation-failure.md
91
16
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Learn Build status updates of commit d3cc59f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/submission/validation-common-reason-fail-app-description-truncation.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-app-name-beta-app-production.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-app-crashes.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-support-link.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-support-link-authentication.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-support-link-insecure.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-test-collaboration-scenarios.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-inconsistent-app-functionality.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-no-test-instructions.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-old-app-name.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-provided-test-instructions.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-pass-app-name-beta-app-production.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-pass-inconsistent-app-functionality.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-pass-provided-test-instructions.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-pass-support-link.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reasons-failed-reference-app-funtionality.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reasons-fail-inadequate-app-description.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reasons-functional-bugs-fail-block-app-usage.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reasons-pass-inadequate-app-description.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reasons-pass-reference-app-funtionality.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reasons-region-specific-app.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reasons-region-specific-pass-app.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reasons-unexpected-error-app-usage.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reasons-unexpected-error-scenarios.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason--unexpected-error-scenarios.png
:white_check_mark:Succeeded
View

This comment lists only the first 25 files in the pull request.
For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/deploy-and-publish/appsource/common-reasons-for-app-validation-failure.md
91
17
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Learn Build status updates of commit 242cfed:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/submission/validation-common-reason-fail-app-description-truncation.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-app-name-beta-app-production.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-color-icon-outline.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-app-crashes.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-blank-screen-app-UI.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-support-link.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-support-link-authentication.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-support-link-insecure.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-test-collaboration-scenarios.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-inconsistent-app-functionality.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-no-test-instructions.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-old-app-name.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-partner-center-manifest-different.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-provided-test-instructions.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-pass-app-name-beta-app-production.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-pass-color-icon-outline.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-pass-inconsistent-app-functionality.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-pass-provided-test-instructions.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-pass-support-link.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reasons-failed-reference-app-funtionality.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reasons-fail-inadequate-app-description.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reasons-functional-bugs-fail-block-app-usage.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reasons-pass-inadequate-app-description.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reasons-pass-reference-app-funtionality.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reasons-region-specific-app.png
:white_check_mark:Succeeded
View

This comment lists only the first 25 files in the pull request.
For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/deploy-and-publish/appsource/common-reasons-for-app-validation-failure.md
92
17
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Learn Build status updates of commit 6f9c68a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/submission/validation-common-reason-fail-app-description-truncation.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-app-name-beta-app-production.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-color-icon-outline.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-continuous-app.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-domains-with-beta.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-app-crashes.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-blank-screen-app-UI.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-invalid-unsecure-broken-privacy-policy.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-invalid-unsecure-broken-privacy-policy-links.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-support-link.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-support-link-authentication.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-support-link-insecure.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-test-collaboration-scenarios.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-inconsistent-app-functionality.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-no-test-instructions.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-old-app-name.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-partner-center-manifest-different.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-provided-test-instructions.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-resource-URL-manifest.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-terms-of-use.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-pass-app-name-beta-app-production.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-pass-app-version-number.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-pass-color-icon-outline.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-pass-inconsistent-app-functionality.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-pass-provided-test-instructions.png
:white_check_mark:Succeeded
View

This comment lists only the first 25 files in the pull request.
For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/deploy-and-publish/appsource/common-reasons-for-app-validation-failure.md
92
17
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Learn Build status updates of commit 0882316:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/icons/app-description-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/app-guideline-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/app-name-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/app-ui-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/broken-links-errors-icon-1.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/compliance-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/domain-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/localization-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/privacy-policy-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/schema-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/support-link-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/terms-of-use-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/testability-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-app-description-truncation.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-app-name-beta-app-production.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-color-icon-outline.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-continuous-app.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-domains-with-beta.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-app-crashes.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-blank-screen-app-UI.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-invalid-unsecure-broken-privacy-policy.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-invalid-unsecure-broken-privacy-policy-links.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-support-link.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-support-link-authentication.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-support-link-insecure.png
:white_check_mark:Succeeded
View

This comment lists only the first 25 files in the pull request.
For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Learn Build status updates of commit 4120d74:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/icons/app-description-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/app-guideline-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/app-name-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/app-ui-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/broken-links-errors-icon-1.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/compliance-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/domain-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/localization-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/privacy-policy-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/schema-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/support-link-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/terms-of-use-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/testability-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/trademark-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-app-description-truncation.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-app-name-beta-app-production.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-color-icon-outline.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-continuous-app.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-domains-with-beta.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-app-crashes.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-blank-screen-app-UI.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-invalid-unsecure-broken-privacy-policy.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-invalid-unsecure-broken-privacy-policy-links.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-support-link.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-support-link-authentication.png
:white_check_mark:Succeeded
View

This comment lists only the first 25 files in the pull request.
For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/deploy-and-publish/appsource/common-reasons-for-app-validation-failure.md
91
19
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Learn Build status updates of commit a7babd7:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/concepts/deploy-and-publish/appsource/common-reasons-for-app-validation-failure.md
:warning:Warning
View
Details

msteams-platform/assets/icons/app-description-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/app-guideline-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/app-name-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/app-ui-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/broken-links-errors-icon-1.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/compliance-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/domain-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/localization-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/privacy-policy-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/schema-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/support-link-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/terms-of-use-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/testability-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/trademark-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-app-description-truncation.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-app-name-beta-app-production.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-color-icon-outline.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-continuous-app.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-domains-with-beta.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-app-crashes.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-blank-screen-app-UI.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-invalid-unsecure-broken-privacy-policy.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-invalid-unsecure-broken-privacy-policy-links.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-support-link.png
:white_check_mark:Succeeded
View

This comment lists only the first 25 files in the pull request.

msteams-platform/concepts/deploy-and-publish/appsource/common-reasons-for-app-validation-failure.md

Line 23, Column 7: [Warning: bookmark-not-found] Cannot find bookmark '#violation-of-microsoft-trademark-and-brand-guidelines.' in 'concepts/deploy-and-publish/appsource/common-reasons-for-app-validation-failure.md', did you mean '#violation-of-microsoft-trademark-and-brand-guidelines'?

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Learn Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/deploy-and-publish/appsource/common-reasons-for-app-validation-failure.md
91
18
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Learn Build status updates of commit 86fc230:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/icons/app-description-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/app-guideline-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/app-name-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/app-ui-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/broken-links-errors-icon-1.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/compliance-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/domain-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/localization-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/privacy-policy-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/schema-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/support-link-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/terms-of-use-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/testability-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/trademark-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-app-description-truncation.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-app-name-beta-app-production.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-color-icon-outline.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-continuous-app.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-domains-with-beta.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-app-crashes.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-blank-screen-app-UI.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-invalid-unsecure-broken-privacy-policy.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-invalid-unsecure-broken-privacy-policy-links.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-support-link.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-support-link-authentication.png
:white_check_mark:Succeeded
View

This comment lists only the first 25 files in the pull request.
For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/deploy-and-publish/appsource/common-reasons-for-app-validation-failure.md
92
17
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Learn Build status updates of commit 601a2e7:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/icons/app-description-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/app-guideline-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/app-name-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/app-ui-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/broken-links-errors-icon-1.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/compliance-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/domain-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/localization-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/privacy-policy-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/schema-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/support-link-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/terms-of-use-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/testability-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/trademark-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/violation-trademark-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-app-description-truncation.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-app-name-beta-app-production.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-color-icon-outline.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-continuous-app.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-domains-with-beta.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-app-crashes.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-blank-screen-app-UI.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-invalid-unsecure-broken-privacy-policy.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-invalid-unsecure-broken-privacy-policy-links.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-support-link.png
:white_check_mark:Succeeded
View

This comment lists only the first 25 files in the pull request.
For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/deploy-and-publish/appsource/common-reasons-for-app-validation-failure.md
92
17
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Learn Build status updates of commit a811a1c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/icons/app-description-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/app-guideline-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/app-name-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/app-ui-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/broken-links-errors-icon-1.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/compliance-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/domain-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/localization-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/privacy-policy-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/schema-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/support-link-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/terms-of-use-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/testability-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/trademark-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/violation-trademark-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-app-description-truncation.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-app-name-beta-app-production.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-color-icon-outline.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-continuous-app.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-domains-with-beta.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-app-crashes.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-app-localization-manifest.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-blank-screen-app-UI.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-first-reference-teams.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-invalid-unsecure-broken-privacy-policy.png
:white_check_mark:Succeeded
View

This comment lists only the first 25 files in the pull request.
For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/deploy-and-publish/appsource/common-reasons-for-app-validation-failure.md
92
17
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Learn Build status updates of commit d94b20a:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/concepts/deploy-and-publish/appsource/common-reasons-for-app-validation-failure.md
:warning:Warning
View
Details

msteams-platform/assets/icons/app-description-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/app-guideline-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/app-name-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/app-ui-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/broken-links-errors-icon-1.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/compliance-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/domain-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/localization-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/privacy-policy-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/schema-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/support-link-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/terms-of-use-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/testability-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/trademark-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/violation-trademark-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-app-description-truncation.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-app-name-beta-app-production.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-color-icon-outline.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-continuous-app.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-domains-with-beta.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-app-crashes.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-app-localization-manifest.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-blank-screen-app-UI.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-comparsion-app-description.png
:white_check_mark:Succeeded
View

This comment lists only the first 25 files in the pull request.

msteams-platform/concepts/deploy-and-publish/appsource/common-reasons-for-app-validation-failure.md

Line 109, Column 4: [Warning: duplicate-alt-text - See documentation] Alt text 'Screenshot of image to show failed scenario of long description of Microsoft.' is duplicated. Within an article, alt text must be unique.
Line 111, Column 4: [Warning: duplicate-alt-text - See documentation] Alt text 'Screenshot of image to show failed scenario of long description of Microsoft.' is duplicated. Within an article, alt text must be unique.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Learn Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/deploy-and-publish/appsource/common-reasons-for-app-validation-failure.md
92
17
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Learn Build status updates of commit 1313a47:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/concepts/deploy-and-publish/appsource/common-reasons-for-app-validation-failure.md
:warning:Warning
View
Details

msteams-platform/assets/icons/app-description-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/app-guideline-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/app-name-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/app-ui-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/broken-links-errors-icon-1.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/compliance-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/domain-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/localization-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/privacy-policy-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/schema-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/support-link-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/terms-of-use-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/testability-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/trademark-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/violation-trademark-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-app-description-truncation.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-app-display-ads.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-app-name-beta-app-production.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-color-icon-outline.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-continuous-app.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-domains-with-beta.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-app-crashes.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-app-localization-manifest.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-blank-screen-app-UI.png
:white_check_mark:Succeeded
View

This comment lists only the first 25 files in the pull request.

msteams-platform/concepts/deploy-and-publish/appsource/common-reasons-for-app-validation-failure.md

Line 113, Column 4: [Warning: duplicate-alt-text - See documentation] Alt text 'Screenshot of failed image to show the called out limitations.' is duplicated. Within an article, alt text must be unique.
Line 115, Column 4: [Warning: duplicate-alt-text - See documentation] Alt text 'Screenshot of failed image to show the called out limitations.' is duplicated. Within an article, alt text must be unique.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Learn Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/deploy-and-publish/appsource/common-reasons-for-app-validation-failure.md
92
17
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Learn Build status updates of commit 4acf962:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/icons/app-description-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/app-guideline-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/app-name-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/app-ui-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/broken-links-errors-icon-1.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/compliance-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/domain-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/localization-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/privacy-policy-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/schema-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/support-link-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/terms-of-use-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/testability-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/trademark-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/violation-trademark-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-app-description-truncation.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-app-display-ads.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-app-name-beta-app-production.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-color-icon-outline.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-continuous-app.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-domains-with-beta.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-app-crashes.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-app-localization-manifest.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-blank-screen-app-UI.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-comparsion-app-description.png
:white_check_mark:Succeeded
View

This comment lists only the first 25 files in the pull request.
For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/deploy-and-publish/appsource/common-reasons-for-app-validation-failure.md
92
17
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/deploy-and-publish/appsource/common-reasons-for-app-validation-failure.md
92
18
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Learn Build status updates of commit 52d8360:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/icons/app-description-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/app-guideline-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/app-name-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/app-ui-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/broken-links-errors-icon-1.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/compliance-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/developer-name-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/domain-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/localization-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/privacy-policy-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/schema-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/support-link-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/terms-of-use-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/testability-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/trademark-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/violation-trademark-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-app-description-truncation.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-app-display-ads.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-app-name-beta-app-production.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-color-icon-outline.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-continuous-app.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-domains-with-beta.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-app-crashes.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-app-localization-manifest.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-blank-screen-app-UI.png
:white_check_mark:Succeeded
View

This comment lists only the first 25 files in the pull request.
For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/deploy-and-publish/appsource/common-reasons-for-app-validation-failure.md
92
18
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Learn Build status updates of commit 0c9c797:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/icons/app-description-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/app-guideline-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/app-name-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/app-ui-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/broken-links-errors-icon-1.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/compliance-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/developer-name-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/domain-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/localization-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/privacy-policy-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/schema-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/support-link-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/terms-of-use-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/testability-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/trademark-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/violation-trademark-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-app-description-truncation.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-app-display-ads.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-app-name-beta-app-production.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-color-icon-outline.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-continuous-app.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-domains-with-beta.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-app-crashes.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-app-localization-manifest.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-blank-screen-app-UI.png
:white_check_mark:Succeeded
View

This comment lists only the first 25 files in the pull request.
For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/deploy-and-publish/appsource/common-reasons-for-app-validation-failure.md
92
18
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/deploy-and-publish/appsource/common-reasons-for-app-validation-failure.md
92
18
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Learn Build status updates of commit e254b7b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/icons/app-description-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/app-guideline-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/app-name-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/app-ui-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/broken-links-errors-icon-1.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/compliance-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/developer-name-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/domain-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/localization-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/privacy-policy-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/schema-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/support-link-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/terms-of-use-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/testability-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/trademark-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/violation-trademark-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-app-description-truncation.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-app-display-ads.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-app-name-beta-app-production.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-color-icon-outline.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-continuous-app.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-domains-with-beta.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-app-crashes.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-app-localization-manifest.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-blank-screen-app-UI.png
:white_check_mark:Succeeded
View

This comment lists only the first 25 files in the pull request.
For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/deploy-and-publish/appsource/common-reasons-for-app-validation-failure.md
92
18
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Learn Build status updates of commit 3e4bdf7:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/icons/app-description-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/app-guideline-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/app-name-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/app-ui-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/broken-links-errors-icon-1.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/compliance-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/developer-name-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/domain-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/localization-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/privacy-policy-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/schema-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/support-link-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/terms-of-use-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/testability-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/trademark-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/violation-trademark-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-app-description-truncation.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-app-display-ads.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-app-name-beta-app-production.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-color-icon-outline.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-continuous-app.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-domains-with-beta.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-app-crashes.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-app-localization-manifest.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-blank-screen-app-UI.png
:white_check_mark:Succeeded
View

This comment lists only the first 25 files in the pull request.
For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/deploy-and-publish/appsource/common-reasons-for-app-validation-failure.md
91
18
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Learn Build status updates of commit 1b8bf4b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/icons/app-description-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/app-guideline-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/app-name-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/app-ui-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/broken-links-errors-icon-1.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/compliance-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/developer-name-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/domain-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/localization-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/privacy-policy-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/schema-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/support-link-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/terms-of-use-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/testability-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/trademark-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/violation-trademark-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-app-description-truncation.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-app-display-ads.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-app-name-beta-app-production.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-color-icon-outline.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-continuous-app.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-domains-with-beta.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-app-crashes.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-app-localization-manifest.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-blank-screen-app-UI.png
:white_check_mark:Succeeded
View

This comment lists only the first 25 files in the pull request.
For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/deploy-and-publish/appsource/common-reasons-for-app-validation-failure.md
91
18
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Learn Build status updates of commit b36b135:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/icons/app-description-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/app-guideline-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/app-name-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/app-ui-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/broken-links-errors-icon-1.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/compliance-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/developer-name-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/domain-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/localization-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/privacy-policy-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/schema-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/support-link-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/terms-of-use-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/testability-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/trademark-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/violation-trademark-icon.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-app-description-truncation.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-app-display-ads.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-app-name-beta-app-production.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-color-icon-outline.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-continuous-app.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-fail-domains-with-beta.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-app-crashes.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-app-localization-manifest.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/submission/validation-common-reason-failed-blank-screen-app-UI.png
:white_check_mark:Succeeded
View

This comment lists only the first 25 files in the pull request.
For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel


Configuration of Brittany

Afaict, when used by HIE Brittany does not respect the configuration in ~/.brittany/config.yaml. Could Brittany be made configurable by HIE or used in such a way that the configuration file is respected? This change may be best done in the Brittany library itself

Ok, it looks like Brittany reads config values in Main.hs.  @lspitzner How would you feel about a pull request which moved the readConfigs code into an exported module, so that tools like haskell-ide-engine could use it? It seems best for users that tools using Brittany have the same functionality when used by IDEs as they do when used on the command line.

Seems reasonable.
With readConfigs you currently have to either pass non-null list of potential config locations manually or the behaviour depends on the current working dir. The latter is probably not a good idea, if users have per-project config but hie only has once common instance. So i propose the slightly more involved:

expose a variant of readConfigs that never depends on cwd;
expose a defaultGlobalConfigPaths binding that returns those, to prevent code duplication or future divergence.

help found :)
Just a heads up, I've started with the Brittany PR so I can then work on this change.

Oops, I haven't realised that someone is working on it and made a PR to Brittany a couple of days ago:
https://github.com/lspitzner/brittany/pull/121

@AlexRaga no problem! I'll find something else to help with. Nice work BTW!


guide: make proper DVC File guide + separate reference?

Some/parts of the docs in https://dvc.org/doc/user-guide/dvc-files feel more like a reference than a guide. While it's arguable whether that is a problem (e.g. other docs in that section have the same "problem"), it seems we agree that an actual guide for writing dvc.yaml would be great to have, since it's such a major component of DVC projects. Some ideas (from https://github.com/iterative/dvc.org/pull/2052#pullrequestreview-558335370):

we could separate the dvc.yaml format explanation?
Like dvc.yaml short reference, then a section about "stage definition" explaining what key/value it takes, then "variables/parametriation" and then introduce loops. This way, concepts will get built (up on)

split it into subsections - one about regular simple pointers .dvc, second about dvc.yaml and start writing a proper guide in it, start building proper structure

similar docs (spacy, ansible, etc...
I like docker-compose. Examples with one or two lines of text
to write intro and help people write the yaml themselves, that fusion in spacy projects is nicer.
we could also take a look at pypyr: They have separated the yaml definitions nicely into sections/concepts

And from https://github.com/iterative/dvc.org/pull/2052#pullrequestreview-562269533

we should have this references, there should be some general description, then basic layout, then other syntax like templating, loops, etc. Again, let's refer to some good examples that describe languages

And https://github.com/iterative/dvc.org/pull/2052#issuecomment-757025327

The biggest concern is still structure... these titles (inside DVC Files) do not look good to me... They should higher level.

.dvc file - is clearly a reference thing. Where do we put it?
do we need two seprate dvc.yaml sections?
advanced-dvc.yaml - is too heavy and a mix of a reference (precise spec) and guide (story-like)

Oh, and:

I'm also thinking we will need to split dvc.yaml from .dvc files in the guide (as a 3rd level in the main nav) so these H3s become H2s and are shown in the right-hand nav
we'll just need to repeat the Outputs and Dependencies sections in both pages (.dvc file outs/deps are a little different from those in dvc.yaml anyway so that would be more correct even if there's overlap).
From https://github.com/iterative/dvc.org/pull/2052#pullrequestreview-558335854

@shcheklein I moved all pending structure discussions from #2052 to here (see desc.). On your Q from https://github.com/iterative/dvc.org/pull/2052#issuecomment-757025327:

do we need two separate dvc.yaml sections? why do we consider basic templating and advanced feature?

Ideally not (let's come up with a definite org here) but for now it works so we clearly separate the 2.0 features into https://dvc.org/doc/user-guide/dvc-files/advanced-dvc.yaml.
And we can call it "basic" templating but the explanation takes a while (params files, global vars, local vars, etc. etc.) so maybe it's not that basic. But if we completely extract the reference part then yeah, it should be able to fit in the single dvc.yaml guide along with multi-stages — it will still be long though but maybe that's OK/inevitable.

@shcheklein I moved all pending structure discussions from #2052 to here (see desc.). On your Q from https://github.com/iterative/dvc.org/pull/2052#issuecomment-757025327:

do we need two separate dvc.yaml sections? why do we consider basic templating and advanced feature?

Ideally not (let's come up with a definite org here) but for now it works so we clearly separate the 2.0 features into https://dvc.org/doc/user-guide/dvc-files/advanced-dvc.yaml.
And we can call it "basic" templating but the explanation takes a while (params files, global vars, local vars, etc. etc.) so maybe it's not that basic. But if we completely extract the reference part then yeah, it should be able to fit in the single dvc.yaml guide along with multi-stages — it will still be long though but maybe that's OK/inevitable.

@jorgeorpinel, something wrong with the docs? The direct link downloads the html page for me.

@jorgeorpinel, something wrong with the docs? The direct link downloads the html page for me.

@jorgeorpinel, you might need to change it to Advanced dvc-yaml 🙂

@jorgeorpinel, you might need to change it to Advanced dvc-yaml 🙂

o_O yeah I guess the URL shouldn't end in .yaml ... That's a bug! You can load it from https://dvc.org/doc/user-guide/dvc-files though. Will address separately... Thanks @skshetry

o_O yeah I guess the URL shouldn't end in .yaml ... That's a bug! You can load it from https://dvc.org/doc/user-guide/dvc-files though. Will address separately... Thanks @skshetry

Fix in #2090 (please merge when you can @shcheklein)

Fix in #2090 (please merge when you can @shcheklein)

I don't understand why we don't use right-side TOC instead. I find traversing through those pages difficult

@skshetry yes maybe a single dvc.yaml guide with several H2 headers (even if it's long) will be part of the solution here. But one more reason we sometimes avoid that you can see in cmd refs with multiple Examples (e.g. https://dvc.org/doc/command-reference/remote): you may notice there are some issues such, like having to scroll in a small space (see also #723, #753).

Can dvc.yaml fit a single page - good question. I really hope so, I'm though worried that about some points...

@shcheklein it could be one guide page and one reference page somewhere else. I think we may need to extract the reference part to a new top section for DVC File/Format refs though (DV "Language" ref). Put .dvc, dvc.yaml/lock, .dvcignore, and maybe even .dvc/ dir (internals) there... But let me finish researching other docs sites and come up with a final proposal ⌛

I don't understand why we don't use right-side TOC instead. I find traversing through those pages difficult

@skshetry yes maybe a single dvc.yaml guide with several H2 headers (even if it's long) will be part of the solution here. But one more reason we sometimes avoid that you can see in cmd refs with multiple Examples (e.g. https://dvc.org/doc/command-reference/remote): you may notice there are some issues such, like having to scroll in a small space (see also #723, #753).

Can dvc.yaml fit a single page - good question. I really hope so, I'm though worried that about some points...

@shcheklein it could be one guide page and one reference page somewhere else. I think we may need to extract the reference part to a new top section for DVC File/Format refs though (DV "Language" ref). Put .dvc, dvc.yaml/lock, .dvcignore, and maybe even .dvc/ dir (internals) there... But let me finish researching other docs sites and come up with a final proposal ⌛

@jorgeorpinel

you may notice there are some issues such, like having to scroll in a small space (see also #723, #753).

those glitches should not determine layout to my mind in any way. Those are issues that should be fixed.

But let me finish researching other sites and come up with a final proposal ⌛

yep!

@jorgeorpinel

you may notice there are some issues such, like having to scroll in a small space (see also #723, #753).

those glitches should not determine layout to my mind in any way. Those are issues that should be fixed.

But let me finish researching other sites and come up with a final proposal ⌛

yep!

Pending research (1/2)
On the terminology, I'm going for "${} expression", "replace", "generate" (details in https://github.com/iterative/dvc.org/pull/2052#discussion_r557595088)

Pending research (1/2)
On the terminology, I'm going for "${} expression", "replace", "generate" (details in https://github.com/iterative/dvc.org/pull/2052#discussion_r557595088)

(2/2)
On the organization of docs (Can dvc.yaml fit a single page?), here are some raw results:

Helm has
(1) a long, monolithic "Topic" (guide + ref) for Charts (Chart.yaml), and
(2-13) a series of guides about templating elsewhere. No dedicated schema ref.
Verdict: 👎 Their docs lack easy nav menus and seem pretty hard to browse/revisit. The topic is spread across at least 13 pages.

Kubernetes
(1) ConfigMap (K8s objects e.g. pod.yml) are explained in the "Overview/Configuration" section.
(2) A disconnected how-to Config. Pod w/ ConfigMap page is provided too.
(3) An entirely separate site for the underlying API ref exists as well.
Verdict: 🙆♂ Considering their huge docs, you can find what you need (not super easy: the left nav is complicated). The right-side ToC nav helps explore long pages.

spaCy Projects (project.yml) is all
(1) stuffed into a single, very long page. The top section is an intro guide, and the remaining sections mix guide + ref.
Verdict: 🙆♂ Smart graphic design helps a lot (e.g. project.yml samples floated right, clear schema ref. tables). But the page is way long and all the nav (external and ToC) is all on the left side, while the right side has space to spare

BTW their project.yml looks a lot like our dvc.yaml (fields description, vars, commands with deps/outputs)

Ansible playbooks (playbook.yml) are mentioned heavily in (1-4) several descriptive docs in their User Guide (and in other docs later), and finally described properly in (5) a buried guide. There's (6, 7) a couple related references in different places (the latter one has the YAML schema)
Verdict: 👎 Too many guides in many places to cover all the playbook features. The familiar readthedocs-site could be a good thing but the nav is super complicated.

(2/2)
On the organization of docs (Can dvc.yaml fit a single page?), here are some raw results:

Helm has
(1) a long, monolithic "Topic" (guide + ref) for Charts (Chart.yaml), and
(2-13) a series of guides about templating elsewhere. No dedicated schema ref.
Verdict: 👎 Their docs lack easy nav menus and seem pretty hard to browse/revisit. The topic is spread across at least 13 pages.

Kubernetes
(1) ConfigMap (K8s objects e.g. pod.yml) are explained in the "Overview/Configuration" section.
(2) A disconnected how-to Config. Pod w/ ConfigMap page is provided too.
(3) An entirely separate site for the underlying API ref exists as well.
Verdict: 🙆♂ Considering their huge docs, you can find what you need (not super easy: the left nav is complicated). The right-side ToC nav helps explore long pages.

spaCy Projects (project.yml) is all
(1) stuffed into a single, very long page. The top section is an intro guide, and the remaining sections mix guide + ref.
Verdict: 🙆♂ Smart graphic design helps a lot (e.g. project.yml samples floated right, clear schema ref. tables). But the page is way long and all the nav (external and ToC) is all on the left side, while the right side has space to spare

BTW their project.yml looks a lot like our dvc.yaml (fields description, vars, commands with deps/outputs)

Ansible playbooks (playbook.yml) are mentioned heavily in (1-4) several descriptive docs in their User Guide (and in other docs later), and finally described properly in (5) a buried guide. There's (6, 7) a couple related references in different places (the latter one has the YAML schema)
Verdict: 👎 Too many guides in many places to cover all the playbook features. The familiar readthedocs-site could be a good thing but the nav is super complicated.

docker-compose.yml is introduced in the Compose docs, but the Compose file ref (partly a guide too) is a GH repo.
Verdict: 👎 The Compose docs are short and sweet but the actual schema ref. on GH is hard to navigate (seems lazy to have it there)

pypyr pipelines (pipelinename.yaml) are introed in the CLI ref and explained shortly after in their own section of docs (mix of guide + ref).
 The docs site UI is so-so though.

That said it's obviously a simple project so it's easier to organize effectively.

docker-compose.yml is introduced in the Compose docs, but the Compose file ref (partly a guide too) is a GH repo.
Verdict: 👎 The Compose docs are short and sweet but the actual schema ref. on GH is hard to navigate (seems lazy to have it there)

pypyr pipelines (pipelinename.yaml) are introed in the CLI ref and explained shortly after in their own section of docs (mix of guide + ref).
 The docs site UI is so-so though.

That said it's obviously a simple project so it's easier to organize effectively.

See #2098 for a WIP proposal to address all this.
p.s. what about https://dvc.org/doc/user-guide/dvc-internals and https://dvc.org/doc/user-guide/dvcignore, shuold we move them into the DVC Files nav section?

See #2098 for a WIP proposal to address all this.
p.s. what about https://dvc.org/doc/user-guide/dvc-internals and https://dvc.org/doc/user-guide/dvcignore, shuold we move them into the DVC Files nav section?

about dvc.yaml and start writing a proper guide in it, start building proper structure

Question on this: won't it be pretty repetitive with https://dvc.org/doc/start/data-pipelines (once we rewrite that page)? Meaning, how should the basic dvc.yaml User Guide do differ from the Get Started: Data Pipelines?

about dvc.yaml and start writing a proper guide in it, start building proper structure

Question on this: won't it be pretty repetitive with https://dvc.org/doc/start/data-pipelines (once we rewrite that page)? Meaning, how should the basic dvc.yaml User Guide do differ from the Get Started: Data Pipelines?

The purpose of the get started is to give a brief overview, it can be actionable so that people can try it. In our case it's already too long (mostly because we tend to grow all the documents and from time to time we need to dry them)
The purpose of the User Guide is to provide comprehensive information (e.g. language spec). To some extent even Command Reference can be considered part of the User Guide for example.
It means that these document should be very different in language, in how they are structured, otherwise something is probably not right.

The purpose of the get started is to give a brief overview, it can be actionable so that people can try it. In our case it's already too long (mostly because we tend to grow all the documents and from time to time we need to dry them)
The purpose of the User Guide is to provide comprehensive information (e.g. language spec). To some extent even Command Reference can be considered part of the User Guide for example.
It means that these document should be very different in language, in how they are structured, otherwise something is probably not right.