Revise container support details in migration guide

[Rui Hiraoka (rui-hira)]

Updated container support information for Service Fabric Managed Clusters, clarifying support for Windows containers and installation requirements for container runtimes.

[prmerger-automator]

Rui Hiraoka (@rui-hira) : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

[prmerger-automator]

Rui Hiraoka (@rui-hira) : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

[learn-build-service-prod]

Learn Build status updates of commit ddcb043:

❌ Validation status: errors

Please follow instructions here which may help to resolve issue.

File	Status	Preview URL	Details
articles/service-fabric/security-controls-policy.md	❌Error		Details
articles/virtual-machines/security-controls-policy-image-builder.md	❌Error		Details
articles/virtual-machines/security-controls-policy.md	❌Error		Details

articles/service-fabric/security-controls-policy.md

• Line 22, Column 1: [Error: include-not-found - See documentation] Invalid include link: '~/azure-docs-pr/includes/policy/standards/intro-warning.md'.

articles/virtual-machines/security-controls-policy-image-builder.md

• Line 23, Column 1: [Error: include-not-found - See documentation] Invalid include link: '~/azure-docs-pr/includes/policy/standards/intro-warning.md'.

articles/virtual-machines/security-controls-policy.md

• Line 23, Column 1: [Error: include-not-found - See documentation] Invalid include link: '~/azure-docs-pr/includes/policy/standards/intro-warning.md'.

For more details, please refer to the build 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.

[Regan Downer (v-regandowner)]

Tom Cassidy (@tomvcassidy)

Can you review the proposed changes?

IMPORTANT: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

[github-actions]

This pull request has been inactive for at least 14 days. If you are finished with your changes, don't forget to sign off. See the contributor guide for instructions.
Get Help
Docs Support Teams Channel
Resolve Merge Conflict