Fix Microsoft Teams Webhook Certificate Errors in Oracle PL/SQL
Question details
Determine which certificates Oracle needs to validate HTTPS calls to a Microsoft Teams webhook.

- Product
- Microsoft Teams webhooks and Oracle PL/SQL
- Device & OS
- not provided
- Scenario
- An Oracle PL/SQL application sends HTTPS requests to a Teams webhook using an Oracle wallet.
- Observed behavior
- Certificate validation fails intermittently or returns after the connection worked for several weeks.
Identify the exact hostname in the webhook URL and the Oracle wallet used by the PL/SQL session. Keep the full webhook URL private because it may contain a secret.
Update the Oracle wallet with the current trusted certificate chain
Use this approach when Oracle cannot validate the webhook host's TLS certificate or the endpoint's certificate chain has changed.
The certificate shown by an endpoint can change. Check the complete current chain for the exact webhook hostname rather than trusting only a previously observed leaf certificate or a certificate from a different host.
From a system with OpenSSL, run `openssl s_client -connect HOSTNAME:443 -servername HOSTNAME -showcerts`, replacing HOSTNAME with the hostname from the webhook URL. Review the certificates and issuers presented.
Use the certificate authority's official sources to obtain the current root and any required intermediate certificates for the chain. Confirm their validity and fingerprints before importing them.
Use Oracle Wallet Manager or `orapki wallet add -wallet WALLET_PATH -trusted_cert -cert CERT_FILE` to import each required trusted certificate into the wallet used by the application. Follow the prompts and Oracle's wallet requirements for your version.
Run `orapki wallet display -wallet WALLET_PATH` to inspect the wallet, then confirm that the PL/SQL session points to it with `UTL_HTTP.SET_WALLET` or the applicable Oracle configuration. Retry the HTTPS request to the exact webhook hostname.

Check webhook status and Oracle TLS diagnostics
Use these checks if the wallet appears correct or the HTTPS request still fails.
Use WPS Office for Office-Compatible Documents
WPS Office is a free, lightweight alternative for working with Office files in a familiar interface. It supports common Microsoft Office formats for an easier move between suites, although it does not fix Teams webhook or Oracle TLS errors.

Frequently Asked Questions
Why did the Teams webhook work before but fail later?
The endpoint's certificate or chain may have changed, or a certificate may have expired. Inspect the current chain for the exact webhook hostname and compare it with the trusted certificates in the Oracle wallet.
Is importing the webhook server's current certificate enough?
Not necessarily. A leaf certificate can be replaced during rotation. Obtain the current chain and configure the required trusted root and intermediates in the Oracle wallet according to your Oracle version's TLS requirements.
How can I see which certificates are in the Oracle wallet?
Run `orapki wallet display -wallet WALLET_PATH` or open the wallet in Oracle Wallet Manager. Compare its trusted certificates with the chain required by the webhook host.
Does an expired webhook cause a certificate validation error?
Webhook expiration and TLS certificate validation are separate issues. Check the webhook's status in the service that created it, and investigate Oracle's TLS error and wallet independently.




