Azure certificate authority, CRL and OCSP endpoints
Microsoft's edit ·
Microsoft's commit message in MicrosoftDocs/azure-docs · commit 21342c4 · +1 −1 lines · also on GitHub
⋯ 218 unchanged lines
219219
220220
## Certificate pinning
221221
222
−Certificate pinning is a security technique where you accept only authorized, or *pinned*, certificates when establishing a secure session. The process rejects any attempt to establish a secure session using a different certificate. For publicly trusted TLS certificates used by Azure services, Microsoft generally doesn't recommend static certificate pinning. For more information, see [Certificate pinning](certificate-pinning.md).
222
+Certificate pinning is a security technique where you accept only authorized, or *pinned*, certificates when establishing a secure session. The process rejects any attempt to establish a secure session using a different certificate. For more information, including guidance on static pinning of publicly trusted certificates, see [Certificate pinning](certificate-pinning.md).
223223
224224
### How to address certificate pinning
225225
⋯ 158 unchanged lines
Microsoft's Markdown source from MicrosoftDocs/azure-docs, © Microsoft Corporation, under CC BY 4.0. Changed lines with up to 3 unchanged lines around each; ChangeIntel kept this copy 10 Oct 00:08 UTC. The commit date is when the source changed, which can be hours or days before Learn published it.