What causes Fabric Pipeline Error 2113?

The Base64-encoded PFX certificate string was incorrectly copied or contains extra whitespace or line breaks. The password provided does not match the password used when the PFX certificate was originally exported. The PFX file itself is corrupted or was encoded with a non-standard Base64 encoding. The certificate has expired or is not in the expected PFX/PKCS#12 format

How do I fix Fabric Pipeline Error 2113?

Step 1: Re-export the PFX certificate from the certificate store or KeyVault, ensuring you use the correct private key export option and note the exact password used during export.. Step 2: Re-encode the PFX file to Base64 using a reliable tool (e.g., PowerShell: `[Convert]::ToBase64String([IO.File]::ReadAllBytes('cert.pfx'))`) and replace the existing value in the pipeline connection.. Step 3: Confirm the password entered in the pipeline or linked service exactly matches the PFX export password — check for leading/trailing spaces and character encoding issues.. Step 4: Validate the certificate locally by attempting to import it using the same Base64 string and password with a test script before saving it back to the pipeline.. Step 5: If using Azure Key Vault to store the certificate or password, verify that the secret versions referenced in the linked service are current and have not been rotated without updating the pipeline reference.

High severityauthenticationMicrosoft Fabric →

Power BI Refresh Error:
Fabric Pipeline Error 2113

What does this error mean?

Error 2113 occurs when Fabric cannot generate a valid certificate from the provided Base64-encoded PFX string and password combination. The certificate or password is incorrect, corrupted, or improperly encoded.

Common causes

1The Base64-encoded PFX certificate string was incorrectly copied or contains extra whitespace or line breaks
2The password provided does not match the password used when the PFX certificate was originally exported
3The PFX file itself is corrupted or was encoded with a non-standard Base64 encoding
4The certificate has expired or is not in the expected PFX/PKCS#12 format

How to fix it

1Step 1: Re-export the PFX certificate from the certificate store or KeyVault, ensuring you use the correct private key export option and note the exact password used during export.
2Step 2: Re-encode the PFX file to Base64 using a reliable tool (e.g., PowerShell: `[Convert]::ToBase64String([IO.File]::ReadAllBytes('cert.pfx'))`) and replace the existing value in the pipeline connection.
3Step 3: Confirm the password entered in the pipeline or linked service exactly matches the PFX export password — check for leading/trailing spaces and character encoding issues.
4Step 4: Validate the certificate locally by attempting to import it using the same Base64 string and password with a test script before saving it back to the pipeline.
5Step 5: If using Azure Key Vault to store the certificate or password, verify that the secret versions referenced in the linked service are current and have not been rotated without updating the pipeline reference.

Frequently asked questions

How do I correctly convert a PFX file to a Base64 string for use in Fabric?

In PowerShell, run: `[Convert]::ToBase64String([IO.File]::ReadAllBytes('C:\path\to\cert.pfx'))`. Copy the entire output string without any line breaks and paste it into the pipeline's certificate field.

Can I store the PFX Base64 string in Azure Key Vault instead of directly in the pipeline?

Yes, and this is the recommended approach. Store the Base64 string as a Key Vault secret and reference it via a Key Vault linked service in your Fabric pipeline to avoid hardcoding sensitive certificate data.