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
⚠️
powershell_heavy
⚠️
windows_first
⚠️
missing_linux_example
Summary:
The documentation demonstrates a moderate Windows bias. While it does provide some cross-platform guidance (notably OpenSSL commands for certificate handling), it frequently references Windows-specific tools (IIS, Certreq.exe), provides PowerShell examples alongside Azure CLI but not Bash or Linux-native scripting, and lists Windows/container limitations before Linux ones. There are no explicit Linux GUI or command-line examples for certificate management, and automation examples are limited to Azure CLI and PowerShell, omitting Bash or Linux-native approaches.
Recommendations:
- When referencing certificate export or creation, provide Linux-native alternatives (e.g., using OpenSSL on Linux) before or alongside Windows tools like IIS or Certreq.exe.
- For automation, include Bash shell script examples or at least mention that Azure CLI commands work cross-platform, and provide explicit Linux/Bash usage where possible.
- When listing platform-specific limitations or capabilities (e.g., outbound calls with private CA client certificates), clearly state Linux support status and provide parity in explanations.
- Avoid listing Windows/PowerShell examples before Linux equivalents; alternate or group by platform.
- Add a section or callout for Linux users, summarizing the typical workflow and tools they would use for certificate management in Azure App Service.
- Where screenshots or UI steps are shown, clarify if the experience is identical on Linux-hosted apps or note any differences.
Create pull request
Scan History
| Date | Scan ID | Status | Bias Status |
|---|---|---|---|
| 2025-07-12 23:44 | #41 | in_progress | ❌ Biased |
| 2025-07-12 00:58 | #8 | cancelled | ✅ Clean |
| 2025-07-10 05:06 | #7 | processing | ✅ Clean |
| 2025-07-09 23:22 | #6 | cancelled | ✅ Clean |
Flagged Code Snippets
#### [Azure PowerShell](#tab/azure-powershell/rbac)
#### 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.