Document Details
Configure Ssl Certificate
❌
This page contains Windows bias
About This Page
This page is part of the Azure documentation. It contains code examples and configuration instructions for working with Azure services.
Bias Analysis
Bias Types:
⚠️
windows_tools
⚠️
windows_first
⚠️
powershell_heavy
⚠️
missing_linux_example
Summary:
The documentation demonstrates a moderate Windows bias. While it provides some cross-platform guidance (e.g., OpenSSL commands for certificate export), it references Windows-specific tools (IIS, Certreq.exe) without equivalent Linux alternatives, lists Azure PowerShell examples alongside Azure CLI but does not provide Bash or Linux-native scripting examples, and refers to Windows-specific scenarios in FAQs. Linux tools and workflows are either missing or mentioned after Windows options.
Recommendations:
- When referencing Windows tools like IIS or Certreq.exe for certificate export, also provide equivalent Linux commands or tools (e.g., OpenSSL, certbot, or native Linux certificate management instructions).
- Include Linux/Bash scripting examples for automation tasks, not just Azure CLI and PowerShell.
- In FAQs and scenario explanations, clarify Linux support and provide Linux-specific guidance where features differ (e.g., outbound client certificate support in Linux containers).
- Ensure that cross-platform tools (like OpenSSL) are presented as primary options, and avoid implying Windows tools are the default or preferred method.
- Where PowerShell is used, provide Bash or shell script equivalents for Linux users.
Create pull request
Scan History
| Date | Scan ID | Status | Bias Status |
|---|---|---|---|
| 2025-09-10 00:00 | #107 | completed | ✅ Clean |
| 2025-08-21 00:01 | #87 | in_progress | ❌ Biased |
| 2025-08-20 00:01 | #86 | completed | ❌ Biased |
| 2025-08-19 00:01 | #85 | completed | ❌ Biased |
| 2025-08-18 00:00 | #84 | in_progress | ❌ Biased |
| 2025-08-17 00:01 | #83 | in_progress | ❌ Biased |
| 2025-08-16 00:00 | #82 | in_progress | ❌ Biased |
| 2025-08-15 00:01 | #81 | in_progress | ❌ Biased |
| 2025-07-22 00:01 | #57 | completed | ✅ Clean |
| 2025-07-19 13:51 | #54 | completed | ✅ Clean |
| 2025-07-17 00:00 | #53 | completed | ❌ Biased |
| 2025-07-16 00:00 | #52 | completed | ❌ Biased |
| 2025-07-13 21:25 | #47 | cancelled | ✅ Clean |
| 2025-07-13 20:48 | #44 | cancelled | ❌ Biased |
| 2025-07-09 13:09 | #3 | cancelled | ✅ Clean |
| 2025-07-08 04:23 | #2 | cancelled | ❌ Biased |
Flagged Code Snippets
#### Export the merged private certificate to .pfx
Now, export your merged TLS/SSL certificate with the private key that was used to generate your certificate request. If you generated your certificate request by using OpenSSL, then you created a private key file.
OpenSSL v3 changed the default cipher from 3DES to AES256. Use the command line `-keypbe PBE-SHA1-3DES -certpbe PBE-SHA1-3DES -macalg SHA1` to override the change.
OpenSSL v1 uses 3DES as the default, so the .pfx files that are generated are supported without any special modifications.
1. To export your certificate to a .pfx file, run the following command. Replace the placeholders _<private-key-file>_ and _<merged-certificate-file>_ with the paths to your private key and your merged certificate file.