Yes, the key part of the error is: SELF SIGNED CERT IN CHAIN. That almost always means your company network/security appliance is intercepting HTTPS traffic and replacing certificates with an internal corporate certificate, but Node.js / PAC CLI does not trust that certificate. This is not really a Power Platform / PAC issue itself — it’s usually an enterprise SSL inspection / proxy / certificate trust issue.
From your screenshot, the failing endpoint is: blob.core.windows.net (Azure Blob Storage) during pac code push. So the PAC CLI is trying to upload the bundle to Azure storage and Node/npm rejects the TLS certificate chain.
What to ask IT
You can send something like this: I’m using Microsoft Power Platform CLI (pac code push) and HTTPS requests to Azure Blob Storage are failing with SELF SIGNED CERT IN CHAIN. It appears our corporate proxy/security appliance is performing SSL inspection and replacing certificates with an internal CA certificate that Node.js does not trust. Could you please :
Provide the corporate root/intermediate CA certificate
Ensure it is trusted by Node.js applications
Verify access to:
*.blob.core.windows.net
Microsoft Power Platform endpoints
Optionally exclude Azure Blob Storage traffic from SSL inspection
🏷️Please tag me @Kushal_M,if you still have any queries related to the solution or issue persists.
❤️Please consider giving it a Like, If the approach was useful in other ways.
✅Please click Accept as solution if my post helped you solve your issue and help others who will face the similar issue in future.
Was this reply helpful?YesNo
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.