Remove non-resolving OCSP endpoints from APIM VNet docs. #127944
+1
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Updates APIM VNet documentation to remove invalid OCSP endpoints and align with current Microsoft CA infrastructure.
Changes
ocsp.msocsp.com(retired; no longer resolves).oneocsp.msocsp.comwith the correctoneocsp.microsoft.com.Rationale
Two listed OCSP hosts are no longer functional or documented elsewhere. The Microsoft page “Azure Certificate Authority details” includes a changelog entry (dated 8 October 2024) stating that ocsp.msocsp.com was removed from Microsoft’s CA/CDP/OCSP endpoints list. Cleaning them up prevents incorrect allowlists and reflects current certificate-validation behavior.
Impact
Improves accuracy of outbound network requirements; no change to APIM functionality.