Skip to content

Conversation

@BrandynR-MSFT
Copy link
Contributor

Updated and clarified wording for supported TLS versions (1.2 and 1.3) as the 'upto 1.0' was misleading. TLS 1.0 and 1.1 Retirement which has lead to enforcement of TLS1.2 and 1.3 across Azure

Updated and clarified wording for supported TLS versions (1.2 and 1.3) as the 'upto 1.0' was misleading. 
TLS 1.0 and 1.1 Retirement which has lead to enforcement of TLS1.2 and 1.3 across Azure
@prmerger-automator
Copy link
Contributor

@BrandynR-MSFT : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit 528c751:

✅ Validation status: passed

File Status Preview URL Details
articles/application-gateway/application-gateway-ssl-policy-overview.md ✅Succeeded

For more details, please refer to the build report.

@ktoliver
Copy link
Contributor

@mbender-ms

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

@prmerger-automator prmerger-automator bot added the aq-pr-triaged tracking label for the PR review team label Nov 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants